idnits 2.17.1 draft-bchv-rfc6890bis-06.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 a Security Considerations section. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 7, 2017) is 2577 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: '2' on line 130 -- Looks like a reference, but probably isn't: '7' on line 140 Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Bonica 3 Internet-Draft Juniper Networks 4 Updates: 6890 (if approved) M. Cotton 5 Intended status: Best Current Practice ICANN 6 Expires: October 9, 2017 B. Haberman 7 Johns Hopkins University 8 L. Vegoda 9 ICANN 10 April 7, 2017 12 Updates to Special-Purpose IP Address Registries 13 draft-bchv-rfc6890bis-06 15 Abstract 17 This memo updates the IANA IPv4 and IPv6 Special-Purpose Address 18 Registries to address issues raised by the definition of a "global" 19 prefix. It also corrects several errors in registry entries to 20 ensure the integrity of the IANA Special-Purpose Address Registries. 22 This memo updates RFC 6890. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at http://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on October 9, 2017. 41 Copyright Notice 43 Copyright (c) 2017 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 59 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 60 2.1. Definition of Global . . . . . . . . . . . . . . . . . . 3 61 2.2. Updates to the IPv4 Special-Purpose Address Registry . . 3 62 2.3. Updates to the IPv6 Special-Purpose Address Registry . . 3 63 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 64 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 65 4.1. Normative References . . . . . . . . . . . . . . . . . . 4 66 4.2. Informative References . . . . . . . . . . . . . . . . . 4 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 69 1. Introduction 71 In order to support new protocols and practices, the IETF 72 occasionally reserves an address block for a special purpose. For 73 example, [RFC1122] reserves an IPv4 address block (0.0.0.0/8) to 74 represent the local (i.e., "this") network. Likewise, [RFC4291] 75 reserves an IPv6 address block (fe80::/10) to represent link-scoped 76 unicast addresses. 78 Several issues have been raised with the documentation of some of the 79 special-purpose address blocks in [RFC6890]. Specifically, the 80 definition of "global" provided in [RFC6890] was misleading as it 81 slightly differed from the generally accepted definition of "global 82 scope" (i.e., the ability to forward beyond the boundaries of an 83 administrative domain, described as "global unicast" in the IPv6 84 addressing architecture [RFC4291]). 86 This memo updates the definition of "global" from [RFC6890] for the 87 IPv4 and IPv6 Special-Purpose Address Registries, augments the fields 88 contained within the registries in order to address the confusion 89 raised by the definition of "global", and corrects some errors in 90 some of the entries in the Special-Purpose Address Registries. 92 This memo updates [RFC6890]. 94 2. IANA Considerations 96 2.1. Definition of Global 98 [RFC6890] defined the term "global" without taking into consideration 99 the multiple uses of the term. Specifically, IP addresses can be 100 global in terms of allocation scope as well as global in terms of 101 routing/reachability. To address this ambiguity, the use of the term 102 "global" defined in [RFC6890] is replaced with "globally reachable". 103 The following definition replaces the definiton of "global" in the 104 IANA Special-Purpose Address Registries: 106 o Globally Reachable - A boolean value indicating whether an IP 107 datagram whose destination address is drawn from the allocated 108 special-purpose address block is forwardable beyond a specified 109 administrative domain. 111 The same relationship between the value of "Destination" and the 112 values of "Forwardable" and "Global" described in [RFC6890] holds for 113 "Globally Reachable". If the value of "Destination" is FALSE, the 114 values of "Forwardable" and "Globally Reachable" must also be FALSE. 116 The "Global" column in the IPv4 Special-Purpose Address Registry 117 (https://www.iana.org/assignments/iana-ipv4-special-registry) and the 118 IPv6 Special-Purpose Address Registry 119 (https://www.iana.org/assignments/iana-ipv6-special-registry) is 120 renamed to "Globally Reachable". 122 2.2. Updates to the IPv4 Special-Purpose Address Registry 124 o Limited Broadcast prefix (255.255.255.255/32) - The Reserved-by- 125 Protocol value is changed from False to True. 127 2.3. Updates to the IPv6 Special-Purpose Address Registry 129 o TEREDO prefix (2001::/32) - The Globally Reachable value is 130 changed from False to "N/A [2]". The [2] footnote states: 132 * See [RFC4380] for details. 134 o EID Space for LISP (2001:5::/32) - All footnotes are incremented 135 by 1. 137 o 6to4 (2002::/16) - All footnotes are incremented by 1. 139 o Unique-Local (fc00::/7) - The Globally Reachable value is changed 140 from False to "False [7]". The [7] footnote states: 142 * See [RFC4193] for more details on the routability of Unique- 143 Local addresses. The Unique-Local prefix is drawn from the 144 IPv6 Global Unicast Address range, but is specified as not 145 globally routed. 147 3. Acknowledgements 149 Brian Carpenter and C.M. Heard provided useful comments on initial 150 versions of this document. Daniel Migualt provided an in-depth 151 review that helped strengthen the text within the document. 153 4. References 155 4.1. Normative References 157 [RFC6890] Cotton, M., Vegoda, L., Bonica, R., Ed., and B. Haberman, 158 "Special-Purpose IP Address Registries", BCP 153, 159 RFC 6890, DOI 10.17487/RFC6890, April 2013, 160 . 162 4.2. Informative References 164 [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - 165 Communication Layers", STD 3, RFC 1122, 166 DOI 10.17487/RFC1122, October 1989, 167 . 169 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 170 Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005, 171 . 173 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 174 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 175 2006, . 177 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 178 Network Address Translations (NATs)", RFC 4380, 179 DOI 10.17487/RFC4380, February 2006, 180 . 182 Authors' Addresses 184 Ronald Bonica 185 Juniper Networks 187 Email: rbonica@juniper.net 188 Michelle Cotton 189 ICANN 191 Email: michelle.cotton@icann.org 193 Brian Haberman 194 Johns Hopkins University 196 Email: brian@innovationslab.net 198 Leo Vegoda 199 ICANN 201 Email: leo.vegoda@icann.org