network
Click on the red underlined text to get to the source
... 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
...
... Several tradeoffs involving control of network names, the
syntax of network names, backward compatibility ...
... Several tradeoffs involving control of network names, the
syntax of network names, backward compatibility, etc. ...
...
It was impossible to reconcile these two areas of concern for network
names because of the desire to unify network number support within
...
... 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 ...
... 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
...
... are usually more consistent though less maintainable and timely.
Hence we recommend both specific methods for mapping network names,
addresses, and subnets ...
... 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 ...
... method
for mapping between allocated network numbers and network names.
(Allocation is centrally performed by the SRI Network Information
...
... network numbers and network names.
(Allocation is centrally performed by the SRI Network Information
Center, aka the NIC).
...
... NETWORK NAME ISSUES AND DISCUSSION ...
...
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 ...
... Network name syntax ...
...
The current syntax for network names, as defined by [RFC 952] is an
alphanumeric string of up to 24 characters, which begins with an
...
... 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 ...
... 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 ...
... 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 ...
...
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 price is that network names will get as complicated as host
names. An administrator will be able to create ...
... host
names. An administrator will be able to create network names in any
domain under his control, and also create ...
... domain under his control, and also create network number to name
entries in IN-ADDR.ARPA domains ...
... debugging tools and status displays
of various sorts. The conversion from IP address to network
number is well known for class A, B, and C IP addresses ...
... Mapping an organization to its network names and numbers. ...
...
This facility is useful because it may not always be possible
to guess the local choice for network names, but the
organization name is often well known.
...
...
The network name syntax discussed above can provide domain names
which will contain mappings from network ...
... 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 ...
... 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 same network number slots already assigned and delegated
in the IN-ADDR.ARPA section of the name space ...
... The main advantage of this scheme over the first is that it
allows convenient names for subnets as well as networks. A
secondary advantage is that it uses names which are not in use
already, and hence it is possible to test whether an
...
... a need to delegate a whole new name space. Since the IP
address space is so closely related to the network number
space, most believe that the overhead of creating such a new
...
... SPECIFICS FOR NETWORK NAME MAPPINGS ...
... 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 ...
... 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 ...
... <reversed-host-zero-number>.IN-ADDR.ARPA. PTR <network-name>
<reversed-host-zero-number>.IN-ADDR.ARPA ...
... master file for some IN-ADDR.ARPA domain for each network
involved. Similar RRs can be used at host ...
... Names which are network names. ...
... 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 ...
... network numbers, and these would be represented
with an additional RR per net.) The second states that the network
name ARPANET.ARPA ...
... 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
...
...
; Define network entry
isi-net.isi.edu. PTR 0.0.9.128.IN-ADDR.ARPA.
...
...
This assumes that the ISI network is named isi-net.isi.edu., first
level subnets are named div1-subnet ...
... Procedure for using an IP address to get network name ...
... IN-ADDR.ARPA. PTR isi-net.isi.edu
4. Conclude that the network name is "isi-net.isi.edu."
...
...
<assigned-network-name> <==> <IP-address>
<autonomous-system-id> <==> <number>
...
... Assigned networks ...
... network-number.YP.
0.0.0.4 PTR SATNET.Assigned-network-number.Name.YP.
0.0.0.10 PTR ARPANET.Assigned-network ...
... network-number.Name.YP.
SATNET. PTR 0.0.0.4.Name.Assigned-network-number.YP.
ARPANET. PTR 0.0.0.10.Name.Assigned-network ...
...
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
...
... 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 ...
... 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.
...
... 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.
...
... 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.
...
... network-number.Name.YP.
SATNET. PTR 0.0.0.4.Name.Assigned-network-number.YP.
ARPANET. PTR 0.0.0.10.Name.Assigned-network ...
...
$origin Assigned-network-number.Name.YP.
SATNET. PTR 0.0.0.4.
...
...
$origin Assigned-network-number.Name.YP.
SATNET. PTT "0.0.0.4"
...
... Reynolds, J., and J. Postel, "Internet Numbers", RFC 997(-> 1117(-> 1166) | 1020(-> 1166 | 1117(-> 1166) | 1062(-> 1166 | 1117(-> 1166)))), USC/Information Sciences Institute, March 1987 Contains network numbers, autonomous system numbers, etc. ...