As per Relevance of the word identifier, we have this rfc below:
Network Working Group V.
Request for Comments: 1174
August 1990
IAB Recommended Policy on Distributing Internet Identifier
IAB Recommended Policy Change to Internet "Connected"
Status of this
This informational RFC represents the official view of the
Activities Board (IAB), and describes the recommended policies
procedures on distributing Internet identifier assignments
dropping the connected status requirement. This RFC does not
a standard. Distribution of this memo is unlimited
Table of
Status of this Memo............................................... 1
Overview.......................................................... 1
1. Recommendation about Internet Identifiers..................... 2
1.1. Summary..................................................... 2
1.2. Introduction................................................ 2
1.3. Proposed Method of Operation................................ 2
2. Recommendation about Connected Status......................... 3
2.1. Summary..................................................... 3
2.2. Introduction................................................ 3
2.3. Recommendations............................................. 4
2.a.1. Attachment 1.............................................. 4
2.a.1.1. Summary................................................. 4
2.a.1.2. Background.............................................. 4
2.a.1.3. Recommendation.......................................... 6
2.a.1.4. Discussion.............................................. 7
2.a.2. Attachment 2.............................................. 8
Security Considerations........................................... 8
Author's Address.................................................. 9
This RFC includes two recommendations from the IAB to the FNC.
first is a "Recommended Policy on Distributing Internet
Assignment", that is, a suggestion to distribute the function
assigning network and autonomous system numbers. The second is
"Recommended Policy Change to Internet 'Connected' Status", that is
a suggestion to drop the notion of connected status in favor
recording the acceptable use policy and traffic access policy
each network. Included in this second recommendation is the
Cerf [Page 1]
RFC 1174 Identifier Assignment and Connected Status August 1990
suggestion that any registered network may be entered into the
database without regard to connected status
1. Recommendation about Internet
To: Chairman, Federal Networking
From: Chairman, Internet Activities
CC: IAB,
Subject: Recommended Policy on Distributing
Identifier
1.1.
This document recommends procedures for distributing assignment
Internet identifiers (network and autonomous system numbers).
1.2.
Throughout its entire history, the Internet system has employed
central Internet Assigned Numbers Authority (IANA) for the
and assignment of various numeric identifiers needed for
operation of the Internet. The IANA function is performed by
Information Sciences Institute. The IANA has the
authority to delegate portions of this responsibility and,
respect to numeric network and autonomous system identifiers,
lodged this responsibility with an Internet Registry (IR).
function is performed by SRI International at its Network
Center (DDN-NIC).
With the rapid escalation of the number of networks in the
and its concurrent internationalization, it is timely to
further delegation of assignment and registration authority on
international basis. It is also essential to take into
that such identifiers, particularly network identifiers of class
and B type, will become an increasingly scarce commodity
allocation must be handled with thoughtful care
1.3. Proposed Method of
It is proposed to retain the centralized IANA and IR functions
The IR would continue to be the principal registry for all
and autonomous system numbers. It would also continue to
the list of root Domain Name System servers and a database
registered nets and autonomous systems
In addition, however, the IR would also allocate to
approved by the Coordinating Committee for Intercontinental
Cerf [Page 2]
RFC 1174 Identifier Assignment and Connected Status August 1990
Networking (CCIRN) blocks of network and autonomous system numbers
as needed, and delegate to them further assignment authority
It is recommended that, at least initially, the IR serve as
default registry in cases where no delegated registration
has been identified
Copies of the aggregate Internet registration database(s) should
maintained by the IR and copies provided to each delegated
to improve redundancy and access to this information. Updates to
database, however, would still be centralized at the IR with
copies redistributed by file transfer or other means on a
basis
It is recommended that candidate delegated registries meet with
IANA and IR to review operational procedures and requirements and
produce documentation to be issued as RFCs describing the details
the proposed distributed mode of operation
It is recommended that host Domain Name registration continue in
present form which already accommodates distribution of
function
2. Recommendation about Connected
To: Chairman, Federal Networking Council (FNC
From: Chairman, Internet Activities
CC: IAB,
Subject: Recommended Policy Change to Internet "Connected"
2.1.
This memorandum recommends a change in the current policy
associating "connected" status to a subset of networks which
been assigned an Internet identifier
2.2.
In the following, the term Internet Assigned Number Authority (IANA
refers to the organization which has primary authority to
and assign numeric identifiers required for operation of
Internet. This function is presently performed by USC
Sciences Institute. The term Internet Registry (IR) refers to
organization which has the responsibility for gathering
registering information about networks to which identifiers (
numbers, autonomous system numbers) have been assigned by the IR.
present, SRI International serves as the IR
Cerf [Page 3]
RFC 1174 Identifier Assignment and Connected Status August 1990
Attachments (1) and (2) outline the rationale for and implications
changing the current policy for associating "connected" status
only a subset of networks which have been assigned
identifiers
2.3.
The following actions are recommended
1. The Internet Registry should be instructed to drop
reference to "connected" status in its databases and in its
for Internet network and autonomous system registration
2. The Internet Registry should be instructed to request
statements of acceptable network usage, access and transit
for external traffic (i.e., traffic entering from or exiting
other networks) from each applicant for a network or
system identifier. For example, some networks conform to
National Science Foundation acceptable use guidelines;
networks will carry any traffic (e.g., common carriers);
may prohibit transit use. Retrospective statements should
gathered by the IR for networks already registered.
statements should be made available on-line and widely publicized
3. The Internet Registry should be instructed to allow
registered networks to be entered into the Domain Name
database without regard to "connected" status
Attachment: (1) Recommendation for replacement of "Connected"
(2) Recommendation on DNS and
2.a.1. Attachment 1
Recommendation for Replacement of "Connected"
2.a.1.1.
A revision of the current Internet procedures controlling
to the Internet is recommended to solve urgent problems caused
Internet growth both in the US and internationally.
recommendation involves relaxation of the present "connected"
rule and the creation of a policy database to guide
administrators
2.a.1.2.
With the demise of the ARPANET and the growth of a global Internet
the administration and registration of Internet network numbers
Cerf [Page 4]
RFC 1174 Identifier Assignment and Connected Status August 1990
outgrown its initially conceived client base: military,
and government-sponsored research organizations. Since
international growth has extended the Internet community to
and a broad range of academic and research institutions, we must re
evaluate some of the criteria for assignment and use of
network numbers
In the early phases of the Internet research project, numbers
assigned only to networks of organizations that were participating
the research effort. Later, as the system became more stable
expanded into a widespread infrastructure, other organizations
networks were assigned network numbers and allowed to interconnect
they were parts of the U.S. Government or sponsored by a
organization. To ensure global uniqueness, a single
Registry (IR) was designated: the Defense Data Net
Information Center (DDN-NIC) at SRI International
As the Internet protocols became popular in the
marketplace, many organizations purchased and installed
networks that needed network number assignments but were not
to be connected to the federally-sponsored system. The IR adopted
policy of assigning network numbers to all who requested them,
distinguishing networks permitted to link to the global Internet
assigning them "connected" status. Essentially, this meant that
network to which the number was assigned had the sanction of a U.S
Government sponsoring organization to link to the Internet
The present day Internet encompasses networks that serve
intermediaries to access the federally-sponsored backbones. Many
these intermediate networks were initiated under the sponsorship
the National Science Foundation. Some have been founded
federal assistance as consortia of using organizations.
Government has expressed a desire that all such networks be self
supporting, without the need for federal subsidy. To achieve
goal, it has been essential for the intermediate networks to
an increasingly varied range of users. A great many
participants can be found on the intermediate level networks.
use of the federally-sponsored backbones is premised on the
that the traffic is in support of academic, scholarly or
research work. The criteria for use of the intermediate
networks alone is sometimes more relaxed and, in the cases of
newly-formed commercial networks, there are no restrictions at all
In essence, each network needs to be able to determine, on the
of its own criteria, with which networks it will interconnect and
which networks it will support transit service. There is no longer
simple binary correlation between "connected" status and
use policy. The matter becomes even more complex as we
Cerf [Page 5]
RFC 1174 Identifier Assignment and Connected Status August 1990
the large and growing number of non-U.S. networks joining the
Internet. It is inappropriate to require that all of these
adhere to U.S. access and use criteria; rather, it can only
required that the traffic they send through the federally-
networks be consistent with the federal criteria
2.a.1.3.
Since the concept of a single, global "connected" status is no
meaningful, it is recommended that it be retired and to define
characteristics that could be used by networks within the Internet
determine a specific network's eligibility to communicate with
networks
Some attributes which might be useful to track and could be used
criteria to determine the acceptability of Internet traffic
routing purposes include
1) Country
2) Conformance to acceptable use policy for
NSFNET, MILNET, NSI, ESnet, NORDUnet, ...
To implement this idea, the IR would update the current Internet
Number-Template to query applicants for the necessary information
This information would then be collected in a database containing
for instance, a matrix of network numbers over policies. Note
the policies might be presented in narrative form. In addition,
usage policies of the various networks must be publicly available
that applicants and other interested parties can be advised of
issues as they relate to various networks
Under this proposal, the IR would be charged with the
and administration of the Internet number space but not with
enforcement of policy. The IR should collect enough information
permit network administrators to make intelligent decisions as to
acceptability of traffic destined to or from each and
legitimate Internet number. Enforcement of policies is
below
At a later step, we anticipate that it will be desirable
distribute the IR function among multiple centers, e.g., with
on different continents. This should be straight-forward once the
function is divorced from policy enforcement
Cerf [Page 6]
RFC 1174 Identifier Assignment and Connected Status August 1990
2.a.1.4.
It is already true in the current Internet that there
restrictions on certain traffic on particular networks. For example
two intermediate level networks that are willing to carry
traffic can link with each other but are barred from
commercial traffic or any other traffic that is not for academic
scholarly purposes across the federally-sponsored backbones
Routing of traffic based upon acceptable-use policies requires
technical ability known as "policy-based routing" (PBR). At
present time, the PBR mechanism available in the Internet operates
the level of an entire network; all users and hosts on a network
subject to the same routes for a given destination. Using this
mechanism, a network maintains routes (and provides transit services
only for networks with compatible use policies. For an
level network, for example, the routing decisions must be made on
basis of the network numbers assigned to the organizations;
might be considered to have traffic conformant with federal
policies and some might not
Although it is much more fine-grained than the current "on or off
rule of connected status, the use of PBR based on networks is still
very coarse measure of control. Since the decision on
is made at the network level, one has to assign a set
characteristics to all traffic emanating from or entering into
given network to make this access control strategy work.
application of such controls could prevent a commercial
from legitimately sending research or scholarly data across
federal backbone (e.g., IBM needs to communicate with MCI and
about NSFNET, but other parts of IBM may need to communicate
commercial matters). Organizations with a variety of uses might
to artificially define several networks with which to
different use policies
The practical result is that in order to support desirable
patterns, government-sponsored networks will sometimes have to
upon self-policing by traffic sources, rather than upon
mechanical enforcement of acceptable use policies. Higher
on usage will have a cost in terms of limiting desirable access
An important project now underway in the Internet Engineering
Force (IETF) is developing a more general mechanism for PBR that
allow control at the level of individual hosts and possibly
user. It will give an end host or user the ability to select routes
taking into consideration issues such as cost, performance
reliability of the transit networks
Cerf [Page 7]
RFC 1174 Identifier Assignment and Connected Status August 1990
2.a.2. Attachment 2
IAB Policy Recommendation on DNS and
The Internet Domain Name system (DNS) is an essential part of
networking infrastructure. It establishes a global
database for mapping host names into IP addresses and for
electronic mail. Its efficient and reliable functioning is vital
nearly all Internet users
Some DNS operations depend upon the existence of a complete
at certain "root" servers, in particular at the Internet
(IP) located at the Defense Data Net Network Information Center
SRI International (DDN-NIC). The past policy has been to
inclusion in this database to approval of Internet interconnection
a U.S. Government agency. This "connected" status restriction is
longer viable, and recommendations for its replacement have been
forward
In any case, we believe that the DNS database is not the
architectural level for enforcement of administrative
restrictions, e.g., controls over the announcement of networks in
routing protocols
The Internet Activities Board (IAB) therefore strongly endorses
following recommendation from the Federal Engineering Planning
to the Federal Networking Council, to provide DNS service
of access control policies
"There has been a great deal of discussion about
nameservers, the IN-ADDR domain, and "connected" status as
Internet has grown to include many more nations than just
United States. As we move to a more global Internet, it
like it would be a good idea to re-evaluate some of the rules
have governed the naming and registration policies that exist
The naming and routing should be completely decoupled.
particular, it should be possible to register both a name/domain
as well as address servers within the IN-ADDR domain,
of whether the client has "connected" status or not. This
be implemented immediately by the IR at the DDN-NIC. No U.S
Government sponsor should be required for domain name/
registration."
Security
Security issues are not addressed in this memo
Cerf [Page 8]
RFC 1174 Identifier Assignment and Connected Status August 1990
Author's
Vinton G.
Corporation for National Research
1895 Preston White Drive, Suite 100
Reston, VA 22091
Phone: (703) 620-8990
EMail: vcerf@nri.reston.va.
Cerf [Page 9]
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 technical nosh by ServerMasters Corporation
collaboration of BobX
