Organization: China Interactive Publishing Network (http://www.china-pub.com/)
RFC Document Chinese Translation Program (http://www.china-pub.com/compters/emook/aboutemook.htm)
E-mail: Ouyang@china-pub.com
Translator: 15222775 @ 61. (15222775 @ 61. Hbzzx2001@yahoo.com.cn)
Translation time: 2002-1-18
Copyright: This Chinese translation copyright belongs to China Interactive Publishing Network. Can be used for non-commercial use free reprint, but must
Keep the translation and copyright information of this document.
Network Working Group Jon Postel
Request for Comments: 890 ISI
February 1984
External Gateway Agreement Implementation Plan
(RFC890 - EXTERIOR GATEWAY Protocol Implementation Schedule)
Memorandum status
This memo is a policy declaration of implementing external gateway protocols on the Internet. This is the official of ICCB and DARPA
Policy statement.
table of Contents
Current situation 1
In the future
Transition 2
Policy statement 2
Increase 3
Available help 3
Reference 3
Current situation
The current Internet has a large number of intelligent gateways and a lot of smart gateways. Intelligent gateway uses a network connection protocol
(GGP) [3] Dynamically exchanges routing information between themselves. Unneable gateway can not be dynamically swap routing
information.
Unimpled gateway must be registered on the intelligent gateway routing table, and the smart gateway status in the intelligent gateway list (example
In addition, adding new unimportant gateways) When changing, manual intervention is required.
The amount of traffic in the intelligent gateway route traffic depends on the number of intelligent gateways and the total number of networks. Because of a smart gateway
In the case of a single network connected to the international internet network, typically exist for each unimplete gateway in the routing table.
One or more networks.
The gateway of a single network connected to the international internet network is called "branch" gateway.
The GGP program currently used for the smart gateway has a limit of capacity. Urgently need to be significantly improved. This is very
It is difficult to complete because the intelligent gateway maintained by several different groups, and it is difficult to separate a subset of these gateways to test new
program.
In the future
In the future, there will be a large number of equal gateway independent systems depending on the situation. In order to maintain the route selection information, each will have special
With internal programs, perhaps through an internal gateway protocol (IGP). The intelligence of the gateway will result in autonomy that is used for gateways.
System IGP intelligence. Some gateways for each autonomous system will pass through an external gateway protocol (EGP) [2] and other
Some gateways of the autonomous system exchange routing information.
Affected by the original intelligent gateway into a large number of autonomous systems allow more flexible to improve the route selection process
Send and test. Different autonomous systems can use different routing processes, as long as they pass EGP and other autonomous
System communication.
Transition
The first step in transitioning from the current situation to the future situation is to use at least one subset of the EGP to eliminate all unimpled.
Gateway.
These subsets are referred to as the "Branch External Gateway Protocol" and is described in RFC 888 [1].
The second step is to incorporate the existing intelligent gateway into the autonomous system. Gateway maintained by different groups and programming
Get different autonomous systems. According to the current situation, this will lead to a very large autonomous system and three or four small.
Autonomous system. At this stage, large-scale autonomous systems may be called "core" autonomous system. All other autonomous systems will
To become a branch line attached to this core via EGP.
The third step will specify a complete EGP protocol and provide sufficient connectivity between equality autonomous systems.
Policy statement
After August 1, 84, there was certainly no intelligent gateway in the Internet.
Each gateway must be a member of a self-governing system. Some gateways for each autonomous system must use the external gateway protocol to exchange routing information with certain gateways of the core autonomous system.
meaning
If you have now there is a non-smart gateway, you should start doing something to upgrade it into an external gateway association.
The gateway is replaced with an EGP gateway.
Available help
The gateway you use may be developed by someone.
The following places are driving EGP Gateway: BBN, MIT, LINKABIT, ISI, HONEYWELL and SYMBOLICS. for
Further understanding, send a message to the Joyce Reynolds, mailbox "jkreynolds @ _USC - ISIF".
It is planned to provide EGP functionality in Berkeley 4.2 Unix.
Berkeley has shown an intention that makes the EGP function in the 4.2 Unix version before the deadline of the net-free gateway.
Available.
This is a post-empty list called "External Gateway Agreement - Person". You can use this list to send the mailbox
Send a message "EGP - People - Request @ _BBN - UNIX".
There is an available EGP test scheme in TOPS20. For the introduction of the use, you can send a message to Jim
Mathis, Mailbox "Mathis @ _SRI - KL".
If you need a self-government number, send a request to Joyce Reynolds, mailbox "jkreynolds @ _USC -
ISIF.
Reference
[1] Seamonson, L., And E. Rosen, "Stub EXTERG GATEWAY Protocol",
RFC-888, BBN Communications Company, January 1984.
[2] Rosen, E., "Exterior Gateway Protocol", RFC-827, BOLT BERANEK
And Newman, October 1982.
[3] Hinden, R., And A. Sheltzer, "The Darpa Internet Gateway",
RFC-823, Bolt Beeranek and newman, september 1982.
RFC890 - Exterior Gateway Protocol Implementation Schedule External Gateway Protocol Implementation Plan
1
RFC Document Chinese Translation Program
