draft-ietf-6man-3627-historic-01.txt   rfc6547.txt 
6man W. George Internet Engineering Task Force (IETF) W. George
Internet-Draft Time Warner Cable Request for Comments: 6547 Time Warner Cable
Obsoletes: 3627 (if approved) December 19, 2011 Obsoletes: 3627 February 2012
Updates: 6164 (if approved) Updates: 6164
Intended status: Informational Category: Informational
Expires: June 21, 2012 ISSN: 2070-1721
RFC3627 to Historic status RFC 3627 to Historic Status
draft-ietf-6man-3627-historic-01
Abstract Abstract
This document moves RFC3627 (Use of /127 Prefix Length Between This document moves "Use of /127 Prefix Length Between Routers
Routers Considered Harmful) to HISTORIC status to reflect the updated Considered Harmful" (RFC 3627) to Historic status to reflect the
guidance contained in RFC6164 (Using 127-Bit IPv6 Prefixes on Inter- updated guidance contained in "Using 127-Bit IPv6 Prefixes on Inter-
Router Links). While a standards track document already supersedes Router Links" (RFC 6164). A Standards Track document supersedes an
an informational document and therefore RFC6164 is the appropriate informational document; therefore, guidance provided in RFC 6164 is
guidance to follow when the two documents are in conflict, this links to be followed when the two documents are in conflict. This document
the two documents so that it is clearer that the IETF has updated links the two RFCs so that the IETF's updated guidance on this topic
guidance on the matter. is clearer.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document is not an Internet Standards Track specification; it is
Task Force (IETF). Note that other groups may also distribute published for informational purposes.
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on June 21, 2012. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6547.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3 2. Security Considerations . . . . . . . . . . . . . . . . . . . . 3
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. References . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Normative References . . . . . . . . . . . . . . . . . . . 4
5.1. Normative References . . . . . . . . . . . . . . . . . . . 3 4.2. Informative References . . . . . . . . . . . . . . . . . . 4
5.2. Informative References . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
This document moves RFC 3627 [RFC3627] to HISTORIC status in This document moves "Use of /127 Prefix Length Between Routers
accordance with RFC 2026 [RFC2026]. It has been superseded by Considered Harmful" [RFC3627] to Historic status in accordance with
RFC 6164 [RFC6164]. While a standards track document already RFC 2026 [RFC2026]. RFC 3627 has been superseded by "Using 127-Bit
supersedes an informational document and therefore RFC6164 is the IPv6 Prefixes on Inter-Router Links" [RFC6164]. A Standards Track
appropriate guidance to follow when the two documents are in document supersedes an informational document; therefore, guidance
conflict, this may not be clear to casual readers who are not provided in RFC 6164 is to be followed when the two documents are in
completely familiar with the differences in IETF document types. conflict. This may not have been clear to casual readers who are not
This document adds the necessary link between the two documents so familiar with the differences in IETF document types. This document
that those referring to RFC3627 for guidance will see that it has adds the necessary link between the two RFCs so that users referring
been obsoleted by updated guidance on the matter, thus hopefully to RFC 3627 for guidance will see that it has been obsoleted by
eliminating any confusion that may be present. updated guidance on the matter, thus hopefully eliminating any
confusion that may be present.
2. Acknowledgements 2. Security Considerations
This document introduces no new security considerations.
3. Acknowledgements
Thanks to Brian Carpenter, Bob Hinden, and Ron Bonica for guidance on 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 the matter, and to Pekka Savola and Miya Kohno and the other authors
of 6164 for their support. of 6164 for their support.
3. IANA Considerations 4. References
This memo includes no request to IANA.
4. Security Considerations
This draft introduces no new security considerations.
5. References
5.1. Normative References 4.1. Normative References
[RFC3627] Savola, P., "Use of /127 Prefix Length Between Routers [RFC3627] Savola, P., "Use of /127 Prefix Length Between Routers
Considered Harmful", RFC 3627, September 2003. Considered Harmful", RFC 3627, September 2003.
[RFC6164] Kohno, M., Nitzan, B., Bush, R., Matsuzaki, Y., Colitti, [RFC6164] Kohno, M., Nitzan, B., Bush, R., Matsuzaki, Y., Colitti,
L., and T. Narten, "Using 127-Bit IPv6 Prefixes on Inter- L., and T. Narten, "Using 127-Bit IPv6 Prefixes on Inter-
Router Links", RFC 6164, April 2011. Router Links", RFC 6164, April 2011.
5.2. Informative References 4.2. Informative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision [RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996. 3", BCP 9, RFC 2026, October 1996.
Author's Address Author's Address
Wesley George Wesley George
Time Warner Cable Time Warner Cable
13820 Sunrise Valley Drive 13820 Sunrise Valley Drive
Herndon, VA 20171 Herndon, VA 20171
US US
Phone: +1 703-561-2540 Phone: +1 703-561-2540
Email: wesley.george@twcable.com EMail: wesley.george@twcable.com
 End of changes. 15 change blocks. 
60 lines changed or deleted 53 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/