home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Internet Info 1997 December
/
Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso
/
drafts
/
draft_ietf_a_c
/
draft-ietf-bgp-defaultroute-01.txt
< prev
next >
Wrap
Text File
|
1993-03-03
|
2KB
|
62 lines
A new Request for Comments is now available in online RFC libraries.
RFC 1397:
Title: Default Route Advertisement In
BGP2 And BGP3 Versions Of The Border Gateway
Protocol
Author: D. Haskin
Mailbox: dhaskin@bbn.com
Pages: 2
Characters: 4,124
Updates/Obsoletes: none
This document specifies the recommendation of the Internet Engineering
Task Force's Border Gateway Protocol (BGP) Working Group on default
route advertisement support in BGP2 and BGP3 versions of the Border
Gateway Protocol. This recommendation only applies to BGP2 and BGP3
versions of the Border Gateway Protocol since starting with the BGP4
version a default route advertisement capability is built in the
protocol.
This is now a Proposed Standard Protocol.
This RFC specifies an IAB standards track protocol for the Internet
community, and requests discussion and suggestions for improvements.
Please refer to the current edition of the "IAB Official Protocol
Standards" for the standardization state and status of this protocol.
Distribution of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US. Requests to be added
to or deleted from the RFC-DIST distribution list should be sent to
RFC-REQUEST@NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info@ISI.EDU" with the message body
"help: ways_to_get_rfcs". For example:
To: rfc-info@ISI.EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC@NIC.DDN.MIL. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU. Please consult RFC 1111, "Instructions to RFC
Authors", for further information.
Joyce K. Reynolds
USC/Information Sciences Institute