rfc2901.txt

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

Network Working Group                                          Z. Wenzel
Request for Comments: 2901                                    J. Klensin
FYI: 37                                                          R. Bush
Category: Informational                                         S. Huter
                                         Network Startup Resource Center
                                                             August 2000


   Guide to Administrative Procedures of the Internet Infrastructure

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

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

Abstract

   This document describes the administrative procedures for networks
   seeking to connect to the global Internet.  This includes the steps
   and operations necessary for address space allocation and
   registration, routing database registration, and domain name
   registration.  The document also contains information about the
   required forms and how to obtain them.

Table of Contents

   Who Should Read This Document ...................................  2
   Checklist .......................................................  3
   Prerequisites ...................................................  3
   I.    Preparation of Systems and Network Planning ...............  4
           A.  What do I need to connect to the Internet? ..........  4
           B.  What connectivity medium should I choose? ...........  4
           C.  What else do I need to do? ..........................  4
           D.  How do I get the documents referred to in this guide?  6
           E.  Section References ..................................  6
   II.   Address Space Allocation ..................................  7
           A.  Who is my upstream provider? ........................  7
           B.  How much address space should I ask for? ............  8
           C.  What is CIDR? .......................................  9
           D.  How do I request and register address space? ........ 10
           E.  Section References .................................. 13





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


   III.  Autonomous Systems (AS) ................................... 13
           A.  What is an ASN and do I need one? ................... 13
           B.  How do I register an ASN? ........................... 14
           C.  Section References .................................. 15
   IV.   Routing and Exchange Points ............................... 15
           A.  Do I need to register with a routing database? ...... 15
           B.  What about CIDR and routing? ........................ 16
           C.  How do I choose a routing database? ................. 16
           D.  How do I register in the RADB (The Americas)? ....... 17
           E.  Section References .................................. 18
   V.    Domain Name Registration .................................. 18
           A.  What is a country domain? ........................... 18
           B.  How do I register as a country domain? .............. 18
           C.  What if my country is already registered? ........... 19
           D.  How do I resolve a country domain name dispute? ..... 19
           E.  Section References .................................. 19
   VI.   IN-ADDR.ARPA Domain Delegation ............................ 19
           A.  What is an IN-ADDR.ARPA domain and do I need one? ... 20
           B.  How do I register an IN-ADDR.ARPA domain? ........... 20
   VII.  Security .................................................. 21
           A.  Is there a way to prevent unauthorized changes to my
           objects? ................................................ 21
   VIII. Network Optimization and Management ....................... 22
           A.  How do I optimize traffic on my network? ............ 22
   Security Considerations ......................................... 22
   Acknowledgements ................................................ 22
   References ...................................................... 22
   Authors' Addresses .............................................. 24
   Appendix A:  The Internet Agencies .............................. 25
   Appendix B:  Documentation ...................................... 28
   Appendix C:  Country Codes ...................................... 29
   Appendix D:  Acronyms ........................................... 30
   Full Copyright Statement ........................................ 31

Who Should Read This Document

   This document is intended for system engineers and technical managers
   of networks who want to make a connection to the Internet.  It
   assumes a basic knowledge of the Internet and networking.

   This information is intended to help new or expanding networks
   understand and follow the Internet administrative procedures, and to
   provide assistance in filling out the various templates and
   registration forms.  Appendix D is a glossary of acronyms.







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


Checklist

   This document will explain the following procedures:

   o  Determine your organization type and current status.
   o  Determine your administrative and technical contacts.
   o  Determine your budget (and chargeback system) and choice of
      carriers.
   o  Determine to whom you will connect.
   o  Predict your current and projected address space needs.
   o  Set-up your system to connect.
   o  Request and register your address space allocation.
   o  Request and register an autonomous system number, if needed.
   o  Register with a routing database, if needed.
   o  Register your country's domain name, if needed.
   o  Request and register your IN-ADDR.ARPA domain name, if needed.

Prerequisites

   This document assumes that you have examined different alternatives
   for physical connectivity and will assist you in navigating the
   Internet infrastructure so that you can use that connectivity. In
   choosing your upstream provider, you should consider their ability to
   deal with the Internet infrastructure.

   What will you be doing and what role will you play?

   o  If you are interested in connecting yourself (or a small
      organization), you are an Internet end user.  You will probably
      want to contact an Internet Service Provider (ISP) for most of
      your needs.  Read section I and the first part of section II.

   o  If you are interested in connecting your organization and in
      having address space to distribute within your network, you are an
      Internet high volume end user.  You will need more address space,
      but still may chose to work with an Internet Service Provider
      (ISP) for most of your needs.  Read sections I and II.

   o  If you are interested in connecting your organization, and in
      distributing addresses to your clients (who are end users), you
      are an Internet Service Provider (ISP).  You will need to contact
      a Local Internet Registry (if one is available, or your upstream
      provider).  Read section I and continue reading the rest of this
      document.







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


   o  If you are interested in distributing addresses to your clients
      and your clients are in turn distributing addresses, you are a
      Local Internet Registry or large ISP.  You will probably need to
      contact the Regional Internet Registry in your geographical area.
      Read section I and continue reading the rest of this document.

I.      Preparation of Systems and Network Planning

   STEP ONE: PREPARE INFORMATION, ORGANIZE HARDWARE, FIGURE OUT TO WHOM
   YOU WILL CONNECT, AND TEST IN-COUNTRY SYSTEMS.

A.  What do I need to connect to the Internet?

   You can connect using dial-up or dedicated lines, and you can choose
   UUCP or IP.  It is preferable to be running the UNIX operating system
   with TCP/IP over a dedicated line, although you can begin by using
   UUCP over a dial-up line.  Although there are alternatives to UNIX,
   for historical reasons and robustness UNIX is better prepared to
   handle Internet connectivity.  It is best to use TCP/IP inside your
   network even if you use another method for your external
   connectivity.

   You will need to obtain an Internet Protocol (IP) address, or block
   of addresses, and a domain name.  You may also need an Autonomous
   System Number (ASN) and an IN-ADDR.ARPA (reverse addressing) domain
   name.  However, you may begin by having dial-up connectivity to
   another organization that supports one or more mail exchange (MX)
   record(s) for your site.  This would allow you to receive email at
   your own domain name without requiring you to invest as much
   initially.

B.  What connectivity medium should I choose?

   You may be constrained by telecommunications regulations in your
   country as to your choice of dial-up, digital phone lines, fiber
   optic cable, or satellite suppliers.  If not, cost, bandwidth, and
   reliability will determine your choice.

C.  What else do I need to do?

   Before you do anything else:

   1. Designate an administrative contact person and a technical contact
   person.

   Choose one person to be the administrative contact and another person
   to be the technical contact.  Write down their full names, email and
   postal addresses, and telephone and fax numbers (with country



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


   prefixes in the form + country code (e.g., +011), city code, and
   local telephone number).  The administrative contact should be a
   member of your organization and must reside in the country.  The
   technical contact should be the key network support person and may be
   represented initially by someone outside of the country.  Note that
   the technical contact must transition to a network support person
   residing in the country.  The Internet Registries will request this
   information in the form of database entries called objects.  For
   example, on the RIPE template, the administrative contact should be
   listed in the admin-c field in the database objects, and the
   technical contact in the tech-c field in the database objects (more
   information on database objects follows in section II D below).

   2. Determine your cost-recovery charging scheme, if needed, so that
   you can sustain operations.

   No form or record will specifically request this, but it is important
   that you project your costs adequately so that you can assess fees to
   cover them and ensure stability of operations.

   3. Diagram your network topology.

   Determine the number of groups and end users.  Describe the size and
   shape of your current network.  Design your addressing plan based on
   this information.  It may be helpful to consider your organization
   chart when doing this, if you anticipate it to be fairly stable.

   If you are restricted to using the local telecommunications company's
   telephone circuit, choose your circuit carrier based on capacity and
   where it lands geographically.  Consider an asymmetric circuit, e.g.,
   128kbps in and 64kbps out, if you expect to have more incoming
   traffic than outgoing (e.g., if most of the traffic is expected to
   originate from web servers outside your network).

   4.  Determine to whom you will connect.

   See the prerequisites section for types of connection providers that
   might be appropriate for your situation.  Determine which ISP or
   telecommunications company best fits your connectivity needs.

   5.  Predict your address space and bandwidth requirements from end
   user needs.

   Since address space is finite and must be conserved, end users are
   not permitted to reserve address space.  Address space is based on
   what your needs are and how you justify those needs.  Evaluation of
   IP address space requests is usually based on the documentation you
   provide for the following 24 months (as per RFC 2050), as specified



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


   in the address space usage template and in the addressing plan you
   submit.  Once you have used your assigned address space, you can
   request additional space based on an updated estimate of growth in
   your network.  This usually includes detailed documentation, updating
   the appropriate regional registry database with details of your end
   user assignments, and assigning address space both conservatively and
   efficiently.

   You will need to justify your needs for address space by
   communicating your network design and should be prepared to clearly
   present your plan for effective use of the request.  Determine your
   current and future user needs.  If you are offering virtual web
   services, it is no longer necessary to assign one IP address per
   domain.  HTTP/1.1 defines the "host" header to allow vanity names
   without the use of an IP address.  Allocations for points of presence
   (POP) throughout your region should also be determined.  Predictions
   of user behavior can be based on analysis of published rates,
   interviews with individual and institutional subscribers, and case
   histories of other countries (see "History of the Internet in
   Thailand").  For example,

      Area1
        10 dialup modems
        10 leased lines to organization's LANs (size of the LANs)
      Area2
         5 dialup modems
      Main POP
         5 servers: mail, WWW, DNS, FTP, etc.

   When you design your plan, you should design it for what you need
   now, what you believe you will need six months from now, and then one
   year and two years from now.

   6.  Set up, connect, and test your hardware and software.

   It is important to ensure that you have enough representative systems
   set up and their connectivity tested using temporary addresses before
   contacting the appropriate agency for address space.

D.  How do I get the documents referred to in this guide?

   See Appendix B for details on obtaining the documents referred to in
   this guide.

E.  Section References

   For more information on TCP/IP, see RFC 2151, "A Primer on Internet
   and TCP/IP Tools and Utilities".



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


II.     Address Space Allocation

   STEP TWO: OBTAIN ADDRESS SPACE ALLOCATION AND REGISTRATION FROM THE
   ISP YOU ARE CONNECTING TO, OR (AS A LAST RESORT) YOUR REGIONAL
   REGISTRY.