usefor-usefor-01 September 2004

6.2  Informative References

   [ISO.3166.1988]
    International Organization for Standardization, "Codes for
    the representation of names of countries, 3rd edition",
    ISO Standard 3166, August 1988.
   [PGPVERIFY]
    Lawrence, D., "PGPverify", June 1999.

   [RFC0977]  Kantor, B. and P. Lapsley, "Network News Transfer
    Protocol", RFC 977, February 1986.

   [RFC1036]  Horton, M. and R. Adams, "Standard for interchange of
    USENET messages", RFC 1036, December 1987.

   [RFC2633]  Ramsdell, B., "S/MIME Version 3 Message Specification",
    RFC 2633, June 1999.

   [RFC3156]  Elkins, M., Del Torto, D., Levien, R. and T. Roessler,
    "MIME Security with OpenPGP", RFC 3156, August 2001.

   [Son-of-1036]
    Spencer, H., "News Article Format and Transmission", June
    1994.

   [USEAGE]   Lindsey, C., "Usenet Best Practice",
    draft-ietf-usefor-useage-*.txt.

   [USEPRO]   Lindsey, C., "News Article Architecture and Protocols",
    draft-ietf-usefor-usepro-*.txt.


Authors' Addresses

   Charles H. Lindsey
   University of Manchester
   5 Clerewood Avenue
   Heald Green
   Cheadle
   Chesire  SK8 3JU
   GB

   Phone: +44 161 436 6131
   EMail: chl@clw.cs.man.ac.uk


   Kenneth Murchison
   Oceana Matrix Ltd.
   21 Princeton Place
   Orchard Park, NY  14127
   US

   Phone: +1 716 662 8973
   EMail: ken@oceana.com
   Dan Kohn
   Skymoon Ventures
   3045 Park Boulevard
   Palo Alto, CA  94306
   US

   Phone: +1 650 327 2600
   EMail: dan@dankohn.com
Appendix A.  Acknowledgements

   Comments and/or text were provided by Mark Crispin, Claus Faerber,
   Ned Freed, Andrew Gierth, Tony Hansen, Paul Hoffman, Simon Josefsson,
   Bruce Lilly, Pete Resnick, and Henry Spencer.
Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2004).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.