idnits 2.17.1 draft-ietf-sunset4-ipv6-ietf-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 : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 04, 2017) is 2603 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) No issues found here. 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 Retevia 4 Intended status: Standards Track March 04, 2017 5 Expires: September 5, 2017 7 IETF: End Work on IPv4 8 draft-ietf-sunset4-ipv6-ietf-00 10 Abstract 12 The IETF will stop working on IPv4, except where needed to mitigate 13 documented security issues, to facilitate the transition to IPv6, or 14 to enable IPv4 decommissioning. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at http://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on September 5, 2017. 33 Copyright Notice 35 Copyright (c) 2017 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Statement . . . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. Security Considerations . . . . . . . . . . . . . . . . . . . 3 52 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 53 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 54 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 5.1. Normative References . . . . . . . . . . . . . . . . . . 3 56 5.2. Informative References . . . . . . . . . . . . . . . . . 3 57 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 59 1. Statement 61 The IETF has developed IPv6 to replace IPv4. 63 Ongoing focus is required to ensure that future IETF work is capable 64 of IPv6-only operation. Until the time when IPv4 is no longer in 65 wide use and/or declared historic, the IETF needs to continue to 66 update IPv4-only protocols and features for vital operational or 67 security issues. "Vital" means "necessary for successfully operating 68 IPv4 networks." Similarly, the IETF needs to complete the work 69 related to IPv4-to-IPv6 transition tools for migrating more traffic 70 to IPv6. Some changes may be necessary in IPv4 protocols to 71 facilitate decommissioning IPv4 in a way that does not create 72 unacceptable impact to applications or users. These sorts of 73 IPv4-focused activities, in support of security, transition, and 74 decommissioning, will continue, where accompanied by problem 75 statements based on operational experience. 77 The IESG will review proposed working group charters to ensure 78 that work will be capable of operating without IPv4, except in 79 cases of IPv4 security, transition, and decommissioning work. 81 The IETF will update IPv4 protocols and features to facilitate 82 IPv4 decommissioning. No IPv4-only feature will be added unless 83 there's an equivalent feature added in the IPv6 version. 85 New IETF work will explicitly support IPv6, or be IP version 86 agnostic (because it is implemented above the network layer), 87 except IPv4-specific transition technologies. 89 The IETF will not initiate new IPv4 extension technology 90 development. 92 New IETF work must function completely on IPv6-only nodes and 93 networks. 95 2. Security Considerations 97 It is possible that bugs inherent to IPv4 will yet be discovered. 98 The IETF will document these, and may mitigate them if consensus 99 exists that mitigation is required. 101 3. IANA Considerations 103 This document does not direct IANA to alter its processes for 104 allocating IPv4 addresses according to its processes. This is 105 unlikely to be a significant activity for long. 107 4. Acknowledgements 109 This document is based largely on draft-george-ipv6-support, and I 110 thank Wes George for his significant work on that document. Terry 111 Manderson was also essential in developing this document. 113 5. References 115 5.1. Normative References 117 5.2. Informative References 119 Author's Address 121 Lee Howard 122 Retevia 123 Fairfax, VA 22032 124 USA 126 Email: Lee@asgard.org