RFC 3167

Request to Move RFC 1745 to Historic Status

πŸ“… published August 2001, from ietf

RFC 3167: Request to Move RFC 1745 to Historic Status πŸŽ€βœ¨

Network Working Group, Category: Informational, August 2001. Written by D. Meyer (Sprint) and J. Scudder (Cisco Systems). Nothing in this title block says it obsoletes or updates another RFC. πŸ’…


Status of This Memo 🌸

okay so this memo is for information only πŸ’– It's giving "FYI bestie" and it does not specify an Internet standard of any kind. Distribution is unlimited, so share it with everyone 🫢

Copyright (C) The Internet Society (2001). All Rights Reserved.

Abstract ✨

so RFC 1745, "BGP4/IDRP for IP---OSPF Interaction", describes tech that was never deployed on the public internet 😭 This doc asks for RFC 1745 to be moved to Historic status. 🧚

1. Details πŸ”₯

okay the lore: while reviewing internet standards about BGP, it became super clear that the BGP/IDRP and OSPF interaction from RFC 1745 has never been deployed on the public internet. It would also need a lot of implementation complexity πŸ’€ Since nobody has ever used this mechanism on the public internet, the proposal is to reclassify it as Historic. That's it, that's the tea πŸ“

2. Security Considerations πŸ”

Moving RFC 1745 to Historic has no known effect on the security of the internet. Zero known drama here, periodt πŸ’œ

3. References πŸ“š

[RFC1745]   Varadhan, K., Hares, S. and Y. Rekhter, "BGP4/IDRP for
            IP---OSPF Interaction", RFC 1745, December 1994.

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

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. Thank you, Internet Society πŸ’–

πŸ“¦ where this page comes from