idnits 2.17.1 draft-templin-6man-aeroaddr-03.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 (November 27, 2018) is 1974 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 November 27, 2018 5 Expires: May 31, 2019 7 The AERO Address 8 draft-templin-6man-aeroaddr-03.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 May 31, 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 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 67 1. Introduction 69 IPv6 interfaces are required to have a link-local address that is 70 unique on the link [RFC4291][RFC8200]. Nodes normally derive a link 71 local address through the use of IPv6 StateLess Address Auto 72 Configuration (SLAAC) and employ Duplicate Address Detection (DAD) to 73 ensure uniqueness [RFC4861][RFC4862]. This document presents a 74 method for a node that obtains a delegated prefix to statelessly 75 construct one or more link-local addresses (known as "AERO 76 addresses") that are assured to be unique on the link. 78 Nodes that construct AERO addresses must have assurance that all 79 other nodes on the link employ the same address autoconfiguration 80 method. This can be assured on links for which there is an 81 "IPv6-over-(foo)" specification that mandates use of AERO addresses 82 (e.g., see: [I-D.templin-intarea-6706bis]). Other link types can be 83 administratively coordinated (e.g., via network management) to assure 84 that only AERO addresses are used. 86 2. Terminology 88 The terminology in the normative references applies. 90 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 91 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 92 document are to be interpreted as described in [RFC2119]. Lower case 93 uses of these words are not to be interpreted as carrying RFC2119 94 significance. 96 3. The AERO Address 98 An AERO address is an IPv6 link-local address with an interface 99 identifier based on a prefix that has been delegated to a node for 100 its own exclusive use. 102 For IPv6, AERO addresses begin with the prefix fe80::/64 and include 103 in the interface identifier (i.e., the lower 64 bits) a 64-bit prefix 104 taken from the node's delegated IPv6 prefix. For example, if the 105 node obtains the IPv6 delegated prefix 2001:db8:1000:2000::/56 it 106 constructs its corresponding AERO addresses as: 108 fe80::2001:db8:1000:2000 110 fe80::2001:db8:1000:2001 112 fe80::2001:db8:1000:2002 114 ... etc. ... 116 fe80::2001:db8:1000:20ff 118 For IPv4, AERO addresses are based on an IPv4-mapped IPv6 address 119 [RFC4291] formed from the node's delegated IPv4 prefix. For example, 120 for the IPv4 prefix 192.0.2.16/28 the IPv4-mapped AERO addresses are: 122 fe80::FFFF:192.0.2.16 124 fe80::FFFF:192.0.2.17 126 fe80::FFFF:192.0.2.18 128 ... etc. ... 130 fe80:FFFF:192.0.2.31 132 Administratively-provisioned AERO addresses are allocated from the 133 range fe80::/96, and MUST be managed for uniqueness by the 134 administrative authority for the link. For interfaces that assign 135 IPv4 addresses, the lower 32 bits of the AERO address includes the 136 IPv4 address, e.g., for the IPv4 address 192.0.2.1 the corresponding 137 AERO address is fe80::192.0.2.1. For other interfaces, the lower 32 138 bits of the AERO address includes a unique integer value, e.g., 139 fe80::1, fe80::2, fe80::3, etc. (Note that the address fe80:: is 140 reserved as the IPv6 link-local Subnet Router Anycast address 141 [RFC4291], and the address fe80::ffff:ffff is reserved for special- 142 purposes; hence, these values are not available for administrative 143 assignment.) 144 AERO addresses that embed an IPv6 prefix can be statelessly 145 transformed into an IPv6 Subnet Router Anycast address [RFC4291] and 146 vice-versa. For example, for the AERO address 147 fe80::2001:db8:2000:3000 the corresponding Subnet Router Anycast 148 address is 2001:db8:2000:3000::, and for the IPv6 Subnet Router 149 Anycast address 2001:db8:1:2:: the corresponding AERO address is 150 fe80::2001:db8:1:2. 152 4. Applicability 154 The AERO address is useful for mobile networks that comprise a mobile 155 router and a tethered network of "Internet of Things" devices that 156 travel together with the router as a single unit. The mobile router 157 assigns the AERO address to its upstream interface over which it 158 receives a prefix delegation from a delegating router. The manner 159 for receiving the delegated prefix could be through static 160 configuration or some automated prefix delegation service. 162 Many other use case scenarios are possible (e.g., home networks) but 163 the above case extends to multitudes of applications, e.g., a cell 164 phone and its associated devices, an airplane and its on-board 165 network, etc. A similar uses case exists for a mobile node that 166 obtains a delegated prefix solely for its own internal multi- 167 addressing purposes. These use cases are discussed in 168 [I-D.templin-v6ops-pdhost]. 170 5. Implementation Status 172 Public domain implementations exist that use the AERO address format 173 as described in this document. 175 6. IANA Considerations 177 This document introduces no IANA considerations. 179 7. Security Considerations 181 TBD 183 8. Acknowledgements 185 This work is aligned with the NASA Safe Autonomous Systems Operation 186 (SASO) program under NASA contract number NNA16BD84C. 188 This work is aligned with the FAA as per the SE2025 contract number 189 DTFAWA-15-D-00030. 191 This work is aligned with the Boeing Information Technology (BIT) 192 MobileNet program and the Boeing Research & Technology (BR&T) 193 enterprise autonomy program. 195 9. References 197 9.1. Normative References 199 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 200 Requirement Levels", BCP 14, RFC 2119, 201 DOI 10.17487/RFC2119, March 1997, 202 . 204 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 205 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 206 2006, . 208 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 209 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 210 DOI 10.17487/RFC4861, September 2007, 211 . 213 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 214 Address Autoconfiguration", RFC 4862, 215 DOI 10.17487/RFC4862, September 2007, 216 . 218 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 219 (IPv6) Specification", STD 86, RFC 8200, 220 DOI 10.17487/RFC8200, July 2017, 221 . 223 9.2. Informative References 225 [I-D.templin-intarea-6706bis] 226 Templin, F., "Asymmetric Extended Route Optimization 227 (AERO)", draft-templin-intarea-6706bis-02 (work in 228 progress), October 2018. 230 [I-D.templin-v6ops-pdhost] 231 Templin, F., "Multi-Addressing Considerations for IPv6 232 Prefix Delegation", draft-templin-v6ops-pdhost-21 (work in 233 progress), June 2018. 235 Author's Address 237 Fred L. Templin (editor) 238 Boeing Research & Technology 239 P.O. Box 3707 240 Seattle, WA 98124 241 USA 243 Email: fltemplin@acm.org