As per Relevance of the word structure, we have this rfc below:
Network Working Group Z.
Request for Comments: 2901 J.
FYI: 37 R.
Category: Informational S.
Network Startup Resource
August 2000
Guide to Administrative Procedures of the Internet
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited
Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document describes the administrative procedures for
seeking to connect to the global Internet. This includes the
and operations necessary for address space allocation
registration, routing database registration, and domain
registration. The document also contains information about
required forms and how to obtain them
Table of
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
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
This document is intended for system engineers and technical
of networks who want to make a connection to the Internet.
assumes a basic knowledge of the Internet and networking
This information is intended to help new or expanding
understand and follow the Internet administrative procedures, and
provide assistance in filling out the various templates
registration forms. Appendix D is a glossary of acronyms
Wenzel, et al. Informational [Page 2]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
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
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
This document assumes that you have examined different
for physical connectivity and will assist you in navigating
Internet infrastructure so that you can use that connectivity.
choosing your upstream provider, you should consider their ability
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
organization), you are an Internet end user. You will
want to contact an Internet Service Provider (ISP) for most
your needs. Read section I and the first part of section II
o If you are interested in connecting your organization and
having address space to distribute within your network, you are
Internet high volume end user. You will need more address space
but still may chose to work with an Internet Service
(ISP) for most of your needs. Read sections I and II
o If you are interested in connecting your organization, and
distributing addresses to your clients (who are end users),
are an Internet Service Provider (ISP). You will need to
a Local Internet Registry (if one is available, or your
provider). Read section I and continue reading the rest of
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
and your clients are in turn distributing addresses, you are
Local Internet Registry or large ISP. You will probably need
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
STEP ONE: PREPARE INFORMATION, ORGANIZE HARDWARE, FIGURE OUT TO
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
UUCP or IP. It is preferable to be running the UNIX operating
with TCP/IP over a dedicated line, although you can begin by
UUCP over a dial-up line. Although there are alternatives to UNIX
for historical reasons and robustness UNIX is better prepared
handle Internet connectivity. It is best to use TCP/IP inside
network even if you use another method for your
connectivity
You will need to obtain an Internet Protocol (IP) address, or
of addresses, and a domain name. You may also need an
System Number (ASN) and an IN-ADDR.ARPA (reverse addressing)
name. However, you may begin by having dial-up connectivity
another organization that supports one or more mail exchange (MX
record(s) for your site. This would allow you to receive email
your own domain name without requiring you to invest as
initially
B. What connectivity medium should I choose
You may be constrained by telecommunications regulations in
country as to your choice of dial-up, digital phone lines,
optic cable, or satellite suppliers. If not, cost, bandwidth,
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
person
Choose one person to be the administrative contact and another
to be the technical contact. Write down their full names, email
postal addresses, and telephone and fax numbers (with
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,
local telephone number). The administrative contact should be
member of your organization and must reside in the country.
technical contact should be the key network support person and may
represented initially by someone outside of the country. Note
the technical contact must transition to a network support
residing in the country. The Internet Registries will request
information in the form of database entries called objects.
example, on the RIPE template, the administrative contact should
listed in the admin-c field in the database objects, and
technical contact in the tech-c field in the database objects (
information on database objects follows in section II D below).
2. Determine your cost-recovery charging scheme, if needed, so
you can sustain operations
No form or record will specifically request this, but it is
that you project your costs adequately so that you can assess fees
cover them and ensure stability of operations
3. Diagram your network topology
Determine the number of groups and end users. Describe the size
shape of your current network. Design your addressing plan based
this information. It may be helpful to consider your
chart when doing this, if you anticipate it to be fairly stable
If you are restricted to using the local telecommunications company'
telephone circuit, choose your circuit carrier based on capacity
where it lands geographically. Consider an asymmetric circuit, e.g.,
128kbps in and 64kbps out, if you expect to have more
traffic than outgoing (e.g., if most of the traffic is expected
originate from web servers outside your network).
4. Determine to whom you will connect
See the prerequisites section for types of connection providers
might be appropriate for your situation. Determine which ISP
telecommunications company best fits your connectivity needs
5. Predict your address space and bandwidth requirements from
user needs
Since address space is finite and must be conserved, end users
not permitted to reserve address space. Address space is based
what your needs are and how you justify those needs. Evaluation
IP address space requests is usually based on the documentation
provide for the following 24 months (as per RFC 2050), as
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
submit. Once you have used your assigned address space, you
request additional space based on an updated estimate of growth
your network. This usually includes detailed documentation,
the appropriate regional registry database with details of your
user assignments, and assigning address space both conservatively
efficiently
You will need to justify your needs for address space
communicating your network design and should be prepared to
present your plan for effective use of the request. Determine
current and future user needs. If you are offering virtual
services, it is no longer necessary to assign one IP address
domain. HTTP/1.1 defines the "host" header to allow vanity
without the use of an IP address. Allocations for points of
(POP) throughout your region should also be determined.
of user behavior can be based on analysis of published rates
interviews with individual and institutional subscribers, and
histories of other countries (see "History of the Internet
Thailand"). For example
Area
10 dialup
10 leased lines to organization's LANs (size of the LANs
Area
5 dialup
Main
5 servers: mail, WWW, DNS, FTP, etc
When you design your plan, you should design it for what you
now, what you believe you will need six months from now, and then
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
set up and their connectivity tested using temporary addresses
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
this guide
E. Section
For more information on TCP/IP, see RFC 2151, "A Primer on
and TCP/IP Tools and Utilities".
Wenzel, et al. Informational [Page 6]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
II. Address Space
STEP TWO: OBTAIN ADDRESS SPACE ALLOCATION AND REGISTRATION FROM
ISP YOU ARE CONNECTING TO, OR (AS A LAST RESORT) YOUR
REGISTRY
Internet Protocol (IP) addresses (under the current version 4)
32-bit numbers usually expressed as 4 octets in dotted
notation (for example, 128.223.162.27, which is the IP address
the Network Startup Resource Center (NSRC) web server at the time
this writing). Public IP addresses make up the Internet
space. Addresses are allocated in a hierarchical manner and
designed to be unique
The Internet Assigned Numbers Authority (IANA) allocates
address blocks to the three current Regional Internet
(IRs): ARIN, APNIC, and RIPE NCC which, in turn, allocate
blocks to Local Internet Registries or large ISPs. Local
Registries, which are typically ISPs or collections of
represented at a country level, and large ISPs process the
majority of address space assignments to ISPs and end
Contact the Internet service provider from whom you are getting
connectivity services (your upstream provider) with an
allocation request. It is important and required that you
your upstream provider first, and not the Regional IR automatically
The first question the Regional Registry will ask you is why
cannot get address space from your upstream provider
A. Who is my upstream provider
If there is an ISP already functioning in your country, contact
directly. If you are to be the first connection in your country,
may need to contact your Regional IR in your geographic region,
you should always contact your upstream provider first for
and guidance. Since address allocation is hierarchical,
administrative organizations and procedures also represent
hierarchical structure. It is important not to skip a step in
hierarchy. Current Regional Registries include ARIN (the Americas
Caribbean, and Africa), RIPE (Europe, Africa, and the Middle East),
and APNIC (the Pacific Rim and Asia). Contact information for
organizations is listed in Appendix A
You should contact your Regional Internet Registry if 1) the ISP
are connecting to is unable or unwilling to provide address space,
2) your particular connectivity requirements will result in non-
data to your customers possibly taking a different route over
Internet than data destined for your upstream provider's customers
Wenzel, et al. Informational [Page 7]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
or 3) you anticipate a quick growth rate that may require
your current upstream provider to a larger one and you wish to
the renumbering that such a move would require
B. How much address space should I ask for
Regional IRs typically assign address blocks on the basis of
immediate need and projected utilization rate within one year. (
you are in the ARIN region, it is one year for end user
and three months for ISPs.) Calculate your address space
accordingly. It is recommended to include the organization chart
network topology diagram referred to in section I.C, number 3
(above). Note that address space is allocated based on CIDR
boundaries (see next section). The registries will need
understand your network engineering and deployment plans
significant detail before they can allocate address space
Therefore, the more detailed information you can provide, the
likely your request will be processed quickly
If you obtain address space from your ISP, it is very likely that
will need to renumber should you decide to change upstream
and/or if you grow considerably. As this renumbering may affect
customers (and their customers, etc.) if they are using
lines, you should carefully weigh the cost/benefit involved
obtaining address space from your upstream provider
If you are singly homed, you should obtain your address space
your upstream ISP. If you plan on enlarging but remaining
homed, you should continue to obtain space this way as it
aggregation. If, however, you plan to be multi-homed as part of
growth plan, it would make sense to become a member of an
Regional IR (or, if one exists in your region, a national
Information Center (NIC) and obtain a /19 or "provider aggregatable
address space
The minimum routable block is often a /19, so if you plan
enlarging, it is better to pay the fees to the Regional IR now
obtain a /19 block so that you will not have to renumber later.
that if you are an ISP in the ARIN region, ARIN has
requirements before you can do this in terms of the amount of
space you have previously used, which must be a /21. The
policy is that you must have used a /19 previously from your
ISP before going to ARIN, or you must be multi-homed and show
have used a /21 and be willing to renumber and ARIN will issue a /20
from a reserved /19.
Wenzel, et al. Informational [Page 8]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
As of February 8, 1999, ARIN lowered the minimum allocation size
IP addresses from a /19 to a /20. ARIN will issue
allocations of prefixes no longer than /20. If allocations
than /20 are needed, ISPs and end users should request address
from their upstream provider. ARIN does not guarantee that
will be globally routable
APNIC and RIPE NCC do not have these requirements. For APNIC,
allocations to members will be a /19.
Remember that your upstream provider should route you if you
them. You are a customer of the ISP, so if the service is not
you need you should change ISPs
IF YOU ARE CONNECTED TO ONLY ONE PROVIDER, AND ARE NOT VERY
YET, GET AN ADDRESS RANGE FROM YOUR PROVIDER. SKIP THE REST OF
SECTION AND ALL OF SECTION V
C. What is CIDR
CIDR stands for Classless Inter-Domain Routing. Historically,
addresses were assigned within classes: Class A (8 bits of
address, 24 bits of host address), Class B (16 bits of
address, 16 bits of host address), or Class C (24 bits of
address, 8 bits of host address). With the advent of CIDR,
space is now allocated and assigned on bit boundaries. Using
means you are able to assign addresses corresponding with the
of hosts on the network, thereby conserving address space
The following table illustrates this
Addrs Bits Pref Class
1 0 /32 255.255.255.255
2 1 /31 255.255.255.254
4 2 /30 255.255.255.252
8 3 /29 255.255.255.248
16 4 /28 255.255.255.240
32 5 /27 255.255.255.224
64 6 /26 255.255.255.192
128 7 /25 255.255.255.128
256 8 /24 1C 255.255.255.0
512 9 /23 2C 255.255.254.0
1K 10 /22 4C 255.255.252.0
2K 11 /21 8C 255.255.248.0
4K 12 /20 16C 255.255.240.0
8K 13 /19 32C 255.255.224.0
Wenzel, et al. Informational [Page 9]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Number of addresses available; note that the number
addressable hosts normally is 2 less than this number
the host parts with all equal bits (all 0s, all 1s)
reserved
Size of the allocation/assignment in bits of address space
Length of the prefix covering this address space. This
sometimes used to indicate the size of
allocation/assignment
Size of the address space in terms of class C network numbers
The network mask defining the routing prefix in dotted
notation
(From http://www.ibm.net.il/~hank/cidr.html
D. How do I request and register address space
You will need to send a database object to the appropriate
to request and register address space. The registration
are composed of records that are a series of fields separated by
or more blank lines; each field consists of two parts, the tag
the value. Do not modify the tags in the templates or errors
occur. Values for particular fields are specified in the templates
be careful to enter appropriate information
The first line of a template denotes the record type. For example
an IP address template's first line is inetnum, therefore the
is known as an inetnum object. This first line is also used as
primary key for the record, therefore if you want to modify the
field of the record, the only way to do so is to delete the
entirely and add a new record with the corrected information
For illustration, here is the RIPE inetnum object
inetnum: [IP address range that will be assigned
netname: Network-
descr: Network-Name Communications Company,
admin-c: NIC-handle of administrative
tech-c: NIC-handle of technical
country: ISO 3166-country-
Wenzel, et al. Informational [Page 10]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
rev-srv: ns.someserver.
rev-srv: ns.otherserver.
status: assigned pa (provider aggregatable
or assigned pi (provider independent
changed: email@address.net 960731
source:
For Countries in the APNIC
In order to obtain services from APNIC, you will need to become
member. APNIC-070 is the APNIC Membership Application. It
located at
ftp://ftp.apnic.net/apnic/docs/membership-
Send the completed form via email to APNIC at
member-apply@apnic.
APNIC Address Allocation Requests
Once you have become a member, you can request IP address space
one of the three IP address request forms. If you are
organization that will use address space internally only (e.g.,
enterprises such as universities, government ministries,
corporations, etc.), choose #1 (End User Address Request). If
are an organization that plans to sub-delegate address space
customers (e.g., you are an ISP), choose #2 (ISP Address Request).
If you are a confederation of ISPs (e.g., national NICs, etc.),
choose #3 (Confederation Address Request).
1. APNIC-074 is the APNIC End User Internet Address Request Form
2. APNIC-065 is the APNIC Internet Services Provider
Address Request Form
3. Confederations are a means by which service providers can
together to provide resource allocation and registration
tailored to their specific local language and cultural requirements
For details on how to become an APNIC recognized confederation
please see APNIC Confederation Concepts and Requirements located at
ftp://ftp.apnic.net/apnic/docs/confed-
APNIC-074 is the APNIC Confederation Internet Address Request Form
Wenzel, et al. Informational [Page 11]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Copies of all forms can be found in the following directory
ftp://ftp.apnic.net/apnic/
http://www.apnic.net/reg.
All completed forms should be sent to
hostmaster@apnic.
If there are strong reasons why you cannot obtain address space
your upstream ISP, and you require address space as a one-
allocation only, you can obtain address space as a "non member".
more details, see APNIC-071:
http://ftp.apnic.net/apnic/docs/non-member-
and send the completed form to
billing@apnic.
For Countries in the ARIN
Membership in ARIN is optional and not a requirement for
IP address space from the registry or from your Internet
provider. If you are a large end user organization, choose #1.
you are an ISP, choose #2.
1. The form for network number assignments is located at
ftp://rs.arin.net/templates/networktemplate.
http://www.arin.net/templates/networktemplate.
2. The form for ISPs to obtain a CIDR block of IP network numbers
located at
ftp://rs.arin.net/templates/isptemplate.
http://www.arin.net/templates/isptemplate.
Send either completed form via email to ARIN at
hostmaster@arin.
with "IP request" (if you chose #1) or "ISP CIDR request" (if
chose #2) in the subject field, as appropriate
Wenzel, et al. Informational [Page 12]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
For Countries in the RIPE
RIPE NCC provides IP address space allocation only to
local Internet registries. For a description of the
Internet Registry policies and procedures, see RIPE-159, "
Internet Registry Policies and Procedures". It is located at
ftp://ftp.ripe.net/ripe/docs/ripe-159.
RIPE-160 is Guidelines for Setting up a Local Internet Registry.
is located at
ftp://ftp.ripe.net/docs/ripe-160.
If you have questions regarding setting up a new local IR,
contact the RIPE NCC at
new-lir@ripe.
Once your local IR is established, you will get detailed
on how to submit requests to the RIPE NCC hostmaster
Send the completed form via email to RIPE NCC at
ncc@ripe.
If you have general queries, please contact RIPE NCC at
ncc@ripe.
E. Section
For more information on IP addresses, see RFC 1518, "An
for IP Address Allocation with CIDR" and RFC 2050, "Internet
IP Allocation Guidelines".
III. Autonomous Systems (AS
STEP THREE: IF NEEDED, OBTAIN AN AUTONOMOUS SYSTEM NUMBER
A. What is an ASN and do I need one
Autonomous System Numbers (ASNs) are used to facilitate routing
multi-homed environments. They are allocated when your
policy is different from your provider's. This generally means
site is multi-homed. In nearly all cases, unless you are multi-
to more than one ISP, you will not need an ASN. If your
policy does not differ from your service provider's, you should
Wenzel, et al. Informational [Page 13]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
the service provider's ASN. If there is constant traffic between
and a point in another country, you may want to connect to a
ISP in that country. Note that the resultant multi-homing
makes the system more robust and may also change registry (
therefore request) relationships. It also increases costs greatly
You may have to reduce traffic on your international lines
choosing to connect to a local exchange point. This allows
to stay within your country and off of expensive international links
If you implement this plan, you will be multi-homed and will need
read the autonomous systems and routing sections of this document
B. How do I register an ASN
Since the ASN space is quite limited, request only what you
need when you need it
For Countries in the APNIC
APNIC-066 is the ASN Request Form. The form is located at
http://ftp.apnic.net/apnic/docs/asn-
Send the completed form via email to APNIC at
hostmaster@apnic.
For Countries in the ARIN
A complete listing of assigned ASNs is located at
ftp://rs.arin.net/netinfo/asn.
The ASN registration form is located at
ftp://rs.arin.net/templates/asntemplate.
http://www.arin.net/templates/asntemplate.
Send the completed form via email to ARIN at
hostmaster@arin.
with "ASN request" in the subject field
Wenzel, et al. Informational [Page 14]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
For Countries in the RIPE
The European Autonomous System Number Application Form and
Notes form (RIPE-147) is located at
ftp://ftp.ripe.net/ripe/docs/ripe-147.
Local IRs can send the completed form via email to RIPE at
hostmaster@ripe.
C. Section
For more information on ASNs, see RFC 1930, "Autonomous
(AS)".
IV. Routing and Exchange
STEP FOUR: IF NEEDED, REGISTER WITH A ROUTING DATABASE
A. Do I need to register with a routing database
You do not need to register with a routing database if you are
carrying default routes to your (single) ISP. If you get
address space from an ISP, the ISP will register you. If you
connected to more than one ISP, then you should register with
routing database
The more multi-homed you are, the larger your routing tables need
be. If you are connected to public exchange points (see
below), or to more than one backbone ISP, you need to carry
routing tables and run without a default route
Example European Exchange Points
LINX London Internet
M9-IX Moscow Internet
NIX.CZ Neutral Internet Exchange, Czech
Example Asia/Pacific Exchange Points
AUIX Australia Internet
HKIX Hong Kong Internet
JPIX Japan Internet
Wenzel, et al. Informational [Page 15]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Example Americas Exchange Points
MAE-EAST Metropolitan Area Ethernet -
MAE-WEST Metropolitan Area Ethernet -
PAIX Palo Alto Internet
Depending on the requirements of your international ISP, you may
able to have only a default route to them and specific routes
other suppliers if you have an in-country exchange point. Or
may require that you carry a full set of routes, treating
connection to the in-country exchange point as if it were a multi
homed connection
B. What about CIDR and routing
All registries use CIDR. All major router vendors (Cisco, 3Com
Nortel, Proteon, IBM, etc.) support CIDR. CIDR Internet routers
only the prefix of the destination address to route traffic to
subnetted environment
C. How do I choose a routing database
The Internet Routing Registry (IRR) describes registries
by several national and international networking organizations
These currently include the RIPE Network Coordination Centre (NCC),
ANS (Advanced Network Solutions, Inc.), Bell Canada (
CA*net), Cable and Wireless (CW), and the Routing Arbiter
(RADB). The IRR is a way for ASNs to publicize their own
routing policies without having to request a change from a go
between
"whois" queries to "whois.ra.net" return data that they gather
the entire IRR set of routing registries. Tools such as "peval"
"rtconfig" return data only from the RADB. Thus, when running
tools and desiring data from a set of registries, one must
them as in the following example. "whois" queries to the
configure the precedence of routing databases. For example
@RtConfig set sources = "TEST, RADB, RIPE, ANS, BELL, CW
There are several other registries, such as ALTDB. A list, and
information on RADB, is available at
http://www.radb.net
As of January 1, 2000, the transition to the Routing
Specification Language (RSPL) is complete. RIPE-181
submissions are no longer accepted. For more information, see
Wenzel, et al. Informational [Page 16]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
http://www.merit.edu/radb/announce.
With the exception of the Routing Arbiter Database, each
serves a limited customer base. ANS, Cable and Wireless, and
Canada accept routing registrations for their customers alone,
the RIPE NCC oversees European registrations. The Routing
Database is unique in that it handles registrations for
organizations not covered by the other routing registries.
Routing Arbiter also provides coordination among all the
to ensure consistent representation of routing policies
All Regional IRs need to register with one (only one) of the
databases in the IRR. If you are announcing routes via BGP4, you
to register your routes in the Routing Registry in only one of
IRR's. Logically, this will be the "closest" IRR to you. However
note that some ISPs do not use the regional registries or RADB
D. How do I register in the RADB (The Americas)?
You need to submit three types of database records to the RADB:
or more maintainer objects, an AS object, and one or more
objects
To specify the individuals who are allowed to update your records
the RADB, fill out one or more maintainer objects and send them
email to
db-admin@radb.
You need to submit a maintainer object before you can register any
or route objects
To describe the autonomous system that announces your routes,
out an AS object and submit it via email to
auto-dbm@radb.
AS objects are also called aut-num objects
To register your routes, fill out one or more route objects, and
them to RADB via email to
auto-dbm@radb.
Note that most of the IRR participants have the auto-dbm@xx.net
address function for accepting updates to the IRR automatically
Wenzel, et al. Informational [Page 17]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
E. Section
For more information on routers, see RFC 1812, "Requirements for
Version 4 Routers". See also RFC 1786, "Representation of IP
Policies in a Routing Registry (ripe-181++)".
For more information on CIDR and routing, see RFC 1817, "CIDR
Classful Routing".
V. Domain Name
STEP FIVE: REGISTER YOUR DOMAIN NAME
A. What is a country domain
The Domain Name System (DNS) specifies the naming of computers
a hierarchy. Top-Level Domain (TLD) names include generic
(gTLDs) and two-letter country codes (ccTLDs). Examples of
include .com (commercial), .net (network), and .org (organization).
Examples of two-letter country codes are .ca for Canada, .fr
France, and .id for Indonesia. ISO 3166 is used as a basis
country code top-level domain names. Country codes are assigned
the International Organization for Standardization (ISO)
cooperation with the United Nations. The Internet Assigned
Authority (IANA) directly registers all country-code top-
domains, however it is not involved in the allocation of codes
countries. IANA is a function of the Internet Corporation
Assigned Names and Numbers (ICANN, see Appendix A). See ISO 3166
more information and a current listing of country codes (Appendix C).
A hierarchy of names may, and normally should be, created under
TLD. There is a wide variation in the structure of country domains
In some countries there is a substantial hierarchy, while in
the structure is flat. In some country domains the second levels
generic categories, while in others they are based on geography,
in still others, organization names are listed directly under
country code. Examples of second level generic categories are ac
edu (academic or education), co or com (corporate or commercial),
go or gov (government).
B. How do I register as a country domain
First check that: (1) the domain is still available, few are, (2)
have someone in your country as the administrative contact, and (3)
your name servers are prepared (see RFC 1912 for information
common errors in preparing name servers).
Wenzel, et al. Informational [Page 18]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
The whois master database is the authoritative source of
on .com, .net, .org, and .edu domain name registrations. It
currently maintained by Network Solutions, Inc. and holds
pointers to which whois database contains the record for the
name
To apply to manage a country code top-level domain you should
1. First, if you are on a UNIX host, use the "whois" command to
if the domain is already registered
whois =
2. If the domain does not already have an administrative contact
request a Domain Name Agreement template from IANA by sending
to
iana@iana.
C. What if my country is already registered
If your country is already registered, contact the country-
administrator to register a new second-level domain name
Please note that ARIN, RIPE, and APNIC do not handle domain
(other than IN-ADDR.ARPA). If you want to register a domain
directly under a top-level domain (TLD), please contact
appropriate TLD administrator
D. How do I resolve a country domain name dispute
See RFC 1591 for domain name dispute information. Note that you
need to resolve the dispute within your country before you
IANA
E. Section
For more information on domain names, see RFC 1591, "Domain
System Structure and Delegation"; RFC 1713, "Tools for
Debugging"; and RFC 1912, "Common DNS Operational and
Errors".
VI. IN-ADDR.ARPA Domain
STEP SIX: IF NEEDED, REGISTER YOUR IN-ADDR.ARPA DOMAIN
Wenzel, et al. Informational [Page 19]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
A. What is an IN-ADDR.ARPA domain and do I need one
An IN-ADDR.ARPA domain allows for mapping of IP addresses into
names. This is often referred to as "inverse addressing" because
is the opposite of the domain name to IP address resolution. IN-
domains are represented using the network number in reverse.
example, the IN-ADDR domain for network 123.45.67.0 is represented
67.45.123.in-addr.arpa
You almost always need reverse resolution
B. How do I register an IN-ADDR.ARPA domain
You should ask your upstream provider about registering your IN
ADDR.ARPA domains. If you are working directly with a
registry, see below
For Countries in the APNIC
The IN-ADDR.ARPA Delegation Form is APNIC-064 and is located at
ftp://ftp.apnic.net/apnic/docs/in-addr-
CAUTION: You must set-up your name server to accept the
prior to submission of this form
Send the completed form via email to APNIC at
domreg@rs.apnic.
For Countries in the ARIN
How IN-ADDR.ARPA is registered is dependent on the registration
the block needing reverse entries. For example, all blocks that
been registered directly from the Regional IR may have IN-ADDR.
delegation established by ARIN. In this case, IN-ADDR.
delegations are registered using the ARIN modify template.
template can be found at
ftp://ftp.arin.net/templates/modifytemplate.
http://www.arin.net/templates/modifytemplate.
Instructions for completing the template can be found at the
of the template
CAUTION: Do not list your network number in reverse on the template
Wenzel, et al. Informational [Page 20]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Send the completed form via email to ARIN at
hostmaster@arin.
All blocks that have been reassigned to your organization by an
will have IN-ADDR.ARPA established by your provider. In this case
contact the ISP that reassigned IP address space to your
and coordinate IN-ADDR.ARPA delegation
For Countries in the RIPE
The domain object needs to be entered in the RIPE database
requesting reverse delegation
domain: 0.194.in-addr.
descr: Our organization
admin-c: NIC-handle of administrative contact (e.g., JLC-2RIPE
tech-c: NIC-handle of technical
zone-c: NIC-handle of zone
nserver: Name server (e.g., ns.someserver.net
nserver: ns.otherserver.
nserver: ns.ripe.
changed: email@address.net 960731
source:
NOTE: One of the name servers has to be ns.ripe.
The domain object described above should be included in the request
as well as zone file entries for the zone above the one requested
For example, if a reverse delegation is requested for 1.193.in
addr.arpa, the relevant zone file entries should be included
193.in-addr.arpa; whereas if a reverse delegation is requested
2.2.193.in-addr.arpa, the zone file entries should be included
2.193.in-addr.arpa
Send the completed object(s) via email to RIPE at
auto-inaddr@ripe.
VII.
A. Is there a way to prevent unauthorized changes to my objects
Registries provide various security measures to prevent
changes to your database entries. Contact your regional IR for
information. Note that the contact information you provide in
database object registrations is not private
Wenzel, et al. Informational [Page 21]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
VIII. Network Optimization and
A. How do I optimize traffic on my network
Contact the Cooperative Association for Internet Data
(CAIDA). CAIDA is a collaborative undertaking to promote
cooperation in the engineering and maintenance of a robust,
global Internet infrastructure. CAIDA provides a neutral
to support these cooperative endeavors
The CAIDA web-site is located at
http://www.caida.org
Send email with questions or comments to
info@caida.
Security
Security is discussed in section VII
Thanks to Brian Candler, David Conrad, John Heasley, Kim Hubbard
Daniel Karrenberg, Anne Lord, Dawn Martin, Charles Musisi,
Postel, and April Marine and the IETF User Services Working Group
reviewing various versions of this document; and to Hank
for permission to reprint his table on CIDR
Special thanks are also due to Dr. Steven Goldstein of the
Science Foundation for his contributions and suggestions, and to
National Science Foundation for partial funding of this work
This material is based upon work supported by the National
Foundation under Grant No. NCR-961657. Any opinions, findings,
conclusions or recommendations expressed in this material are
of the author(s) and do not necessarily reflect the views of
National Science Foundation
[1] Malkin, G., "Internet Users' Glossary", FYI 18, RFC 1983,
1996.
[2] Hinden, R., Editor, "Applicability Statement for
Implementation of Classless Inter-Domain Routing (CIDR)",
1517, September 1993.
Wenzel, et al. Informational [Page 22]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
[3] Rekhter, Y. and T. Li, "An Architecture for IP
Allocation with CIDR", RFC 1518, September 1993.
[4] Fuller, V., Li, T., Yu, J. and K. Varadhan, "Classless Inter
Domain Routing (CIDR): an Address Assignment and
Strategy", RFC 1519, September 1993.
[5] Rekhter, Y. and C. Topolcic, "Exchanging Routing
Across Provider Boundaries in the CIDR Environment", RFC 1520,
September 1993.
[6] Postel, J., "Domain Name System Structure and Delegation",
1591, March 1994.
[7] Wijnen, B., Carpenter, G., Curran, K., Sehgal, A. and G. Waters
"Simple Network Management Protocol Distributed
Interface Version 2.0", RFC 1592, March 1994.
[8] Ramao, A., "Tools for DNS debugging", RFC 1713, November 1994.
[9] Baker, F., "Requirements for IP Version 4 Routers", RFC 1812,
June 1995.
[10] Rekhter, Y., "CIDR and Classful Routing", RFC 1817, August 1995.
[11] Barr, D., "Common DNS Operational and Configuration Errors",
1912, February 1996.
[12] Hawkinson, J. and T. Bates, "Guidelines for Creation, Selection
and Registration of an Autonomous System", RFC 1930, March 1996.
[13] Freed, N. and N. Borenstein, "Multipurpose Internet
Extensions (MIME) Part One: Format of Internet Message Bodies",
RFC 2045, November 1996.
[14] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D. and J
Postel, "Internet Registry IP Allocation Guidelines", BCP 12,
RFC 2050, November 1996.
[15] Kessler, G. and S. Shepard, "A Primer On Internet and TCP/
Tools and Utilities", FYI 30, RFC 2151, June 1997.
[16] ISO 3166: "Codes for the Representation of Names of Countries
[17] Palasri, S., Huter, S., and Wenzel, Z. "The History of
Internet in Thailand", University of Oregon Books, 1999.
Wenzel, et al. Informational [Page 23]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Authors'
Zita Wenzel, Ph.D
Network Startup Resource Center (NSRC
1225 Kincaid
1212-University of
Eugene, OR 97403-1212
EMail: zita@nsrc.
John C. Klensin, Ph.D
Network Startup Resource Center (NSRC
1225 Kincaid
1212-University of
Eugene, OR 97403-1212
EMail: klensin@nsrc.
Randy
Network Startup Resource Center (NSRC
1225 Kincaid
1212-University of
Eugene, OR 97403-1212
EMail: randy@nsrc.
Steven
Network Startup Resource Center (NSRC
1225 Kincaid
1212-University of
Eugene, OR 97403-1212
EMail: sghuter@nsrc.
Wenzel, et al. Informational [Page 24]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Appendix A: The Internet
o The Internet Assigned Numbers Authority (IANA
IANA is the central coordinator for the assignment of
parameter values for Internet protocols and for all address space
name space used in the Internet. IANA allocates parts of
Internet address space to Regional Internet Registries (IRs)
distribution to Local IRs and ISPs. IANA is also responsible for
coordination and management of the Domain Name System (DNS).
Note that as of 1999, IANA is a function of the Internet
for Assigned Names and Numbers (ICANN), the non-profit
that is the top-level administration authority of the
Internet
Email: iana@iana.
Postal: 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Telehone: +1-310-823-9358
Fax: +1-310-823-8649
Internet: http://www.iana.org
o Internet Corporation for Assigned Names and Numbers (ICANN
From the ICANN web site
The Internet Corporation for Assigned Names and Numbers (ICANN) is
technical coordination body for the Internet. Created in October 1998
by a broad coalition of the Internet's business, technical, academic
and user communities, ICANN is assuming responsibility for a set
technical functions previously performed under U.S.
contract by IANA and other groups
Specifically, ICANN coordinates the assignment of the
identifiers that must be globally unique for the Internet
function: Internet domain names, IP address numbers,
parameter and port numbers. In addition, ICANN coordinates
stable operation of the Internet's root server system
As a non-profit, private-sector corporation, ICANN is dedicated
preserving the operational stability of the Internet; to
competition; to achieving broad representation of global
communities; and to developing policy through private-sector
bottom-up, consensus-based means. ICANN welcomes the
of any interested Internet user, business, or organization
Wenzel, et al. Informational [Page 25]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Email: icann@icann.
Postal: Internet Corporation for Assigned Names and
(ICANN
4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Telehone: +1-310-823-9358
Fax: +1-310-823-8649
Internet: http://www.icann.org
o
The InterNIC was a cooperative activity between the National
Foundation, General Atomics, AT&T, and Network Solutions, Inc.
joint activity InterNIC no longer exists
Currently, Network Solutions runs the central registry according
the shared registry model specified by ICANN for registration
second-level domain names under the generic top-
domains .com, .net, and .org
For information on accredited registrars for .com, .net, and .org
please see
http://www.icann.org/registrars/accredited-list.
(note that Network Solutions is an accredited registrar as well
the entity running the registry).
Email: hostmaster@netsol.
Postal: Network Solutions, Inc
505 Huntmar Park Dr
Herndon, VA 20170
Telephone: +1-703-742-4777
Fax: +1-703-742-9552
Internet: http://www.networksolutions.com
Regional Internet Registries (IRs
Regional IRs operate in large geopolitical regions such
continents. Currently, there are three Regional IRs: ARIN for
Americas, the Caribbean, and Africa; RIPE NCC for Europe, Africa,
the Middle East; and APNIC for the Asia Pacific region. The
duties of the Regional IRs include coordination and representation
all local Internet Registries in their respective region
Wenzel, et al. Informational [Page 26]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
o
Asia Pacific Network Information Center (APNIC) is a non-
Internet registry for the Asia Pacific region. APNIC provides
address allocation, Autonomous System Number (ASN) assignment,
IN-ADDR.ARPA registration
Email: hostmaster@apnic.
Postal: APNIC Box 2131
Milton Queensland 4064
Telephone: +61-7-3367-0490
Fax: +61-7-3367-0482
Internet: http://www.apnic.net
o
The American Registry for Internet Numbers (ARIN) is a non-
Internet registry that was established for the purpose
administration and registration of Internet Protocol (IP) numbers
the geographical areas that were previously managed by
Solutions, Inc. These areas include, but are not limited to,
America, South America, Africa, and the Caribbean region.
provides IP address allocation, Autonomous System Number (ASN
assignment, and IN-ADDR.ARPA registration
Email: hostmaster@arin.
Postal: 4506 Daly
Suite 200
Chantilly, VA 20151
Telephone: +1-703-227-0660
Fax +1-703-227-0676
Internet: http://www.arin.net
o RIPE
Reseaux IP Europens Network Coordination Centre (RIPE NCC) is a non
profit Internet registry for the European, North African, and
East regions. RIPE NCC provides IP address allocation,
System Number (ASN) assignment, and IN-ADDR.ARPA registration
Email: ncc@ripe.
Postal: Singel 258
1016 AB
The
Phone: +31-20-535-4444
Fax: +31-20-535-4445
Internet: http://www.ripe.net
Wenzel, et al. Informational [Page 27]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Appendix B:
Internet
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
by sending an email message to
rfc-info@rfc-editor.
with the message body help: ways_to_get_rfcs. For example
To: rfc-info@isi.
Subject: getting
help: ways_to_get_
Documents, Templates, and
The documents, templates, and forms referenced in this guide
available from the document stores in the directories listed in
URLs (Uniform Resource Locators). Organizations without
wishing to obtain copies of the referenced documents should
their Local IR to arrange postal delivery of one or more of
documents. Note that fees may be associated with the delivery
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
shown below using your email address as the password. Use the "cd
(change directory) command to connect to the
subdirectory, then use the "get" command to retrieve the
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:
password: your_email_
cd
get _info.
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
body as specified
APNIC
For APNIC documents and templates, "ftp" to ftp.apnic.net and "cd"
/apnic/docs. APNIC no longer has an electronic mail method of
retrieval. Many of APNIC's request forms are also available on
web site at
http://www.apnic.net/reg.
ARIN
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.
Other ARIN documentation is available at
http://www.arin.net/docs.
Or send email to
hostmaster@arin.
RIPE
For RIPE documents and forms, "ftp" to ftp.ripe.net/ripe and "cd"
/docs or cd to /forms
Or send email to
mail-server@ripe.
with send help in the body of the message
Appendix C: Country
The International Organization for Standardization (ISO) 3166
Maintenance Agency and ISO 3166 current list of two-letter
codes is available via
http://www.iso.ch/infoe/agency/3166-1.
Wenzel, et al. Informational [Page 29]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Appendix D:
ANS Advanced Network Services, Inc
ASN Autonomous System
APNIC Asia Pacific Network Information
ARIN American Registry for Internet
AS Autonomous
CANET Canada
CIDR Classless Inter-Domain
DNS Domain Name
gTLD Generic Top-Level
IANA Internet Assigned Numbers
InterNIC Internet Network Information
IP Internet
IR Internet
IRR Internet Routing
ISO International Organization for
ISP Internet Service
LINX London Internet
NCC Network Coordination
NIC Network Information
NSRC Network Startup Resource
POP Point of
RADB Routing Arbiter Data
RFC Request for
RIPE Reseaux IP
TCP/IP Transmission Control Protocol/Internet
TLD Top-Level
Wenzel, et al. Informational [Page 30]
RFC 2901 Administrative Internet Infrastructure Guide August 2000
Full Copyright
Copyright (C) The Internet Society (2000). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Wenzel, et al. Informational [Page 31]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other