RFC3166


RFC index | STD index | BCP index | FYI index
Plain text | gzipped plain text | A4 postscript | A4 postscript, 2 up | A4 postscript, 4 up
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. Meyer & Scudder Informational [Page 1]
RFC 3166 Request to Move RFC 1403 to Historic Status August 2001

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 Meyer & Scudder Informational [Page 2]
RFC 3166 Request to Move RFC 1403 to Historic Status August 2001 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. Meyer & Scudder Informational [Page 3]