idnits 2.17.1 draft-templin-6man-aeroaddr-04.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 (December 17, 2018) is 1955 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) == Outdated reference: A later version (-99) exists of draft-templin-intarea-6706bis-02 == Outdated reference: A later version (-27) exists of draft-templin-v6ops-pdhost-21 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group F. Templin, Ed. 3 Internet-Draft Boeing Research & Technology 4 Intended status: Standards Track December 17, 2018 5 Expires: June 20, 2019 7 The AERO Address 8 draft-templin-6man-aeroaddr-04.txt 10 Abstract 12 IPv6 interfaces are required to have a link-local address that is 13 unique on the link. Nodes normally derive a link local address 14 through the use of IPv6 Stateless Address Autoconfiguration (SLAAC) 15 and employ Duplicate Address Detection (DAD) to ensure uniqueness. 16 This document presents a method for a node that obtains a delegated 17 prefix to statelessly construct a link-local address (known as the 18 "AERO address") that is assured to be unique on the link. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on June 20, 2019. 37 Copyright Notice 39 Copyright (c) 2018 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 2 56 3. The AERO Address . . . . . . . . . . . . . . . . . . . . . . 3 57 4. Applicability . . . . . . . . . . . . . . . . . . . . . . . . 4 58 5. Implementation Status . . . . . . . . . . . . . . . . . . . . 4 59 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4 60 7. Security Considerations . . . . . . . . . . . . . . . . . . . 4 61 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 62 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 63 9.1. Normative References . . . . . . . . . . . . . . . . . . 5 64 9.2. Informative References . . . . . . . . . . . . . . . . . 5 65 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 6 66 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 68 1. Introduction 70 IPv6 interfaces are required to have a link-local address that is 71 unique on the link [RFC4291][RFC8200]. Nodes normally derive a link 72 local address through the use of IPv6 StateLess Address Auto 73 Configuration (SLAAC) and employ Duplicate Address Detection (DAD) to 74 ensure uniqueness [RFC4861][RFC4862]. This document presents a 75 method for a node that obtains a delegated prefix to statelessly 76 construct one or more link-local addresses (known as "AERO 77 addresses") that are assured to be unique on the link. 79 Nodes that construct AERO addresses must have assurance that all 80 other nodes on the link employ the same address autoconfiguration 81 method. This can be assured on links for which there is an 82 "IPv6-over-(foo)" specification that mandates use of AERO addresses 83 (e.g., see: [I-D.templin-intarea-6706bis]). Other link types can be 84 administratively coordinated (e.g., via network management) to assure 85 that only AERO addresses are used. 87 2. Terminology 89 The terminology in the normative references applies. 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 93 document are to be interpreted as described in [RFC2119]. Lower case 94 uses of these words are not to be interpreted as carrying RFC2119 95 significance. 97 3. The AERO Address 99 An AERO address is an IPv6 link-local address with an interface 100 identifier based on a prefix that has been delegated to a node for 101 its own exclusive use. 103 For IPv6, AERO addresses begin with the prefix fe80::/64 and include 104 in the interface identifier (i.e., the lower 64 bits) a 64-bit prefix 105 taken from the node's delegated IPv6 prefix. For example, if the 106 node obtains the IPv6 delegated prefix 2001:db8:1000:2000::/56 it 107 constructs its corresponding AERO addresses as: 109 fe80::2001:db8:1000:2000 111 fe80::2001:db8:1000:2001 113 fe80::2001:db8:1000:2002 115 ... etc. ... 117 fe80::2001:db8:1000:20ff 119 For IPv4, AERO addresses are based on an IPv4-mapped IPv6 address 120 [RFC4291] formed from the node's delegated IPv4 prefix. For example, 121 for the IPv4 prefix 192.0.2.16/28 the IPv4-mapped AERO addresses are: 123 fe80::FFFF:192.0.2.16 125 fe80::FFFF:192.0.2.17 127 fe80::FFFF:192.0.2.18 129 ... etc. ... 131 fe80:FFFF:192.0.2.31 133 Administratively-provisioned AERO addresses are allocated from the 134 range fe80::/96, and MUST be managed for uniqueness by the 135 administrative authority for the link. For interfaces that assign 136 IPv4 addresses, the lower 32 bits of the AERO address includes the 137 IPv4 address, e.g., for the IPv4 address 192.0.2.1 the corresponding 138 AERO address is fe80::192.0.2.1. For other interfaces, the lower 32 139 bits of the AERO address includes a unique integer value, e.g., 140 fe80::1, fe80::2, fe80::3, etc. (Note that the address fe80:: is 141 reserved as the IPv6 link-local Subnet Router Anycast address 142 [RFC4291], and the address fe80::ffff:ffff is reserved for special- 143 purposes; hence, these values are not available for administrative 144 assignment.) 145 AERO addresses that embed an IPv6 prefix can be statelessly 146 transformed into an IPv6 Subnet Router Anycast address [RFC4291] and 147 vice-versa. For example, for the AERO address 148 fe80::2001:db8:2000:3000 the corresponding Subnet Router Anycast 149 address is 2001:db8:2000:3000::, and for the IPv6 Subnet Router 150 Anycast address 2001:db8:1:2:: the corresponding AERO address is 151 fe80::2001:db8:1:2. 153 4. Applicability 155 The AERO address is useful for mobile networks that comprise a mobile 156 router and a tethered network of "Internet of Things" devices that 157 travel together with the router as a single unit. The mobile router 158 assigns the AERO address to its upstream interface over which it 159 receives a prefix delegation from a delegating router. The manner 160 for receiving the delegated prefix could be through static 161 configuration or some automated prefix delegation service. 163 Many other use case scenarios are possible (e.g., home networks) but 164 the above case extends to multitudes of applications, e.g., a cell 165 phone and its associated devices, an airplane and its on-board 166 network, etc. A similar uses case exists for a mobile node that 167 obtains a delegated prefix solely for its own internal multi- 168 addressing purposes. These use cases are discussed in 169 [I-D.templin-v6ops-pdhost]. 171 5. Implementation Status 173 Public domain implementations exist that use the AERO address format 174 as described in this document. 176 6. IANA Considerations 178 This document introduces no IANA considerations. 180 7. Security Considerations 182 TBD 184 8. Acknowledgements 186 This work is aligned with the NASA Safe Autonomous Systems Operation 187 (SASO) program under NASA contract number NNA16BD84C. 189 This work is aligned with the FAA as per the SE2025 contract number 190 DTFAWA-15-D-00030. 192 This work is aligned with the Boeing Information Technology (BIT) 193 MobileNet program and the Boeing Research & Technology (BR&T) 194 enterprise autonomy program. 196 9. References 198 9.1. Normative References 200 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 201 Requirement Levels", BCP 14, RFC 2119, 202 DOI 10.17487/RFC2119, March 1997, 203 . 205 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 206 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 207 2006, . 209 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 210 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 211 DOI 10.17487/RFC4861, September 2007, 212 . 214 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 215 Address Autoconfiguration", RFC 4862, 216 DOI 10.17487/RFC4862, September 2007, 217 . 219 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 220 (IPv6) Specification", STD 86, RFC 8200, 221 DOI 10.17487/RFC8200, July 2017, 222 . 224 9.2. Informative References 226 [I-D.templin-intarea-6706bis] 227 Templin, F., "Asymmetric Extended Route Optimization 228 (AERO)", draft-templin-intarea-6706bis-02 (work in 229 progress), October 2018. 231 [I-D.templin-v6ops-pdhost] 232 Templin, F., "Multi-Addressing Considerations for IPv6 233 Prefix Delegation", draft-templin-v6ops-pdhost-21 (work in 234 progress), June 2018. 236 Appendix A. Change Log 238 << RFC Editor - remove prior to publication >> 240 Changes from -03 to -04: 242 o Added this change log 244 Author's Address 246 Fred L. Templin (editor) 247 Boeing Research & Technology 248 P.O. Box 3707 249 Seattle, WA 98124 250 USA 252 Email: fltemplin@acm.org