RFC 3166

Request to Move RFC 1403 to Historic Status

📅 published August 2001, from ietf

RFC 3166: Request to Move RFC 1403 to Historic Status 🎀

  • Authors: David Meyer (Sprint) and John Scudder (Cisco Systems) 💖
  • Category: Informational ✨
  • Date: August 2001 📅
  • Obsoletes / Updates: Nothing is listed as obsoleted or updated 🦋

Status of This Memo 💅

okay so this memo is just giving information to the Internet community. it's not a standard, not even a little. and anyone can get a copy, distribution is unlimited 🫶

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

Abstract 🔥

so RFC 1403, "BGP OSPF Interaction," describes tech that nobody uses anymore 💀 this doc asks for RFC 1403 to be moved to Historic status. bye bye, but make it archival 🧚

1. Details 💜

bestie, while the team was reviewing the internet standards for BGP, it became super clear that BGP OSPF interaction (the thing from RFC 1403) is not common usage, if it's used at all 🙈 and it needs a lot of implementation complexity on top of that. it hasn't been used on the public internet for years, if it ever was, so the proposal is to reclassify it as Historic. main character energy? no, retired character energy 👑

2. Security Considerations 🔒

moving RFC 1403 to Historic has no known effect on the security of the internet. zero plot twists here, periodt ✨

3. References 📚

[RFC1403]  Varadhan, K., "BGP OSPF Interaction", RFC 1403,
           January 1993.

4. Authors' Addresses 🌸

the two authors and their contact details, copied exactly so you can reach them 💌

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

this part is legal text, so I'm keeping every word exactly as written, no edits 🫡

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