rfc2901.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

   preserving the operational stability of the Internet; to promoting
   competition; to achieving broad representation of global Internet
   communities; and to developing policy through private-sector,
   bottom-up, consensus-based means.  ICANN welcomes the participation
   of any interested Internet user, business, or organization.




Wenzel, et al.               Informational                     [Page 25]

RFC 2901      Administrative Internet Infrastructure Guide   August 2000


   Email:          [e-mail]
   Postal:         Internet Corporation for Assigned Names and Numbers
                   (ICANN)
                   4676 Admiralty Way, Suite 330
                   Marina del Rey, CA 90292
                   USA
   Telehone:       [phone]
   Fax:            [phone]
   Internet:       http://www.icann.org/

   o  InterNIC

   The InterNIC was a cooperative activity between the National Science
   Foundation, General Atomics, AT&T, and Network Solutions, Inc.  The
   joint activity InterNIC no longer exists.

   Currently, Network Solutions runs the central registry according to
   the shared registry model specified by ICANN for registration of
   second-level domain names under the generic top-level
   domains .com, .net, and .org.

   For information on accredited registrars for .com, .net, and .org,
   please see:

      http://www.icann.org/registrars/accredited-list.html

   (note that Network Solutions is an accredited registrar as well as
   the entity running the registry).

   Email:          [e-mail]
   Postal:         Network Solutions, Inc.
                   505 Huntmar Park Dr.
                   Herndon, VA 20170 US
   Telephone:      [phone]
   Fax:            [phone]
   Internet:       http://www.networksolutions.com/

   Regional Internet Registries (IRs)

   Regional IRs operate in large geopolitical regions such as
   continents.  Currently, there are three Regional IRs: ARIN for the
   Americas, the Caribbean, and Africa; RIPE NCC for Europe, Africa, and
   the Middle East; and APNIC for the Asia Pacific region.  The specific
   duties of the Regional IRs include coordination and representation of
   all local Internet Registries in their respective region.






Wenzel, et al.               Informational                     [Page 26]

RFC 2901      Administrative Internet Infrastructure Guide   August 2000


   o  APNIC

   Asia Pacific Network Information Center (APNIC) is a non-profit
   Internet registry for the Asia Pacific region.  APNIC provides IP
   address allocation, Autonomous System Number (ASN) assignment, and
   IN-ADDR.ARPA registration.

   Email:          [e-mail]
   Postal:         APNIC Box 2131
                   Milton Queensland 4064
                   Australia
   Telephone:      [phone]
   Fax:            [phone]
   Internet:       http://www.apnic.net/

   o ARIN

   The American Registry for Internet Numbers (ARIN) is a non-profit
   Internet registry that was established for the purpose of
   administration and registration of Internet Protocol (IP) numbers to
   the geographical areas that were previously managed by Network
   Solutions, Inc.  These areas include, but are not limited to, North
   America, South America, Africa, and the Caribbean region.  ARIN
   provides IP address allocation, Autonomous System Number (ASN)
   assignment, and IN-ADDR.ARPA registration.

   Email:          [e-mail]
   Postal:         4506 Daly Drive
                   Suite 200
                   Chantilly, VA  20151
   Telephone:      [phone]
   Fax             [phone]
   Internet:       http://www.arin.net/

   o RIPE NCC

   Reseaux IP Europens Network Coordination Centre (RIPE NCC) is a non-
   profit Internet registry for the European, North African, and Middle
   East regions.  RIPE NCC provides IP address allocation, Autonomous
   System Number (ASN) assignment, and IN-ADDR.ARPA registration.

   Email:          [e-mail]
   Postal:         Singel 258
                   1016 AB Amsterdam
                   The Netherlands
   Phone:          [phone]
   Fax:            [phone]
   Internet:       http://www.ripe.net/



Wenzel, et al.               Informational                     [Page 27]

RFC 2901      Administrative Internet Infrastructure Guide   August 2000


Appendix B:     Documentation

   Internet Documentation

   For general Internet documentation, "ftp" to rfc-editor.org and "cd"
   to the /rfc subdirectory for Request for Comments documents.

   Details on obtaining these documents via ftp or email may be obtained
   by sending an email message to:

      [e-mail]

   with the message body  help: ways_to_get_rfcs.  For example:

      To: [e-mail]
      Subject: getting rfcs

      help: ways_to_get_rfcs

   Documents, Templates, and Forms

   The documents, templates, and forms referenced in this guide are
   available from the document stores in the directories listed in the
   URLs (Uniform Resource Locators).  Organizations without connectivity
   wishing to obtain copies of the referenced documents should contact
   their Local IR to arrange postal delivery of one or more of the
   documents.  Note that fees may be associated with the delivery of
   hardcopy versions of documents.

   The document stores can be accessed in two ways:

   1.  Via anonymous FTP (File Transfer Protocol).

   Using your ftp program, connect to the appropriate host computer
   shown below using your email address as the password.  Use the "cd"
   (change directory) command to connect to the appropriate
   subdirectory, then use the "get" command to retrieve the specific
   file.  For example:

   ftp rs.apnic.net (for countries in the Asia/Pacific region)
   ftp rs.arin.net (for countries in the Americas)
   ftp rs.ripe.net (for countries in Europe or North Africa)

      login:  anonymous
      password:  your_email_address

      cd netinfo
      get <domain>_info.txt



Wenzel, et al.               Informational                     [Page 28]

RFC 2901      Administrative Internet Infrastructure Guide   August 2000


   2.  Via electronic mail, ftp, or the World Wide Web.

   Send email to the appropriate address shown below with the message
   body as specified.

   APNIC Documentation

   For APNIC documents and templates, "ftp" to ftp.apnic.net and "cd" to
   /apnic/docs.  APNIC no longer has an electronic mail method of form
   retrieval.  Many of APNIC's request forms are also available on the
   web site at:

      http://www.apnic.net/reg.html

   ARIN Documentation

   For ARIN templates, "ftp" to rs.arin.net and "cd" to /templates.

   You can also obtain templates via the web site at:

      http://www.arin.net/templates.html

   Other ARIN documentation is available at:

      http://www.arin.net/docs.html

   Or send email to:

      [e-mail]

   RIPE Documentation

   For RIPE documents and forms, "ftp" to ftp.ripe.net/ripe and "cd" to
   /docs or cd to /forms.

   Or send email to:

      [e-mail]

   with send help in the body of the message.

Appendix C:     Country Codes

   The International Organization for Standardization (ISO) 3166
   Maintenance Agency and ISO 3166 current list of two-letter country
   codes is available via:

      http://www.iso.ch/infoe/agency/3166-1.htm



Wenzel, et al.               Informational                     [Page 29]

RFC 2901      Administrative Internet Infrastructure Guide   August 2000


Appendix D:     Acronyms

   ANS             Advanced Network Services, Inc.
   ASN             Autonomous System Number
   APNIC           Asia Pacific Network Information Center
   ARIN            American Registry for Internet Numbers
   AS              Autonomous System
   CANET           Canada Net
   CIDR            Classless Inter-Domain Routing
   DNS             Domain Name System
   gTLD            Generic Top-Level Domain
   IANA            Internet Assigned Numbers Authority
   InterNIC        Internet Network Information Center
   IP              Internet Protocol
   IR              Internet Registry
   IRR             Internet Routing Registry
   ISO             International Organization for Standardization
   ISP             Internet Service Provider
   LINX            London Internet Exchange
   NCC             Network Coordination Centre
   NIC             Network Information Center
   NSRC            Network Startup Resource Center
   POP             Point of Presence
   RADB            Routing Arbiter Data Base
   RFC             Request for Comments
   RIPE            Reseaux IP Europeans
   TCP/IP          Transmission Control Protocol/Internet Protocol
   TLD             Top-Level Domain























Wenzel, et al.               Informational                     [Page 30]

RFC 2901      Administrative Internet Infrastructure Guide   August 2000


Full Copyright Statement

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS 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.

Acknowledgement

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



















Wenzel, et al.               Informational                     [Page 31]