|
Some of the templates include:
- • Template for contact registration:
This template is used to add, change, or delete a person who is to be registered in the InterNIC database as the main contact for a certain domain.
- • Template for requesting an ISP CIDR4 block:
4CIDR will be discussed further in Chapter 3, "Handling IP Address Depletion."
This is a template targeted for ISPs as part of the process in obtaining CIDR blocks of Internet Protocol (IP) network numbers. The template requests information on how the ISP is connected to the Internet and what, if any, IP blocks were previously allocated to it. This information is reviewed for efficient utilization prior to allocating additional addresses. The ISP has to allocate a technical Point Of Contact (POC) and indicate its network name, organization and geographic location, size of the block requested, and portable/nonportable address space.
The information about portable and nonportable address space is requested to monitor the usage of IP address space. The portable option indicates that the ISP enables its customer to keep the IP address space in case the customer changes providers; the nonportable option indicates that the ISP requires its customers to return the IP address (and hence renumber) when the customer changes providers.
The ISP is also required to provide at least two independent servers for translating address-to-name mapping for hosts in the domain (DNS). The servers should be in physically separate locations and on different networks if possible. A new form for IN-ADDR domain modification should be supplied.
- • Template for requesting Internet Protocol (IP) numbers:
This template must be completed as part of the application process for obtaining Internet Protocol (IP) network numbers. Due to policy constraints on IP address number assignments, users are urged to take their IP addresses from their direct ISPs. IP addresses taken directly from the InterNIC might be subject to policies and might not be routable on the Internet.
Customers should provide an explanation of their Internet connection. In case of a connection to a provider, the customer should contact the provider for IP addresses. A technical POC should be provided, along with a network name, an organization name, type of network (research, educational, and so on), location and postal address, and a justification for the size of IP space requested.
In case 16 class C or more addresses are required, a network topology plan should be provided. In case a class B is requested (256 Cs), the whole network diagram should be included.
- • Template for host registration:
This template is used to register a new name server in the ISP's domain. The template could be used to add, change, or delete the host records from the InterNIC database.
- • Template for requesting Autonomous System (AS) numbers:
An Autonomous System is a group of IP networks/routers sharing the same policies. An AS number is an integer between 1 and 65535 with the range 64512 through 65535 reserved for private use. Due to the finite number of available AS numbers, justification should be presented before an organization is given an AS number. Today, the IANA is enforcing a policy whereby organizations connecting to a single provider and sharing the same policies as their providers use an AS number from the private pool. These private ASs can then be stripped at the provider level. Organizations connecting to multiple providers can request an AS number from the public pool.
Organizations that qualify for getting an AS number should provide an AS name, an organization name, and a technical point of contact.
- • Template to register, delete, or modify an IN-ADDR domain:
The Internet uses a special domain to support address-to-name mapping, referred to as inverse-addressing (IN-ADDR). IN-ADDR domains are represented using the network number in reverse. The IN-ADDR domain for network 192.213.11.0, for example, is 11.213.192.IN-ADDR.ARPA.
The template indicates whether this is a new IN-ADDR registration, a modification, or a deletion of an existing IN-ADDR.
- • Template for requesting or modifying Domain Name records:
This template is used for registering new domain names, making changes to existing domain name records, and removing domain names from the InterNIC database and root servers. The template asks for the purpose of the registration, with a justification for the domain name (com, edu, and so on) and a complete domain name according to RFC 1591 (ex: ABC.COM). RFC 1591 describes the distinction between different domains, for example:
- • GOV is for United States federal government agencies.
- • EDU is for four-year, degree-granting institutions.
- • NET is for network infrastructure machines and organizations.
- • COM is for commercial, for-profit organizations.
- • ORG is for nonprofit organizations.
U.S. state and local government agencies, schools, libraries, museums, and individuals should register under the U.S. domain as described in RFC 1480.
GOV registrations are limited to top-level U.S. Federal Government agencies per RFC 1816.
The template also includes the name of the organization (or individual) using the domain name and the administrative, technical, and billing contacts.
Each domain must provide at least two independent DNSs, which need to be active before the application is submitted.
|