Request to Move RFC 1403 to Historic Status
Requests Historic status for the BGP-OSPF interaction described in RFC 1403.
Meyer, D. and J. Scudder, "Request to Move RFC 1403 to Historic Status", RFC 3166, DOI 10.17487/RFC3166, August 2001, <https://www.rfc-editor.org/info/rfc3166>.
@misc{rfc3166,
series = {Request for Comments},
number = 3166,
howpublished = {RFC 3166},
publisher = {RFC Editor},
doi = {10.17487/RFC3166},
url = {https://www.rfc-editor.org/info/rfc3166},
author = {D. Meyer and J. Scudder},
title = {{Request to Move RFC 1403 to Historic Status}},
pagetotal = 3,
year = 2001,
month = aug,
} RFC text
Contents
Network Working Group D. Meyer
Request for Comments: 3166 Sprint
Category: Informational J. Scudder
Cisco Systems
August 2001
Request to Move RFC 1403 to Historic Status
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
RFC 1403, "BGP OSPF Interaction", describes technology which is no
longer used. This document requests that RFC 1403 be moved to
Historic status.
1. Details
During a review of internet standards relating to BGP, it became
apparent that BGP OSPF interaction, as described in RFC 1403, is not
common usage (if at all), and requires significant implementation
complexity. Since this mechanism has not been in use in the public
internet for many years (if ever), it is proposed to reclassify it to
Historic.
2. Security Considerations
Moving RFC 1403 to Historic has no known effect on the security of
the internet.
3. References
[RFC1403] Varadhan, K., "BGP OSPF Interaction", RFC 1403,
January 1993.
4. Authors' Addresses
David Meyer
Sprint
12502 Sunrise Valley Dr
Reston VA, 20191
MS VARESA-0105
EMail: dmm@sprint.net
John Scudder
Cisco Systems, Inc.
170 Tasman Drive
San Jose, CA, 95134
EMail: jgs@cisco.com
Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
ISO Plain Language
On this page
§1The RFC 1403 Mechanism
RFC 1403 describes an interaction between BGP and OSPF. During a review of Internet standards related to BGP, the authors found that this mechanism was not in common use, if used at all.
The memo says implementing it would require significant complexity. It reports that the mechanism had not been used in the public Internet for many years, if ever.
The earlier RFC described a way for BGP and OSPF to interact. The review found little or no use of that mechanism.
§1Request to Reclassify RFC 1403
Because the interaction was not in public Internet use and added implementation complexity, RFC 3166 proposes reclassifying RFC 1403 as Historic.
The memo says moving RFC 1403 to Historic has no known effect on Internet security. It does not describe protocol changes.
The authors propose Historic status because the mechanism was unused and complex. They say the reclassification has no known security effect.
§3Reference and Scope
The only protocol document cited is RFC 1403, “BGP OSPF Interaction,” published in January 1993. RFC 3166 is a short status request explaining the proposed reclassification.
The request is confined to RFC 1403. It does not define a replacement mechanism or describe changes to BGP or OSPF.
This memo is about the status of RFC 1403 only. It does not replace the routing protocols or define a new one.