6manInternet Engineering Task Force (IETF) W. GeorgeInternet-DraftRequest for Comments: 6547 Time Warner Cable Obsoletes: 3627(if approved) December 19, 2011February 2012 Updates: 6164(if approved) Intended status:Category: InformationalExpires: June 21, 2012 RFC3627ISSN: 2070-1721 RFC 3627 to Historicstatus draft-ietf-6man-3627-historic-01Status Abstract This document movesRFC3627 (Use"Use of /127 Prefix Length Between Routers ConsideredHarmful)Harmful" (RFC 3627) toHISTORICHistoric status to reflect the updated guidance contained inRFC6164 (Using"Using 127-Bit IPv6 Prefixes on Inter- RouterLinks). While a standards trackLinks" (RFC 6164). A Standards Track documentalreadysupersedes an informationaldocument and therefore RFC6164document; therefore, RFC 6164 isthe appropriate guidancetofollowbe followed when the two documents are inconflict, thisconflict. This document links the twodocumentsRFCs so thatit is clearer that the IETF hasIETF's updated guidance onthe matter.this topic is clearer. Status ofthisThis Memo ThisInternet-Draftdocument issubmitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsnot an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF).Note that other groups may also distribute working documents as Internet-Drafts. The listIt represents the consensus ofcurrent Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents validthe IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are amaximumcandidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status ofsix monthsthis document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on June 21, 2012.http://www.rfc-editor.org/info/rfc6547. Copyright Notice Copyright (c)20112012 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) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to 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 are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.Acknowledgements . . .Security Considerations . . . . . . . . . . . . . . . . . . . . 3 3.IANA Considerations . . . . . . . . . . . . . . . . . . .Acknowledgements . . .3 4. Security Considerations. . . . . . . . . . . . . . . . . . . . 35.4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 35.1.4.1. Normative References . . . . . . . . . . . . . . . . . . . 35.2.4.2. Informative References . . . . . . . . . . . . . . . . . . 3Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 41. Introduction This document moves "Use of /127 Prefix Length Between Routers Considered Harmful" RFC 3627 [RFC3627] toHISTORICHistoric status in accordance with RFC 2026 [RFC2026].ItRFC 3627 has been superseded by "Using 127-Bit IPv6 Prefixes on Inter-Router Links" RFC 6164 [RFC6164].While a standards trackA Standards Track documentalreadysupersedes an informationaldocument and therefore RFC6164document; therefore, RFC 6164 isthe appropriate guidancetofollowbe followed when the two documents are inconflict, thisconflict. This may notbehave been clear to casual readers who are notcompletelyfamiliar with the differences in IETF document types. This document adds the necessary link between the twodocumentsRFCs so thatthoseusers referring toRFC3627RFC 3627 for guidance will see that it has been obsoleted by updated guidance on the matter, thus hopefully eliminating any confusion that may be present.3. IANA Considerations This memo includes no request to IANA. 4.2. Security Considerations Thisdraftdocument introduces no new security considerations.2.3. Acknowledgements Thanks to Brian Carpenter, Bob Hinden, and Ron Bonica for guidance on the matter, and to Pekka Savola and Miya Kohno and the other authors of 6164 for their support.5.4. References5.1.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.5.2.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-2540Email:EMail: wesley.george@twcable.com