Network Working Group
Updates: RFCs 1034, 1035
This RFC proposes two extensions to the Domain Name System:
The method for mapping between network names and addresses is a proposed standard, the ideas for a general method are experimental.
This RFC assumes that the reader is familiar with the DNS [RFC 1034, RFC 1035] and its use. The data shown is for pedagogical use and does not necessarily reflect the real Internet.
Distribution of this memo is unlimited.
The DNS is extensible and can be used for a virtually unlimited number of data types, name spaces, etc. New type definitions are occasionally necessary as are revisions or deletions of old types (e.g., MX replacement of MD and MF [RFC 974]), and changes described in [RFC 973]. This RFC describes changes due to the general need to map between identifiers and values, and a specific need for network name support.
Users wish to be able to use the DNS to map between network names and numbers. This need is the only capability found in HOSTS.TXT which is not available from the DNS. In designing a method to do this, there were two major areas of concern:
It was impossible to reconcile these two areas of concern for network names because of the desire to unify network number support within existing IP address to host name support. The existing support is the IN-ADDR.ARPA section of the DNS name space. As a result this RFC describes one structure for network names which builds on the existing support for host names, and another family of structures for future yellow pages (YP) functions such as conversions between TCP- port numbers and mnemonics.
Both structures are described in following sections. Each structure has a discussion of design issues and specific structure recommendations.
We wish to avoid defining structures and methods which can work but do not because of indifference or errors on the part of system administrators when maintaining the database. The WKS RR is an example. Thus, while we favor distribution as a general method, we also recognize that centrally maintained tables (such as HOSTS.TXT) are usually more consistent though less maintainable and timely. Hence we recommend both specific methods for mapping network names, addresses, and subnets, as well as an instance of the general method for mapping between allocated network numbers and network names. (Allocation is centrally performed by the SRI Network Information Center, aka the NIC).
The issues involved in the design were the definition of network name syntax, the mappings to be provided, and possible support for similar functions at the subnet level.
The current syntax for network names, as defined by [RFC 952] is an alphanumeric string of up to 24 characters, which begins with an alpha, and may include "." and "-" except as first and last characters. This is the format which was also used for host names before the DNS. Upward compatibility with existing names might be a goal of any new scheme.
However, the present syntax has been used to define a flat name space, and hence would prohibit the same distributed name allocation method used for host names. There is some sentiment for allowing the NIC to continue to allocate and regulate network names, much as it allocates numbers, but the majority opinion favors local control of network names. Although it would be possible to provide a flat space or a name space in which, for example, the last label of a domain name captured the old-style network name, any such approach would add complexity to the method and create different rules for network names and host names.
For these reasons, we assume that the syntax of network names will be the same as the expanded syntax for host names permitted in [HR]. The new syntax expands the set of names to allow leading digits, so long as the resulting representations do not conflict with IP addresses in decimal octet form. For example, 3Com.COM and 3M.COM are now legal, although 184.108.40.206.COM is not. See [HR] for details.
The price is that network names will get as complicated as host names. An administrator will be able to create network names in any domain under his control, and also create network number to name entries in IN-ADDR.ARPA domains under his control. Thus, the name for the ARPANET might become NET.ARPA, ARPANET.ARPA or Arpa- network.MIL., depending on the preferences of the owner.
The desired mappings, ranked by priority with most important first, are:
The network name syntax discussed above can provide domain names which will contain mappings from network names to various quantities, but we also need a section of the name space, organized by network and subnet number to hold the inverse mappings.
The choices include:
The proposed solution uses information stored at:
Names in the IN-ADDR.ARPA tree that correspond to host-zero IP
addresses. The same method is used for subnets in a nested
fashion. For example, 0.0.0.10.IN-ADDR.ARPA. for net 10.
Two types of information are stored here: PTR RRs which point to the network name in their data sections, and A RRs, which are present if the network (or subnet) is subnetted further. If a type A RR is present, then it has the address mask as its data. The general form is:
<reversed-host-zero-number>.IN-ADDR.ARPA. PTR <network-name> <reversed-host-zero-number>.IN-ADDR.ARPA. A <subnet-mask> For example: 0.0.0.10.IN-ADDR.ARPA. PTR ARPANET.ARPA. or 0.0.2.128.IN-ADDR.ARPA. PTR cmu-net.cmu.edu. A 255.255.255.0In general, this information will be added to an existing master file for some IN-ADDR.ARPA domain for each network involved. Similar RRs can be used at host-zero subnet entries.
<network-name> ptr <reversed-host-zero-number>.IN-ADDR.ARPA For example: ARPANET.ARPA. PTR 0.0.0.10.IN-ADDR.ARPA. or isi-net.isi.edu. PTR 0.0.9.128.IN-ADDR.ARPA.In general, this information will be inserted in the master file for the domain name of the organization; this is a different file from that which holds the information below IN-ADDR.ARPA. Similar PTR RRs can be used at subnet names.
Names corresponding to organizations.
The data here is one or more PTR RRs pointing at the IN-ADDR.ARPA names corresponding to host-zero entries for networks.
ISI.EDU. PTR 0.0.9.128.IN-ADDR.ARPA. MCC.COM. PTR 0.167.5.192.IN-ADDR.ARPA. PTR 0.168.5.192.IN-ADDR.ARPA. PTR 0.169.5.192.IN-ADDR.ARPA. PTR 0.0.62.128.IN-ADDR.ARPA.
The ARPANET is a Class A network without subnets. The RRs which would be added, assuming the ARPANET.ARPA was selected as a network name, would be:
ARPA. PTR 0.0.0.10.IN-ADDR.ARPA. ARPANET.ARPA. PTR 0.0.0.10.IN-ADDR.ARPA. 0.0.0.10.IN-ADDR.ARPA. PTR ARPANET.ARPA.
The first RR states that the organization named ARPA owns net 10 (It might also own more network numbers, and these would be represented with an additional RR per net.) The second states that the network name ARPANET.ARPA. maps to net 10. The last states that net 10 is named ARPANET.ARPA.
Note that all of the usual host and corresponding IN-ADDR.ARPA entries would still be required.
The ISI network is 128.9, a class B number. Suppose the ISI network was organized into two levels of subnet, with the first level using an additional 8 bits of address, and the second level using 4 bits, for address masks of x'FFFFFF00' and X'FFFFFFF0'.
Then the following RRs would be entered in ISI's master file for the ISI.EDU zone:
; Define network entry isi-net.isi.edu. PTR 0.0.9.128.IN-ADDR.ARPA. ; Define first level subnets div1-subnet.isi.edu. PTR 0.1.9.128.IN-ADDR.ARPA. div2-subnet.isi.edu. PTR 0.2.9.128.IN-ADDR.ARPA. ; Define second level subnets inc-subsubnet.isi.edu. PTR 220.127.116.11.IN-ADDR.ARPA. in the 9.128.IN-ADDR.ARPA zone: ; Define network number and address mask 0.0.9.128.IN-ADDR.ARPA. PTR isi-net.isi.edu. A 255.255.255.0 ;aka X'FFFFFF00' ; Define one of the first level subnet numbers and masks 0.1.9.128.IN-ADDR.ARPA. PTR div1-subnet.isi.edu. A 255.255.255.240 ;aka X'FFFFFFF0' ; Define another first level subnet number and mask 0.2.9.128.IN-ADDR.ARPA. PTR div2-subnet.isi.edu. A 255.255.255.240 ;aka X'FFFFFFF0' ; Define second level subnet number 18.104.22.168.IN-ADDR.ARPA. PTR inc-subsubnet.isi.edu.
This assumes that the ISI network is named isi-net.isi.edu., first level subnets are named div1-subnet.isi.edu. and div2-subnet.isi.edu., and a second level subnet is called inc-subsubnet.isi.edu. (In a real system as complicated as this there would be more first and second level subnets defined, but we have shown enough to illustrate the ideas.)
Depending on whether the IP address is class A, B, or C, mask off the high one, two, or three bytes, respectively. Reverse the octets, suffix IN-ADDR.ARPA, and do a PTR query.
For example, suppose the IP address is 10.0.0.51.
0.0.0.10.IN-ADDR.ARPA. PTR ARPANET.ARPA.
Suppose that the IP address is 22.214.171.124.
0.0.9.128.IN-ADDR.ARPA. PTR isi-net.isi.edu
This is a simple extension of the IP address to network name method. When the network entry is located, do a lookup for a possible A RR. If the A RR is found, look up the next level of subnet using the original IP address and the mask in the A RR. Repeat this procedure until no A RR is found.
For example, repeating the use of 126.96.36.199.
0.0.9.128.IN-ADDR.ARPA. PTR isi-net.isi.edu. A 255.255.255.0
0.2.9.128.IN-ADDR.ARPA. PTR div2-subnet.isi.edu. A 255.255.255.240
188.8.131.52.IN-ADDR.ARPA. PTR inc-subsubnet.isi.edu.
The term "Yellow Pages" is used in almost as many ways as the term "domain", so it is useful to define what is meant herein by YP. The general problem to be solved is to create a method for creating mappings from one kind of identifier to another, often with an inverse capability. The traditional methods are to search or use a precomputed index of some kind.
Searching is impractical when the search is too large, and precomputed indexes are possible only when it is possible to specify search criteria in advance, and pay for the resources necessary to build the index. For example, it is impractical to search the entire domain tree to find a particular address RR, so we build the IN- ADDR.ARPA YP. Similarly, we could never build an Internet-wide index of "hosts with a load average of less than 2" in less time than it would take for the data to change, so indexes are a useless approach for that problem.
Such a precomputed index is what we mean by YP, and we regard the IN-ADDR.ARPA domain as the first instance of a YP in the DNS. Although a single, centrally-managed YP for well-known values such as TCP-port is desirable, we regard organization-specific YPs for, say, locally defined TCP ports as a natural extension, as are combinations of YPs using search lists to merge the two.
In examining Internet Numbers [RFC 997] and Assigned Numbers [RFC 1010], it is clear that there are several mappings which might be of value. For example:
<assigned-network-name> <==> <IP-address> <autonomous-system-id> <==> <number> <protocol-id> <==> <number> <port-id> <==> <number> <ethernet-type> <==> <number> <public-data-net> <==> <IP-address>
Following the IN-ADDR example, the YP takes the form of a domain tree organized to optimize retrieval by search key and distribution via normal DNS rules. The name used as a key must include:
This ordering reflects the natural scoping of control, and hence the order of the components in a domain name. Thus domain names would be of the form:
To make this work, we need to define well-know strings for each of these metavariables, as well as encoding rules for converting a <from-value> into a domain name. We might define:
<YP-origin> :=YP <from-data-type>:=TCP-port | IN-ADDR | Number | Assigned-network-number | Name <to-data-type> :=<from-data-type>
Note that "YP" is NOT a valid country code under [ISO 3166] (although we may want to worry about the future), and the existence of a syntactically valid <to-data-type>. <from-data-type> pair does not imply that a meaningful mapping exists, or is even possible.
The encoding rules might be:
$origin Number.TCP-port.YP. 23 PTR TELNET.TCP-port.Number.YP. 25 PTR SMTP.TCP-port.Number.YP. $origin TCP-port.Number.YP. TELNET PTR 23.Number.TCP-port.YP. SMTP PTR 25.Number.TCP-port.YP.
Thus the mapping between 23 and TELNET is represented by a pair of PTR RRs, one for each direction of the mapping.
Network numbers are assigned by the NIC and reported in "Internet Numbers" RFCs. To create a YP, the NIC would set up two domains:
Name.Assigned-network-number.YP and Assigned-network-number.YPThe first would contain entries of the form:
$origin Name.Assigned-network-number.YP. 0.0.0.4 PTR SATNET.Assigned-network-number.Name.YP. 0.0.0.10 PTR ARPANET.Assigned-network-number.Name.YP.The second would contain entries of the form:
$origin Assigned-network-number.Name.YP. SATNET. PTR 0.0.0.4.Name.Assigned-network-number.YP. ARPANET. PTR 0.0.0.10.Name.Assigned-network-number.YP.
These YPs are not in conflict with the network name support described in the first half of this RFC since they map between ASSIGNED network names and numbers, not those allocated by the organizations themselves. That is, they document the NIC's decisions about allocating network numbers but do not automatically track any renaming performed by the new owners.
As a practical matter, we might want to create both of these domains to enable users on the Internet to experiment with centrally maintained support as well as the distributed version, or might want to implement only the allocated number to name mapping and request organizations to convert their allocated network names to the network names described in the distributed model.
We could imagine that all conversion routines using these YPs might be instructed to use "YP.<local-domain>" followed by "YP." as a search list. Thus, if the organization ISI.EDU wished to define locally meaningful TCP-PORT, it would define the domains:
<TCP-port.Number.YP.ISI.EDU> and <Number.TCP-port.YP.ISI.EDU>.We could add another level of indirection in the YP lookup, defining the <to-data-type>.<from-data-type>.<YP-origin> nodes to point to the YP tree, rather than being the YP tree directly. This would enable entries of the form:
IN-ADDR.Netname.YP. PTR IN-ADDR.ARPA.to splice in YPs from other origins or existing spaces.
Another possibility would be to shorten the RDATA section of the RRs which map back and forth by deleting the origin. This could be done either by allowing the domain name in the RDATA portion to not identify a real domain name, or by defining a new RR which used a simple text string rather than a domain name.
Thus, we might replace
$origin Assigned-network-number.Name.YP. SATNET. PTR 0.0.0.4.Name.Assigned-network-number.YP. ARPANET. PTR 0.0.0.10.Name.Assigned-network-number.YP.with
$origin Assigned-network-number.Name.YP. SATNET. PTR 0.0.0.4. ARPANET. PTR 0.0.0.10. or $origin Assigned-network-number.Name.YP. SATNET. PTT "0.0.0.4" ARPANET. PTT "0.0.0.10"where PTT is a new type whose RDATA section is a text string.
Drew Perkins, Mark Lottor, and Rob Austein contributed several of the ideas in this RFC. Numerous contributions, criticisms, and compromises were produced in the IETF Domain working group and the NAMEDROPPERS mailing list.
Author's Address:Paul Mockapetris