As per Relevance of the word autonomous, we have this rfc below:
Network Working Group Jon
Request for Comments: 890
February 1984
Exterior Gateway Protocol Implementation
Status of this
This memo is a policy statement on the implementation of the
Gateway Protocol in the Internet. This is an official
statement of ICCB and DARPA
The Current
Currently the Internet has a number of smart gateways and a number
dumb gateways. The smart gateways dynamically exchange
information among themselves using the Gateway
Protocol (GGP) [3]. The dumb gateways do not exchange
information dynamically
The dumb gateways must be listed in the smart gateway routing tables
and changes in dumb gateways status (e.g., adding new dumb gateways
in the smart gateways tables requires human intervention
The amount of routing traffic between smart gateways depends on
number of smart gateways and the total number of networks.
dumb gateways typically connect a single network at the edge of
Internet, there is typically one more network in the routing
for each dumb gateway
Gateways that connect a single network to the edge of the
may be called "stub" gateways
The current GGP procedures used by the smart gateways are at
limits of their capacity. A significant change to these
is urgently required. This is difficult to perform because the
gateways are maintained by several different groups, and because
is difficult to isolate a subset of these gateways for testing
procedures
The Future
In the future, as it is currently envisioned, there will be a
of co-equal autonomous systems of gateways. Each as will have
own private internal procedures for maintaining routing information
perhaps via an Interior Gateway Protocol (IGP). The smartness of
gateway will be the smartness of the IGP used in the
system the gateway participates in. Some gateways of each
system will exchange routing informations with some gateways of
autonomous systems via an Exterior Gateway Protocol (EGP) [2].
Postel [Page 1]
RFC 890 February 1984
EGP Implementation
The factoring of the old set of smart gateways into a number
autonomous systems allows more flexibility for the development
testing of improved routing procedures. Different autonomous
can adopt different routing procedures internally, as long as
communicate with other autonomous systems via the EGP
The Transition
The first step in the transition from the current situation to
future situation is the replacement of all dumb gateways
gateways that implement at least a subset of the EGP
This subset is called the "Stub Exterior Gateway Protocol", and
described in RFC-888 [1].
The second step is to factor the existing smart gateways
autonomous systems. The gateways programmed and maintained
different groups will become distinct autonomous systems. As
are, this will result in one fairly large autonomous system and
or four small autonomous systems. At this step the large
system will be referred to as the "core" autonomous system.
other autonomous systems will be stubs attached to this core via EGP
The third step is to specify the full EGP protocol, and to allow
rich connectivity between co-equal autonomous systems
Policy
After 1-Aug-84 there shall be no dumb gateways in the Internet
Every gateway must be a member of some autonomous system.
gateway of each autonomous system must exchange routing
with some gateway of the core autonomous system using the
Gateway Protocol
If you have a dumb gateway now, you should start doing
today to get it upgraded to, or replaced by, an EGP gateway
Help
There may be a gateway you can use already developed by someone
People at the following places are working on EGP gateways: BBN
MIT, Linkabit, ISI, Honeywell, and Symbolics. For more
send a message to Joyce Reynolds at mailbox "JKReynolds@USC-ISIF".
There are plans to provide EGP functionality in Berkeley 4.2 Unix
Postel [Page 2]
RFC 890 February 1984
EGP Implementation
Berkeley has indicated an intention to have EGP capability
in the standard release of 4.2 Unix before the cut off date for
gateways
The is a mailing list for EGP implementers called "egp-people".
get on or off this list send a message to the
"egp-people-request@BBN-UNIX".
There is a EGP testing program available on TOPS20. For
about using it send a message to Jim Mathis at
"Mathis@SRI-KL".
If you need an autonomous system number send a request to
Reynolds at mailbox "JKReynolds@USC-ISIF".
[1] Seamonson, L., and E. Rosen, "Stub Exterior Gateway Protocol",
RFC-888, BBN Communications Company, January 1984.
[2] Rosen, E., "Exterior Gateway Protocol", RFC-827, Bolt
and Newman, October 1982.
[3] Hinden, R., and A. Sheltzer, "The DARPA Internet Gateway",
RFC-823, Bolt Beranek and Newman, September 1982.
Postel [Page 3]
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
