RFC 6547

RFC 3627 to Historic Status

πŸ“… published February 2012, from ietf

RFC 6547: RFC 3627 to Historic Status πŸ’–

  • Series and number: Internet Engineering Task Force (IETF) Request for Comments 6547 πŸŽ€
  • Author: W. George (Wesley George), Time Warner Cable 🫢
  • Date: February 2012 🌸
  • Category: Informational, so this one is published for information and is not a Standards Track spec πŸ“š
  • Obsoletes: 3627 πŸ™ˆ
  • Updates: 6164 ✨
  • ISSN: 2070-1721

Abstract ✨

okay so this doc moves "Use of /127 Prefix Length Between Routers Considered Harmful" (RFC 3627) over to Historic status πŸ•°οΈ because the newer guidance in "Using 127-Bit IPv6 Prefixes on Inter-Router Links" (RFC 6164) has replaced it. A Standards Track doc beats an informational one, so if the two ever clash, RFC 6164 wins πŸ‘‘. This doc just links the two RFCs together so everyone can see where the IETF's current advice on this topic lives πŸ’….

Status of This Memo πŸ“

this document is not an Internet Standards Track specification πŸ™…β€β™€οΈ. it's published for informational purposes 🧚.

this document is a product of the Internet Engineering Task Force (IETF) 🌈. it represents the consensus of the IETF community and has received public review. it was approved for publication by the Internet Engineering Steering Group (IESG). not every doc the IESG approves is a candidate for any level of Internet Standard, so see Section 2 of RFC 5741 for that πŸ”.

info about the current status of this doc, any errata, and how to give feedback can be found at http://www.rfc-editor.org/info/rfc6547 πŸ¦‹.

Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. πŸ’œ

this document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they stood on the date of publication πŸ“œ. please read these carefully, because they spell out your rights and restrictions for this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they come without warranty as described in the Simplified BSD License πŸ“.

Table of Contents πŸ—‚οΈ

1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.  Security Considerations . . . . . . . . . . . . . . . . . . . . 3
3.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 3
4.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 4
  4.1.  Normative References  . . . . . . . . . . . . . . . . . . . 4
  4.2.  Informative References  . . . . . . . . . . . . . . . . . . 4

1. Introduction 🌟

okay so this doc moves "Use of /127 Prefix Length Between Routers Considered Harmful" [RFC3627] to Historic status, following RFC 2026 [RFC2026] πŸ“–. RFC 3627 has been superseded by "Using 127-Bit IPv6 Prefixes on Inter-Router Links" [RFC6164] πŸ”„. again, a Standards Track doc supersedes an informational one, so guidance in RFC 6164 is to be followed whenever the two conflict βš–οΈ.

this might not be obvious to casual readers who don't know the difference between IETF document types πŸ™ˆ. so this doc adds the missing link between the two RFCs. that way, anyone who looks up RFC 3627 for guidance will see that it's been obsoleted by newer guidance on the topic πŸ’…. the hope is that this clears up any confusion 🫢.

2. Security Considerations πŸ”

this document introduces no new security considerations πŸ™Œ.

3. Acknowledgements πŸŽ€

thanks to Brian Carpenter, Bob Hinden, and Ron Bonica for their guidance on the matter πŸ‘‘, and to Pekka Savola, Miya Kohno, and the other authors of 6164 for their support πŸ’–.

4. References πŸ“š

4.1. Normative References

  • [RFC3627] Savola, P., "Use of /127 Prefix Length Between Routers Considered Harmful", RFC 3627, September 2003. 🌸
  • [RFC6164] Kohno, M., Nitzan, B., Bush, R., Matsuzaki, Y., Colitti, L., and T. Narten, "Using 127-Bit IPv6 Prefixes on Inter-Router Links", RFC 6164, April 2011. ✨

4.2. Informative References

  • [RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. πŸ¦‹

Author's Address 🏑

Wesley George
Time Warner Cable
13820 Sunrise Valley Drive
Herndon, VA  20171
US

Phone: +1 703-561-2540
EMail: wesley.george@twcable.com
πŸ“¦ where this page comes from