idnits 2.17.1 draft-howard-sunset4-v4historic-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 14, 2016) is 2964 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group L. Howard 3 Internet-Draft Time Warner Cable 4 Intended status: Standards Track March 14, 2016 5 Expires: September 15, 2016 7 IPv4 Declared Historic 8 draft-howard-sunset4-v4historic-00 10 Abstract 12 IPv4 has been superseded by IPv6, and is therefore Historic. 14 Status of This Memo 16 This Internet-Draft is submitted in full conformance with the 17 provisions of BCP 78 and BCP 79. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF). Note that other groups may also distribute 21 working documents as Internet-Drafts. The list of current Internet- 22 Drafts is at http://datatracker.ietf.org/drafts/current/. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 This Internet-Draft will expire on September 15, 2016. 31 Copyright Notice 33 Copyright (c) 2016 IETF Trust and the persons identified as the 34 document authors. All rights reserved. 36 This document is subject to BCP 78 and the IETF Trust's Legal 37 Provisions Relating to IETF Documents 38 (http://trustee.ietf.org/license-info) in effect on the date of 39 publication of this document. Please review these documents 40 carefully, as they describe your rights and restrictions with respect 41 to this document. Code Components extracted from this document must 42 include Simplified BSD License text as described in Section 4.e of 43 the Trust Legal Provisions and are provided without warranty as 44 described in the Simplified BSD License. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 49 2. Implications . . . . . . . . . . . . . . . . . . . . . . . . 3 50 3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 51 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 52 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 53 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 6.1. Normative References . . . . . . . . . . . . . . . . . . 3 55 6.2. Informative References . . . . . . . . . . . . . . . . . 4 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 4 58 1. Introduction 60 According to [RFC2026], "The Internet Standards Process": 62 4.2.4 Historic 64 A specification that has been superseded by a more recent 65 specification or is for any other reason considered to be obsolete 66 is assigned to the "Historic" level. 68 Note: Standards track specifications normally must not depend on 69 other standards track specifications which are at a lower maturity 70 level or on non standards track specifications other than 71 referenced specifications from other standards bodies. (See 72 Section 7.) 74 IPv4 [RFC791] has been superseded by the more recent IPv6 75 specification [RFC2460bis]. The IPv6 document specifically says, "IP 76 version 6 (IPv6) is a new version of the Internet Protocol, designed 77 as the successor to IP version 4 (IPv4) [RFC791]." 79 RFC791 is therefore Historic. 81 IPv4 has inherent limitations which can not be mitigated; the IETF 82 has therefore developed a new protocol without these limitations. 83 Current and future work builds on IPv6, making it better for every 84 purpose than the old protocol. 86 The use of IPv4 is deprecated. The term "deprecated" is used to 87 indicate a feature, characteristic, or practice that should be 88 avoided, in this case because it is being superseded by a newer 89 protocol. The term does not indicate that the practice is harmful, 90 but that there will be no further development in IPv4, and therefore 91 those using the old version are advised to transition to the newer 92 version. 94 2. Implications 96 Moving an Internet Standard to the Historic maturity level does not 97 mean that it cannot be used. It does mean that any Standards Track 98 RFC with a Normative reference to RFC791 is Historic. This is 99 appropriate: any RFC defining IPv4 options is Historic. 101 In addition, some RFCs that refer to RFC791, such as [RFC1035] 102 "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION" which defines A and 103 IN-ADDR.ARPA, will be Updated By this document, but are not Historic. 104 Other documents with incidental references to RFC791 should not be 105 affected. Documents requiring updates are appropriate for [draft- 106 ietf-sunset4-gapanalysis]. 108 The IETF does not update Historic RFCs. Therefore, the IETF will no 109 longer work on IPv4 technologies, including transition technologies. 111 The term "IP," without address family specified, is assumed to mean 112 "IPv6." 114 3. Security Considerations 116 It is possible that bugs inherent to IPv4 will yet be discovered. 117 Being Historic, the IETF will not further update IPv4. Therefore, 118 for security reasons, the use of IPv6 exclusively is recommended. 120 4. IANA Considerations 122 This document does not direct IANA to alter its processes for 123 allocating IPv4 addresses according to its processes. This is 124 unlikely to be a significant activity for long. 126 5. Acknowledgements 128 6. References 130 6.1. Normative References 132 [RFC791], Postel, J., "Internet Protocol", September 1981. 134 [RFC2460bis], Deering, S., and Hinden, R., "Internet Protocol, 135 Version 6 (IPv6) Specification", January 2016. 137 [RFC2026], Bradner, S., "The Internet Standards Process", October 138 1996. 140 [draft-ietf-6man-rfc2460bis] Deering, S. and R. Hinden, "Internet 141 Protocol, Version 6 (IPv6) Specification", November 2015. 143 6.2. Informative References 145 [RFC1035], Mockapetris, P., "DOMAIN NAMES - IMPLEMENTATION AND 146 SPECIFICATION", November 1987. 148 Author's Address 150 Lee Howard 151 Time Warner Cable 152 13820 Sunrise Valley Dr. 153 Herndon, VA 20171 154 USA 156 Email: lee.howard@twcable.com