draft-ietf-idr-bgp4-stdreport1-00.txt   draft-ietf-idr-bgp4-stdreport1-01.txt 
Inter-Domain Routing Working Group Paul Traina Inter-Domain Routing Working Group Paul Traina
INTERNET DRAFT cisco Systems INTERNET DRAFT cisco Systems
<draft-ietf-idr-bgp4-stdreport1-00.txt> October 1995 <draft-ietf-idr-bgp4-stdreport1-01.txt> October 31, 1995
BGP-4 Requirement Satisfaction Report BGP-4 Requirement Satisfaction Report
Status of this Memo Status of this Memo
This memo provides information for the Internet community. It does This memo provides information for the Internet community. It does
not specify an Internet standard. Distribution of this memo is not specify an Internet standard. Distribution of this memo is
unlimited. unlimited.
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
skipping to change at page 1, line 43 skipping to change at page 1, line 44
Board (IAB) and the Internet Engineering Steering Group (IESG), the Board (IAB) and the Internet Engineering Steering Group (IESG), the
second report will present additional knowledge and understanding second report will present additional knowledge and understanding
gained in the time when the protocol was mada a Draft standard and gained in the time when the protocol was mada a Draft standard and
when it was submitted for Standard. when it was submitted for Standard.
The remaining sections of this memo document how BGP satisfies The remaining sections of this memo document how BGP satisfies
General Requirements specified in Section 3.0, as well as General Requirements specified in Section 3.0, as well as
Requirements for Standard specified in Section 6.0 of the "Internet Requirements for Standard specified in Section 6.0 of the "Internet
Routing Protocol Standardization Criteria" document [1]. Routing Protocol Standardization Criteria" document [1].
Please send comments to iwg@ans.net. Please send comments to bgp@ans.net.
Acknowledgments
The BGP protocol has been developed by the IDR (formerly BGP) Working
Group of the Internet Engineering Task Force. The group would like
to express deepest thanks to Yakov Rekhter and Sue Hares, co-chairs
of the IDR working group. I'd also like to explicitly thank Yakov
Rekhter for the review of this document as well as constructive and
valuable comments.
This report is in part based on the initial work of Peter Lothberg
(Ebone), Andrew Partan (Alternet), Sean Doran (Sprint), Tony Bates
(MCI), and several others. Details of their work were presented at
the Twenti-fifth and Twenti-seventh IETF meetings and are available
from the IETF proceedings.
Documentation Documentation
BGP is an inter-autonomous system routing protocol designed for BGP is an inter-autonomous system routing protocol designed for
TCP/IP internets. TCP/IP internets.
Version 4 of the BGP protocol (BGP-4) specification has been Version 4 of the BGP protocol (BGP-4) specification has been
submitted as [2]. submitted as [2].
The MIB specification for BGP-4 has been submitted as [3]. The MIB specification for BGP-4 has been submitted as [3].
skipping to change at page 3, line 5 skipping to change at page 2, line 35
operational Internet. They are: operational Internet. They are:
- cisco Systems, Inc. - cisco Systems, Inc.
- gated consortium - gated consortium
- 3COM - 3COM
- Bay Networks (Wellfleet) - Bay Networks (Wellfleet)
- Proteon - Proteon
- Rainbow-Bridge - Rainbow-Bridge
- Telebit (DK) - Telebit (DK)
Acknowledgments
The BGP protocol has been developed by the IDR (formerly BGP) Working
Group of the Internet Engineering Task Force. The group would like
to express deepest thanks to Yakov Rekhter and Sue Hares, co-chairs
of the IDR working group. I'd also like to explicitly thank Yakov
Rekhter for the review of this document as well as constructive and
valuable comments.
This report is in part based on the initial work of Peter Lothberg
(Ebone), Andrew Partan (Alternet), Sean Doran (Sprint), Tony Bates
(MCI), and several others. Details of their work were presented at
the Twenti-fifth and Twenti-seventh IETF meetings and are available
from the IETF proceedings.
Author's Address: Author's Address:
Paul Traina Paul Traina
cisco Systems, Inc. cisco Systems, Inc.
170 W. Tasman Dr. 170 W. Tasman Dr.
San Jose, CA 95134 San Jose, CA 95134
pst@cisco.com pst@cisco.com
References References
[1] RFC1264 [1] RFC1264
Hinden, R., "Internet Routing Protocol Standardization Criteria", Hinden, R., "Internet Routing Protocol Standardization Criteria",
October 1991. October 1991.
[2] RFC1771 [2] draft-ietf-idr-bgp4-01.txt
Rekhter, Y., and Li, T., "A Border Gateway Protocol 4 (BGP-4)", March Rekhter, Y., and Li, T., "A Border Gateway Protocol 4 (BGP-4)", June
1995. 1995.
[3] RFC1657 [3] RFC1657
S. Willis, J. Burruss, J. Chu, "Definitions of Managed Objects for S. Willis, J. Burruss, J. Chu, "Definitions of Managed Objects for
the Fourth Version of the Border Gateway Protocol (BGP-4) using the Fourth Version of the Border Gateway Protocol (BGP-4) using
SMIv2", July 1994. SMIv2", July 1994.
[4] RFC1772 [4] RFC1772
Rekhter, Y., and P. Gross, Editors, "Application of the Border Rekhter, Y., and P. Gross, Editors, "Application of the Border
Gateway Protocol in the Internet", March 1995. Gateway Protocol in the Internet", March 1995.
[5] RFC1773 [5] RFC1773
Traina P., "Experience with the BGP-4 protocol", March 1995. Traina P., "Experience with the BGP-4 protocol", March 1995.
[6] RFC1774 [6] RFC1774
Traina P., "BGP-4 Protocol Analysis", March 1995. Traina P., "BGP-4 Protocol Analysis", March 1995.
[7] RFC1656 [7] RFC1656
Traina P., "BGP-4 Implementation Expereience", July 1994. Traina P., "BGP-4 Implementation Expereience", July 1994.
[8] draft-heffernan-tcp-md5-01.txt
Heffernan A., "TCP MD5 Signature Option" March, 1995. Work in
Progress.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/