idnits 2.17.1 draft-templin-aerolink-69.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 'Obsoletes: ' line in the draft header should list only the _numbers_ of the RFCs which will be obsoleted by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 27, 2016) is 2830 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) == Missing Reference: 'I-D.taylor-v6ops-fragdrop' is mentioned on line 973, but not defined == Unused Reference: 'RFC0768' is defined on line 2613, but no explicit reference was found in the text == Unused Reference: 'RFC6434' is defined on line 2678, but no explicit reference was found in the text == Unused Reference: 'RFC0879' is defined on line 2722, but no explicit reference was found in the text == Unused Reference: 'RFC1930' is defined on line 2743, but no explicit reference was found in the text == Unused Reference: 'RFC2675' is defined on line 2761, but no explicit reference was found in the text == Unused Reference: 'RFC4459' is defined on line 2822, but no explicit reference was found in the text == Unused Reference: 'RFC4821' is defined on line 2845, but no explicit reference was found in the text == Unused Reference: 'RFC4994' is defined on line 2854, but no explicit reference was found in the text == Unused Reference: 'RFC5494' is defined on line 2878, but no explicit reference was found in the text == Unused Reference: 'RFC5720' is defined on line 2897, but no explicit reference was found in the text == Unused Reference: 'RFC6146' is defined on line 2916, but no explicit reference was found in the text == Unused Reference: 'RFC6204' is defined on line 2925, but no explicit reference was found in the text == Unused Reference: 'RFC6241' is defined on line 2935, but no explicit reference was found in the text == Unused Reference: 'RFC6355' is defined on line 2944, but no explicit reference was found in the text == Unused Reference: 'RFC6691' is defined on line 2958, but no explicit reference was found in the text == Unused Reference: 'RFC6935' is defined on line 2970, but no explicit reference was found in the text == Unused Reference: 'RFC6936' is defined on line 2975, but no explicit reference was found in the text == Unused Reference: 'RFC6980' is defined on line 2984, but no explicit reference was found in the text == Unused Reference: 'RFC7078' is defined on line 2989, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2460 (Obsoleted by RFC 8200) ** Obsolete normative reference: RFC 3315 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 3633 (Obsoleted by RFC 8415) ** Obsolete normative reference: RFC 6434 (Obsoleted by RFC 8504) == Outdated reference: A later version (-21) exists of draft-ietf-dhc-sedhcpv6-13 == Outdated reference: A later version (-13) exists of draft-ietf-intarea-tunnels-03 == Outdated reference: A later version (-05) exists of draft-ietf-nvo3-gue-04 == Outdated reference: A later version (-04) exists of draft-templin-intarea-grefrag-02 -- Obsolete informational reference (is this intentional?): RFC 879 (Obsoleted by RFC 7805, RFC 9293) -- Obsolete informational reference (is this intentional?): RFC 1981 (Obsoleted by RFC 8201) -- Obsolete informational reference (is this intentional?): RFC 5246 (Obsoleted by RFC 8446) -- Obsolete informational reference (is this intentional?): RFC 5996 (Obsoleted by RFC 7296) -- Obsolete informational reference (is this intentional?): RFC 6204 (Obsoleted by RFC 7084) -- Obsolete informational reference (is this intentional?): RFC 6691 (Obsoleted by RFC 9293) Summary: 4 errors (**), 0 flaws (~~), 26 warnings (==), 7 comments (--). 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 Obsoletes: rfc5320, rfc5558, rfc5720, July 27, 2016 5 rfc6179, rfc6706 (if 6 approved) 7 Intended status: Standards Track 8 Expires: January 28, 2017 10 Asymmetric Extended Route Optimization (AERO) 11 draft-templin-aerolink-69.txt 13 Abstract 15 This document specifies the operation of IP over tunnel virtual links 16 using Asymmetric Extended Route Optimization (AERO). Nodes attached 17 to AERO links can exchange packets via trusted intermediate routers 18 that provide forwarding services to reach off-link destinations and 19 redirection services for route optimization. AERO provides an IPv6 20 link-local address format known as the AERO address that supports 21 operation of the IPv6 Neighbor Discovery (ND) protocol and links IPv6 22 ND to IP forwarding. Admission control, address/prefix provisioning 23 and mobility are supported by the Dynamic Host Configuration Protocol 24 for IPv6 (DHCPv6), and route optimization is naturally supported 25 through dynamic neighbor cache updates. Although DHCPv6 and IPv6 ND 26 messaging are used in the control plane, both IPv4 and IPv6 are 27 supported in the data plane. AERO is a widely-applicable tunneling 28 solution using standard control messaging exchanges as described in 29 this document. 31 Status of This Memo 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering 37 Task Force (IETF). Note that other groups may also distribute 38 working documents as Internet-Drafts. The list of current Internet- 39 Drafts is at http://datatracker.ietf.org/drafts/current/. 41 Internet-Drafts are draft documents valid for a maximum of six months 42 and may be updated, replaced, or obsoleted by other documents at any 43 time. It is inappropriate to use Internet-Drafts as reference 44 material or to cite them other than as "work in progress." 46 This Internet-Draft will expire on January 28, 2017. 48 Copyright Notice 50 Copyright (c) 2016 IETF Trust and the persons identified as the 51 document authors. All rights reserved. 53 This document is subject to BCP 78 and the IETF Trust's Legal 54 Provisions Relating to IETF Documents 55 (http://trustee.ietf.org/license-info) in effect on the date of 56 publication of this document. Please review these documents 57 carefully, as they describe your rights and restrictions with respect 58 to this document. Code Components extracted from this document must 59 include Simplified BSD License text as described in Section 4.e of 60 the Trust Legal Provisions and are provided without warranty as 61 described in the Simplified BSD License. 63 Table of Contents 65 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 66 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 3. Asymmetric Extended Route Optimization (AERO) . . . . . . . . 6 68 3.1. AERO Link Reference Model . . . . . . . . . . . . . . . . 6 69 3.2. AERO Link Node Types . . . . . . . . . . . . . . . . . . 8 70 3.3. AERO Addresses . . . . . . . . . . . . . . . . . . . . . 9 71 3.4. AERO Interface Characteristics . . . . . . . . . . . . . 10 72 3.5. AERO Link Registration . . . . . . . . . . . . . . . . . 11 73 3.6. AERO Interface Initialization . . . . . . . . . . . . . . 12 74 3.6.1. AERO Relay Behavior . . . . . . . . . . . . . . . . . 12 75 3.6.2. AERO Server Behavior . . . . . . . . . . . . . . . . 12 76 3.6.3. AERO Client Behavior . . . . . . . . . . . . . . . . 13 77 3.6.4. AERO Forwarding Agent Behavior . . . . . . . . . . . 13 78 3.7. AERO Routing System . . . . . . . . . . . . . . . . . . . 13 79 3.8. AERO Interface Neighbor Cache Maintenace . . . . . . . . 15 80 3.9. AERO Interface Sending Algorithm . . . . . . . . . . . . 16 81 3.10. AERO Interface Encapsulation and Re-encapsulation . . . . 18 82 3.11. AERO Interface Decapsulation . . . . . . . . . . . . . . 19 83 3.12. AERO Interface Data Origin Authentication . . . . . . . . 19 84 3.13. AERO Interface Packet Size Issues . . . . . . . . . . . . 20 85 3.14. AERO Interface Error Handling . . . . . . . . . . . . . . 21 86 3.15. AERO Router Discovery, Prefix Delegation and Address 87 Configuration . . . . . . . . . . . . . . . . . . . . . . 25 88 3.15.1. AERO DHCPv6 Service Model . . . . . . . . . . . . . 25 89 3.15.2. AERO Client Behavior . . . . . . . . . . . . . . . . 25 90 3.15.3. AERO Server Behavior . . . . . . . . . . . . . . . . 28 91 3.15.4. Deleting Link Registrations . . . . . . . . . . . . 32 92 3.16. AERO Forwarding Agent Behavior . . . . . . . . . . . . . 32 93 3.17. AERO Intradomain Route Optimization . . . . . . . . . . . 33 94 3.17.1. Reference Operational Scenario . . . . . . . . . . . 33 95 3.17.2. Concept of Operations . . . . . . . . . . . . . . . 35 96 3.17.3. Message Format . . . . . . . . . . . . . . . . . . . 35 97 3.17.4. Sending Predirects . . . . . . . . . . . . . . . . . 36 98 3.17.5. Re-encapsulating and Relaying Predirects . . . . . . 37 99 3.17.6. Processing Predirects and Sending Redirects . . . . 38 100 3.17.7. Re-encapsulating and Relaying Redirects . . . . . . 40 101 3.17.8. Processing Redirects . . . . . . . . . . . . . . . . 40 102 3.17.9. Server-Oriented Redirection . . . . . . . . . . . . 41 103 3.17.10. Route Optimization Policy . . . . . . . . . . . . . 41 104 3.17.11. Route Optimization and Multiple ACPs . . . . . . . . 42 105 3.18. Neighbor Unreachability Detection (NUD) . . . . . . . . . 42 106 3.19. Mobility Management . . . . . . . . . . . . . . . . . . . 43 107 3.19.1. Announcing Link-Layer Address Changes . . . . . . . 43 108 3.19.2. Bringing New Links Into Service . . . . . . . . . . 43 109 3.19.3. Removing Existing Links from Service . . . . . . . . 43 110 3.19.4. Moving to a New Server . . . . . . . . . . . . . . . 44 111 3.19.5. Packet Queueing for Mobility . . . . . . . . . . . . 44 112 3.20. Proxy AERO . . . . . . . . . . . . . . . . . . . . . . . 45 113 3.21. Extending AERO Links Through Security Gateways . . . . . 47 114 3.22. Extending IPv6 AERO Links to the Internet . . . . . . . . 49 115 3.23. Encapsulation Protocol Version Considerations . . . . . . 52 116 3.24. Multicast Considerations . . . . . . . . . . . . . . . . 53 117 3.25. Operation on AERO Links Without DHCPv6 Services . . . . . 53 118 3.26. Operation on Server-less AERO Links . . . . . . . . . . . 53 119 3.27. Manually-Configured AERO Tunnels . . . . . . . . . . . . 53 120 3.28. Intradomain Routing . . . . . . . . . . . . . . . . . . . 54 121 4. Implementation Status . . . . . . . . . . . . . . . . . . . . 54 122 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 54 123 6. Security Considerations . . . . . . . . . . . . . . . . . . . 54 124 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 55 125 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 56 126 8.1. Normative References . . . . . . . . . . . . . . . . . . 56 127 8.2. Informative References . . . . . . . . . . . . . . . . . 58 128 Appendix A. AERO Alternate Encapsulations . . . . . . . . . . . 65 129 Appendix B. When to Insert an Encapsulation Fragment Header . . 66 130 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 67 132 1. Introduction 134 This document specifies the operation of IP over tunnel virtual links 135 using Asymmetric Extended Route Optimization (AERO). The AERO link 136 can be used for tunneling to neighboring nodes over either IPv6 or 137 IPv4 networks, i.e., AERO views the IPv6 and IPv4 networks as 138 equivalent links for tunneling. Nodes attached to AERO links can 139 exchange packets via trusted intermediate routers that provide 140 forwarding services to reach off-link destinations and redirection 141 services for route optimization [RFC5522]. 143 AERO provides an IPv6 link-local address format known as the AERO 144 address that supports operation of the IPv6 Neighbor Discovery (ND) 145 [RFC4861] protocol and links IPv6 ND to IP forwarding. Admission 146 control, address/prefix provisioning and mobility are supported by 147 the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) [RFC3315], 148 and route optimization is naturally supported through dynamic 149 neighbor cache updates. Although DHCPv6 and IPv6 ND messaging are 150 used in the control plane, both IPv4 and IPv6 can be used in the data 151 plane. AERO is a widely-applicable tunneling solution using standard 152 control messaging exchanges as described in this document. The 153 remainder of this document presents the AERO specification. 155 2. Terminology 157 The terminology in the normative references applies; the following 158 terms are defined within the scope of this document: 160 AERO link 161 a Non-Broadcast, Multiple Access (NBMA) tunnel virtual overlay 162 configured over a node's attached IPv6 and/or IPv4 networks. All 163 nodes on the AERO link appear as single-hop neighbors from the 164 perspective of the virtual overlay even though they may be 165 separated by many underlying network hops. AERO can also operate 166 over native multiple access link types (e.g., Ethernet, WiFi etc.) 167 when a tunnel virtual overlay is not needed. 169 AERO interface 170 a node's attachment to an AERO link. Nodes typically have a 171 single AERO interface; support for multiple AERO interfaces is 172 also possible but out of scope for this document. AERO interfaces 173 do not require Duplicate Address Detection (DAD) and therefore set 174 the administrative variable DupAddrDetectTransmits to zero 175 [RFC4862]. 177 AERO address 178 an IPv6 link-local address constructed as specified in Section 3.3 179 and assigned to a Client's AERO interface. 181 AERO node 182 a node that is connected to an AERO link and that participates in 183 IPv6 ND and DHCPv6 messaging over the link. 185 AERO Client ("Client") 186 a node that issues DHCPv6 messages to receive IP Prefix 187 Delegations (PDs) from one or more AERO Servers. Following PD, 188 the Client assigns an AERO address to the AERO interface for use 189 in DHCPv6 and IPv6 ND exchanges with other AERO nodes. 191 AERO Server ("Server") 192 a node that configures an AERO interface to provide default 193 forwarding and DHCPv6 services for AERO Clients. The Server 194 assigns an administratively provisioned IPv6 link-local unicast 195 address to support the operation of DHCPv6 and the IPv6 ND 196 protocol. An AERO Server can also act as an AERO Relay. 198 AERO Relay ("Relay") 199 a node that configures an AERO interface to relay IP packets 200 between nodes on the same AERO link and/or forward IP packets 201 between the AERO link and the native Internetwork. The Relay 202 assigns an administratively provisioned IPv6 link-local unicast 203 address to the AERO interface the same as for a Server. An AERO 204 Relay can also act as an AERO Server. 206 AERO Forwarding Agent ("Forwarding Agent") 207 a node that performs data plane forwarding services as a companion 208 to an AERO Server. 210 ingress tunnel endpoint (ITE) 211 an AERO interface endpoint that injects tunneled packets into an 212 AERO link. 214 egress tunnel endpoint (ETE) 215 an AERO interface endpoint that receives tunneled packets from an 216 AERO link. 218 underlying network 219 a connected IPv6 or IPv4 network routing region over which the 220 tunnel virtual overlay is configured. A typical example is an 221 enterprise network, but many other use cases are also in scope. 223 underlying interface 224 an AERO node's interface point of attachment to an underlying 225 network. 227 link-layer address 228 an IP address assigned to an AERO node's underlying interface. 229 When UDP encapsulation is used, the UDP port number is also 230 considered as part of the link-layer address; otherwise, UDP port 231 number is set to the constant value '0'. Link-layer addresses are 232 used as the encapsulation header source and destination addresses. 234 network layer address 235 the source or destination address of the encapsulated IP packet. 237 end user network (EUN) 238 an internal virtual or external edge IP network that an AERO 239 Client connects to the rest of the network via the AERO interface. 241 AERO Service Prefix (ASP) 242 an IP prefix associated with the AERO link and from which AERO 243 Client Prefixes (ACPs) are derived (for example, the IPv6 ACP 244 2001:db8:1:2::/64 is derived from the IPv6 ASP 2001:db8::/32). 246 AERO Client Prefix (ACP) 247 a more-specific IP prefix taken from an ASP and delegated to a 248 Client. 250 Throughout the document, the simple terms "Client", "Server" and 251 "Relay" refer to "AERO Client", "AERO Server" and "AERO Relay", 252 respectively. Capitalization is used to distinguish these terms from 253 DHCPv6 client/server/relay [RFC3315]. 255 The terminology of DHCPv6 [RFC3315] and IPv6 ND [RFC4861] (including 256 the names of node variables and protocol constants) applies to this 257 document. Also throughout the document, the term "IP" is used to 258 generically refer to either Internet Protocol version (i.e., IPv4 or 259 IPv6). 261 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 262 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 263 document are to be interpreted as described in [RFC2119]. Lower case 264 uses of these words are not to be interpreted as carrying RFC2119 265 significance. 267 3. Asymmetric Extended Route Optimization (AERO) 269 The following sections specify the operation of IP over Asymmetric 270 Extended Route Optimization (AERO) links: 272 3.1. AERO Link Reference Model 273 .-(::::::::) 274 .-(:::: IP ::::)-. 275 (:: Internetwork ::) 276 `-(::::::::::::)-' 277 `-(::::::)-' 278 | 279 +--------------+ +--------+-------+ +--------------+ 280 |AERO Server S1| | AERO Relay R1 | |AERO Server S2| 281 | Nbr: C1; R1 | | Nbr: S1; S2 | | Nbr: C2; R1 | 282 | default->R1 | |(P1->S1; P2->S2)| | default->R1 | 283 | P1->C1 | | ASP A1 | | P2->C2 | 284 +-------+------+ +--------+-------+ +------+-------+ 285 | | | 286 X---+---+-------------------+------------------+---+---X 287 | AERO Link | 288 +-----+--------+ +--------+-----+ 289 |AERO Client C1| |AERO Client C2| 290 | Nbr: S1 | | Nbr: S2 | 291 | default->S1 | | default->S2 | 292 | ACP P1 | | ACP P2 | 293 +--------------+ +--------------+ 294 .-. .-. 295 ,-( _)-. ,-( _)-. 296 .-(_ IP )-. .-(_ IP )-. 297 (__ EUN ) (__ EUN ) 298 `-(______)-' `-(______)-' 299 | | 300 +--------+ +--------+ 301 | Host H1| | Host H2| 302 +--------+ +--------+ 304 Figure 1: AERO Link Reference Model 306 Figure 1 presents the AERO link reference model. In this model: 308 o AERO Relay R1 aggregates AERO Service Prefix (ASP) A1, acts as a 309 default router for its associated Servers S1 and S2, and connects 310 the AERO link to the rest of the IP Internetwork. 312 o AERO Servers S1 and S2 associate with Relay R1 and also act as 313 default routers for their associated Clients C1 and C2. 315 o AERO Clients C1 and C2 associate with Servers S1 and S2, 316 respectively. They receive AERO Client Prefix (ACP) delegations 317 P1 and P2, and also act as default routers for their associated 318 physical or internal virtual EUNs. (Alternatively, clients can 319 act as multi-addressed hosts without serving any EUNs). 321 o Simple hosts H1 and H2 attach to the EUNs served by Clients C1 and 322 C2, respectively. 324 Each AERO node maintains an AERO interface neighbor cache and an IP 325 forwarding table. For example, AERO Relay R1 in the diagram has 326 neighbor cache entries for Servers S1 and S2 as well as IP forwarding 327 table entries for the ACPs delegated to Clients C1 and C2. In common 328 operational practice, there may be many additional Relays, Servers 329 and Clients. (Although not shown in the figure, AERO Forwarding 330 Agents may also be provided for data plane forwarding offload 331 services.) 333 3.2. AERO Link Node Types 335 AERO Relays provide default forwarding services to AERO Servers. 336 Relays forward packets between neighbors connected to the same AERO 337 link and also forward packets between the AERO link and the native IP 338 Internetwork. Relays present the AERO link to the native 339 Internetwork as a set of one or more AERO Service Prefixes (ASPs) and 340 serve as a gateway between the AERO link and the Internetwork. AERO 341 Relays maintain an AERO interface neighbor cache entry for each AERO 342 Server, and maintain an IP forwarding table entry for each AERO 343 Client Prefix (ACP). AERO Relays can also be configured to act as 344 AERO Servers. 346 AERO Servers provide default forwarding services to AERO Clients. 347 Each Server also peers with each Relay in a dynamic routing protocol 348 instance to advertise its list of associated ACPs. Servers configure 349 a DHCPv6 server function to facilitate Prefix Delegation (PD) 350 exchanges with Clients. Each delegated prefix becomes an ACP taken 351 from an ASP. Servers forward packets between AERO interface 352 neighbors, and maintain an AERO interface neighbor cache entry for 353 each AERO Relay. They also maintain both neighbor cache entries and 354 IP forwarding table entries for each of their associated Clients. 355 AERO Servers can also be configured to act as AERO Relays. 357 AERO Clients act as requesting routers to receive ACPs through DHCPv6 358 PD exchanges with AERO Servers over the AERO link. Each Client MAY 359 associate with a single Server or with multiple Servers, e.g., for 360 fault tolerance, load balancing, etc. Each IPv6 Client receives at 361 least a /64 IPv6 ACP, and may receive even shorter prefixes. 362 Similarly, each IPv4 Client receives at least a /32 IPv4 ACP (i.e., a 363 singleton IPv4 address), and may receive even shorter prefixes. AERO 364 Clients maintain an AERO interface neighbor cache entry for each of 365 their associated Servers as well as for each of their correspondent 366 Clients. 368 AERO Forwarding Agents provide data plane forwarding services as 369 companions to AERO Servers. Note that while Servers are required to 370 perform both control and data plane operations on their own behalf, 371 they may optionally enlist the services of special-purpose Forwarding 372 Agents to offload data plane traffic. 374 3.3. AERO Addresses 376 An AERO address is an IPv6 link-local address with an embedded ACP 377 and assigned to a Client's AERO interface. The AERO address is 378 formed as follows: 380 fe80::[ACP] 382 For IPv6, the AERO address begins with the prefix fe80::/64 and 383 includes in its interface identifier the base prefix taken from the 384 Client's IPv6 ACP. The base prefix is determined by masking the ACP 385 with the prefix length. For example, if the AERO Client receives the 386 IPv6 ACP: 388 2001:db8:1000:2000::/56 390 it constructs its AERO address as: 392 fe80::2001:db8:1000:2000 394 For IPv4, the AERO address is formed from the lower 64 bits of an 395 IPv4-mapped IPv6 address [RFC4291] that includes the base prefix 396 taken from the Client's IPv4 ACP. For example, if the AERO Client 397 receives the IPv4 ACP: 399 192.0.2.32/28 401 it constructs its AERO address as: 403 fe80::FFFF:192.0.2.32 405 The AERO address remains stable as the Client moves between 406 topological locations, i.e., even if its link-layer addresses change. 408 NOTE: In some cases, prospective neighbors may not have advanced 409 knowledge of the Client's ACP length and may therefore send initial 410 IPv6 ND messages with an AERO destination address that matches the 411 ACP but does not correspond to the base prefix. For example, if the 412 Client receives the IPv6 ACP 2001:db8:1000:2000::/56 then 413 subsequently receives an IPv6 ND message with destination address 414 fe80::2001:db8:1000:2001, it accepts the message as though it were 415 addressed to fe80::2001:db8:1000:2000. 417 3.4. AERO Interface Characteristics 419 AERO interfaces use encapsulation (see: Section 3.10) to exchange 420 packets with neighbors attached to the AERO link. AERO interfaces 421 maintain a neighbor cache, and AERO nodes use both DHCPv6 PD and IPv6 422 ND control messaging. AERO Clients send DHCPv6 Solicit, Rebind, 423 Renew and Release messages to AERO Servers, which respond with DHCPv6 424 Reply messages. These messages result in the creation, modification 425 and deletion of neighbor cache entries. 427 AERO interfaces use unicast IPv6 ND Neighbor Solicitation (NS), 428 Neighbor Advertisement (NA), Router Solicitation (RS) and Router 429 Advertisement (RA) messages the same as for any IPv6 link. AERO 430 interfaces use two IPv6 ND redirection message types -- the first 431 known as a Predirect message and the second being the standard 432 Redirect message (see Section 3.17). AERO links further use link- 433 local-only addressing; hence, AERO nodes ignore any Prefix 434 Information Options (PIOs) they may receive in RA messages over an 435 AERO interface. 437 AERO interface ND messages include one or more Source/Target Link- 438 Layer Address Options (S/TLLAOs) formatted as shown in Figure 2: 440 0 1 2 3 441 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 442 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 443 | Type = 2 | Length = 3 | Reserved | 444 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 445 | Link ID | NDSCPs | DSCP #1 |Prf| DSCP #2 |Prf| 446 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 447 | DSCP #3 |Prf| DSCP #4 |Prf| .... 448 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 449 | UDP Port Number | | 450 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + 451 | | 452 + + 453 | IP Address | 454 + + 455 | | 456 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 457 | | 458 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 460 Figure 2: AERO Source/Target Link-Layer Address Option (S/TLLAO) 461 Format 463 In this format, Link ID is an integer value between 0 and 255 464 corresponding to an underlying interface of the target node, NDSCPs 465 encodes an integer value between 0 and 64 indicating the number of 466 Differentiated Services Code Point (DSCP) octets that follow. Each 467 DSCP octet is a 6-bit integer DSCP value followed by a 2-bit 468 Preference ("Prf") value. Each DSCP value encodes an integer between 469 0 and 63 associated with this Link ID, where the value 0 means 470 "default" and other values are interpreted as specified in [RFC2474]. 471 The 'Prf' qualifier for each DSCP value is set to the value 0 472 ("deprecated'), 1 ("low"), 2 ("medium"), or 3 ("high") to indicate a 473 preference level for packet forwarding purposes. When a particular 474 DSCP value is not specified, its preference level is set to "medium" 475 by default. 477 UDP Port Number and IP Address are set to the addresses used by the 478 target node when it sends encapsulated packets over the underlying 479 interface. When UDP is not used as part of the encapsulation, UDP 480 Port Number is set to the value '0'. When the encapsulation IP 481 address family is IPv4, IP Address is formed as an IPv4-mapped IPv6 482 address [RFC4291]. 484 AERO interfaces may be configured over multiple underlying 485 interfaces. For example, common mobile handheld devices have both 486 wireless local area network ("WLAN") and cellular wireless links. 487 These links are typically used "one at a time" with low-cost WLAN 488 preferred and highly-available cellular wireless as a standby. In a 489 more complex example, aircraft frequently have many wireless data 490 link types (e.g. satellite-based, terrestrial, air-to-air 491 directional, etc.) with diverse performance and cost properties. 493 If a Client's multiple underlying interfaces are used "one at a time" 494 (i.e., all other interfaces are in standby mode while one interface 495 is active), then Redirect, Predirect and unsolicited NA messages 496 include only a single TLLAO with Link ID set to a constant value. 498 If the Client has multiple active underlying interfaces, then from 499 the perspective of IPv6 ND it would appear to have multiple link- 500 layer addresses. In that case, Redirect and Predirect messages MAY 501 include multiple TLLAOs -- each with a Link ID that corresponds to a 502 specific underlying interface of the Client. 504 3.5. AERO Link Registration 506 When an administrative authority first deploys a set of AERO Relays 507 and Servers that comprise an AERO link, they also assign a unique 508 domain name for the link, e.g., "linkupnetworks.example.com". Next, 509 if administrative policy permits Clients within the domain to serve 510 as correspondent nodes for Internet mobile nodes, the administrative 511 authority adds a Fully Qualified Domain Name (FQDN) for each of the 512 AERO link's ASPs to the Domain Name System (DNS) [RFC1035]. The FQDN 513 is based on the suffix "aero.linkupnetworks.net" with a prefix formed 514 from the wildcard-terminated reverse mapping of the ASP 515 [RFC3596][RFC4592], and resolves to a DNS PTR resource record. For 516 example, for the ASP '2001:db8:1::/48' within the domain name 517 "linkupnetworks.example.com", the DNS database contains: 519 '*.1.0.0.0.8.b.d.0.1.0.0.2.aero.linkupnetworks.net. PTR 520 linkupnetworks.example.com' 522 This DNS registration advertises the AERO link's ASPs to prospective 523 correspondent nodes. 525 3.6. AERO Interface Initialization 527 3.6.1. AERO Relay Behavior 529 When a Relay enables an AERO interface, it first assigns an 530 administratively provisioned link-local address fe80::ID to the 531 interface. Each fe80::ID address MUST be unique among all AERO nodes 532 on the link, and MUST NOT collide with any potential AERO addresses 533 nor the special addresses fe80:: and fe80::ffff:ffff:ffff:ffff. (The 534 fe80::ID addresses are typically taken from the available range 535 fe80::/96, e.g., as fe80::1, fe80::2, fe80::3, etc.) The Relay then 536 engages in a dynamic routing protocol session with all Servers on the 537 link (see: Section 3.7), and advertises its assigned ASP prefixes 538 into the native IP Internetwork. 540 Each Relay subsequently maintains an IP forwarding table entry for 541 each ACP covered by its ASP(s), and maintains a neighbor cache entry 542 for each Server on the link. Relays exchange NS/NA messages with 543 AERO link neighbors the same as for any AERO node, however they 544 typically do not perform explicit Neighbor Unreachability Detection 545 (NUD) (see: Section 3.18) since the dynamic routing protocol already 546 provides reachability confirmation. 548 3.6.2. AERO Server Behavior 550 When a Server enables an AERO interface, it assigns an 551 administratively provisioned link-local address fe80::ID the same as 552 for Relays. The Server further configures a DHCPv6 server function 553 to facilitate DHCPv6 PD exchanges with AERO Clients. The Server 554 maintains a neighbor cache entry for each Relay on the link, and 555 manages per-ACP neighbor cache entries and IP forwarding table 556 entries based on control message exchanges. Each Server also engages 557 in a dynamic routing protocol with each Relay on the link (see: 558 Section 3.7). 560 When the Server receives an NS/RS message from a Client on the AERO 561 interface it returns an NA/RA message. The Server further provides a 562 simple link-layer conduit between AERO interface neighbors. 563 Therefore, packets enter the Server's AERO interface from the link 564 layer and are forwarded back out the link layer without ever leaving 565 the AERO interface and therefore without ever disturbing the network 566 layer. 568 3.6.3. AERO Client Behavior 570 When a Client enables an AERO interface, it uses the special address 571 fe80::ffff:ffff:ffff:ffff to obtain one or more ACPs from an AERO 572 Server via DHCPv6 PD. Next, it assigns the corresponding AERO 573 address(es) to the AERO interface and creates a neighbor cache entry 574 for the Server, i.e., the DHCPv6 PD exchange bootstraps 575 autoconfiguration of unique link-local address(es). The Client 576 maintains a neighbor cache entry for each of its Servers and each of 577 its active correspondent Clients. When the Client receives Redirect/ 578 Predirect messages on the AERO interface it updates or creates 579 neighbor cache entries, including link-layer address information. 581 3.6.4. AERO Forwarding Agent Behavior 583 When a Forwarding Agent enables an AERO interface, it assigns the 584 same link-local address(es) as the companion AERO Server. The 585 Forwarding Agent thereafter provides data plane forwarding services 586 based solely on the forwarding information assigned to it by the 587 companion AERO Server. 589 3.7. AERO Routing System 591 The AERO routing system is based on a private instance of the Border 592 Gateway Protocol (BGP) [RFC4271] that is coordinated between Relays 593 and Servers and does not interact with either the public Internet BGP 594 routing system or the native IP Internetwork interior routing system. 595 Relays advertise only a small and unchanging set of ASPs to the 596 native routing system instead of the full dynamically changing set of 597 ACPs. 599 In a reference deployment, each AERO Server is configured as an 600 Autonomous System Border Router (ASBR) for a stub Autonomous System 601 (AS) using an AS Number (ASN) that is unique within the BGP instance, 602 and each Server further peers with each Relay but does not peer with 603 other Servers. Similarly, Relays do not peer with each other, since 604 they will reliably receive all updates from all Servers and will 605 therefore have a consistent view of the AERO link ACP delegations. 607 Each Server maintains a working set of associated ACPs, and 608 dynamically announces new ACPs and withdraws departed ACPs in its BGP 609 updates to Relays. Clients are expected to remain associated with 610 their current Servers for extended timeframes, however Servers SHOULD 611 selectively suppress BGP updates for impatient Clients that 612 repeatedly associate and disassociate with them in order to dampen 613 routing churn. 615 Each Relay configures a black-hole route for each of its ASPs. By 616 black-holing the ASPs, the Relay will maintain forwarding table 617 entries only for the ACPs that are currently active, and all other 618 ACPs will correctly result in destination unreachable failures due to 619 the black hole route. 621 Scaling properties of the AERO routing system are limited by the 622 number of BGP routes that can be carried by Relays. Assuming O(10^6) 623 as a reasonable maximum number of BGP routes, this means that O(10^6) 624 Clients can be serviced by a single set of Relays. A means of 625 increasing scaling would be to assign a different set of Relays for 626 each set of ASPs. In that case, each Server still peers with each 627 Relay, but the Server institutes route filters so that each set of 628 Relays only receives BGP updates for the ASPs they aggregate. For 629 example, if the ASP for the AERO link is 2001:db8::/32, a first set 630 of Relays could service the ASP segment 2001:db8::/40, a second set 631 of Relays could service 2001:db8:0100::/40, a third set could service 632 2001:db8:0200::/40, etc. 634 Assuming up to O(10^3) sets of Relays, the AERO routing system can 635 then accommodate O(10^9) ACPs with no additional overhead for Servers 636 and Relays (for example, it should be possible to service 4 billion 637 /64 ACPs taken from a /32 ASP and even more for shorter ASPs). In 638 this way, each set of Relays services a specific set of ASPs that 639 they advertise to the native routing system, and each Server 640 configures ASP-specific routes that list the correct set of Relays as 641 next hops. This arrangement also allows for natural incremental 642 deployment, and can support small scale initial deployments followed 643 by dynamic deployment of additional Clients, Servers and Relays 644 without disturbing the already-deployed base. 646 Note that in an alternate routing arrangement each set of Relays 647 could advertise the aggregated ASP for the link into the native 648 routing system even though each Relay services only a segment of the 649 ASP. In that case, a Relay upon receiving a packet with a 650 destination address covered by the ASP segment of another Relay can 651 simply tunnel the packet to the correct Relay. The tradeoff then is 652 the penalty for Relay-to-Relay tunneling compared with reduced 653 routing information in the native routing system. 655 3.8. AERO Interface Neighbor Cache Maintenace 657 Each AERO interface maintains a conceptual neighbor cache that 658 includes an entry for each neighbor it communicates with on the AERO 659 link, the same as for any IPv6 interface [RFC4861]. AERO interface 660 neighbor cache entires are said to be one of "permanent", "static" or 661 "dynamic". 663 Permanent neighbor cache entries are created through explicit 664 administrative action; they have no timeout values and remain in 665 place until explicitly deleted. AERO Relays maintain a permanent 666 neighbor cache entry for each Server on the link, and AERO Servers 667 maintain a permanent neighbor cache entry for each Relay. Each entry 668 maintains the mapping between the neighbor's fe80::ID network-layer 669 address and corresponding link-layer address. 671 Static neighbor cache entries are created through DHCPv6 PD exchanges 672 and remain in place for durations bounded by prefix lifetimes. AERO 673 Servers maintain static neighbor cache entries for the ACPs of each 674 of their associated Clients, and AERO Clients maintain a static 675 neighbor cache entry for each of their associated Servers. When an 676 AERO Server sends a Reply message response to a Client's Solicit, 677 Rebind or Renew message, it creates or updates a static neighbor 678 cache entry based on the Client's DHCP Unique Identifier (DUID) as 679 the Client identifier, the AERO address(es) corresponding to the 680 Client's ACP(s) as the network-layer address(es), the prefix lifetime 681 as the neighbor cache entry lifetime, the Client's encapsulation IP 682 address and UDP port number as the link-layer address and the prefix 683 length(s) as the length to apply to the AERO address(es). When an 684 AERO Client receives a Reply message from a Server, it creates or 685 updates a static neighbor cache entry based on the Reply message 686 link-local source address as the network-layer address, the prefix 687 lifetime as the neighbor cache entry lifetime, and the encapsulation 688 IP source address and UDP source port number as the link-layer 689 address. 691 Dynamic neighbor cache entries are created or updated based on 692 receipt of a Predirect/Redirect message, and are garbage-collected if 693 not used within a bounded timescale. AERO Clients maintain dynamic 694 neighbor cache entries for each of their active correspondent Client 695 ACPs with lifetimes based on IPv6 ND messaging constants. When an 696 AERO Client receives a valid Predirect message it creates or updates 697 a dynamic neighbor cache entry for the Predirect target network-layer 698 and link-layer addresses plus prefix length. The node then sets an 699 "AcceptTime" variable in the neighbor cache entry to ACCEPT_TIME 700 seconds and uses this value to determine whether packets received 701 from the correspondent can be accepted. When an AERO Client receives 702 a valid Redirect message it creates or updates a dynamic neighbor 703 cache entry for the Redirect target network-layer and link-layer 704 addresses plus prefix length. The Client then sets a "ForwardTime" 705 variable in the neighbor cache entry to FORWARD_TIME seconds and uses 706 this value to determine whether packets can be sent directly to the 707 correspondent. The Client also sets a "MaxRetry" variable to 708 MAX_RETRY to limit the number of keepalives sent when a correspondent 709 may have gone unreachable. 711 It is RECOMMENDED that FORWARD_TIME be set to the default constant 712 value 30 seconds to match the default REACHABLE_TIME value specified 713 for IPv6 ND [RFC4861]. 715 It is RECOMMENDED that ACCEPT_TIME be set to the default constant 716 value 40 seconds to allow a 10 second window so that the AERO 717 redirection procedure can converge before AcceptTime decrements below 718 FORWARD_TIME. 720 It is RECOMMENDED that MAX_RETRY be set to 3 the same as described 721 for IPv6 ND address resolution in Section 7.3.3 of [RFC4861]. 723 Different values for FORWARD_TIME, ACCEPT_TIME, and MAX_RETRY MAY be 724 administratively set, if necessary, to better match the AERO link's 725 performance characteristics; however, if different values are chosen, 726 all nodes on the link MUST consistently configure the same values. 727 Most importantly, ACCEPT_TIME SHOULD be set to a value that is 728 sufficiently longer than FORWARD_TIME to allow the AERO redirection 729 procedure to converge. 731 When there may be a Network Address Translator (NAT) between the 732 Client and the Server, or if the path from the Client to the Server 733 should be tested for reachability, the Client can send periodic RS 734 messages to the Server to receive RA replies. The RS/RA messaging 735 will keep NAT state alive and test Server reachability without 736 disturbing the DHCPv6 server. 738 3.9. AERO Interface Sending Algorithm 740 IP packets enter a node's AERO interface either from the network 741 layer (i.e., from a local application or the IP forwarding system), 742 or from the link layer (i.e., from the AERO tunnel virtual link). 743 Packets that enter the AERO interface from the network layer are 744 encapsulated and admitted into the AERO link, i.e., they are 745 tunnelled to an AERO interface neighbor. Packets that enter the AERO 746 interface from the link layer are either re-admitted into the AERO 747 link or delivered to the network layer where they are subject to 748 either local delivery or IP forwarding. Since each AERO node may 749 have only partial information about neighbors on the link, AERO 750 interfaces may forward packets with link-local destination addresses 751 at a layer below the network layer. This means that AERO nodes act 752 as both IP routers/hosts and sub-IP layer forwarding nodes. AERO 753 interface sending considerations for Clients, Servers and Relays are 754 given below. 756 When an IP packet enters a Client's AERO interface from the network 757 layer, if the destination is covered by an ASP the Client searches 758 for a dynamic neighbor cache entry with a non-zero ForwardTime and an 759 AERO address that matches the packet's destination address. (The 760 destination address may be either an address covered by the 761 neighbor's ACP or the (link-local) AERO address itself.) If there is 762 a match, the Client uses a link-layer address in the entry as the 763 link-layer address for encapsulation then admits the packet into the 764 AERO link. If there is no match, the Client instead uses the link- 765 layer address of a neighboring Server as the link-layer address for 766 encapsulation. 768 When an IP packet enters a Server's AERO interface from the link 769 layer, if the destination is covered by an ASP the Server searches 770 for a neighbor cache entry with an AERO address that matches the 771 packet's destination address. (The destination address may be either 772 an address covered by the neighbor's ACP or the AERO address itself.) 773 If there is a match, the Server uses a link-layer address in the 774 entry as the link-layer address for encapsulation and re-admits the 775 packet into the AERO link. If there is no match, the Server instead 776 uses the link-layer address in a permanent neighbor cache entry for a 777 Relay selected through longest-prefix-match as the link-layer address 778 for encapsulation. 780 When an IP packet enters a Relay's AERO interface from the network 781 layer, the Relay searches its IP forwarding table for an entry that 782 is covered by an ASP and also matches the destination. If there is a 783 match, the Relay uses the link-layer address in the corresponding 784 neighbor cache entry as the link-layer address for encapsulation and 785 admits the packet into the AERO link. When an IP packet enters a 786 Relay's AERO interface from the link-layer, if the destination is not 787 a link-local address and does not match an ASP the Relay removes the 788 packet from the AERO interface and uses IP forwarding to forward the 789 packet to the Internetwork. If the destination address is a link- 790 local address or a non-link-local address that matches an ASP, and 791 there is a more-specific ACP entry in the IP forwarding table, the 792 Relay uses the link-layer address in the corresponding neighbor cache 793 entry as the link-layer address for encapsulation and re-admits the 794 packet into the AERO link. When an IP packet enters a Relay's AERO 795 interface from either the network layer or link-layer, and the 796 packet's destination address matches an ASP but there is no more- 797 specific ACP entry, the Relay drops the packet and returns an ICMP 798 Destination Unreachable message (see: Section 3.14). 800 When an AERO Server receives a packet from a Relay via the AERO 801 interface, the Server MUST NOT forward the packet back to the same or 802 a different Relay. 804 When an AERO Relay receives a packet from a Server via the AERO 805 interface, the Relay MUST NOT forward the packet back to the same 806 Server. 808 When an AERO node re-admits a packet into the AERO link without 809 involving the network layer, the node MUST NOT decrement the network 810 layer TTL/Hop-count. 812 When an AERO node forwards a data packet to the primary link-layer 813 address of a Server, it may receive Redirect messages with an SLLAO 814 that include the link-layer address of an AERO Forwarding Agent. The 815 AERO node SHOULD record the link-layer address in the neighbor cache 816 entry for the neighbor and send subsequent data packets via this 817 address instead of the Server's primary address (see: Section 3.16). 819 3.10. AERO Interface Encapsulation and Re-encapsulation 821 AERO interfaces encapsulate IP packets according to whether they are 822 entering the AERO interface from the network layer or if they are 823 being re-admitted into the same AERO link they arrived on. This 824 latter form of encapsulation is known as "re-encapsulation". 826 The AERO interface encapsulates packets per the Generic UDP 827 Encapsulation (GUE) encapsulation procedures in 828 [I-D.ietf-nvo3-gue][I-D.herbert-gue-fragmentation], or through an 829 alternate encapsulation format (see: Appendix A). For packets 830 entering the AERO link from the IP layer, the AERO interface copies 831 the "TTL/Hop Limit", "Type of Service/Traffic Class" [RFC2983], "Flow 832 Label"[RFC6438].(for IPv6) and "Congestion Experienced" [RFC3168] 833 values in the packet's IP header into the corresponding fields in the 834 encapsulation IP header. For packets undergoing re-encapsulation 835 within the AERO link, the AERO interface instead copies the "TTL/Hop 836 Limit", "Type of Service/Traffic Class", "Flow Label" and "Congestion 837 Experienced" values in the original encapsulation IP header into the 838 corresponding fields in the new encapsulation IP header, i.e., the 839 values are transferred between encapsulation headers and *not* copied 840 from the encapsulated packet's network-layer header. 842 When GUE encapsulation is used, the AERO interface next sets the UDP 843 source port to a constant value that it will use in each successive 844 packet it sends, and sets the UDP length field to the length of the 845 encapsulated packet plus 8 bytes for the UDP header itself plus the 846 length of the GUE header (or 0 if GUE direct IP encapsulation is 847 used). For packets sent to a Server, the AERO interface sets the UDP 848 destination port to 8060, i.e., the IANA-registered port number for 849 AERO. For packets sent to a correspondent Client, the AERO interface 850 sets the UDP destination port to the port value stored in the 851 neighbor cache entry for this correspondent. The AERO interface then 852 either includes or omits the UDP checksum according to the GUE 853 specification. 855 For IPv4 encapsulation, the AERO interface sets the DF bit as 856 discussed in Section 3.13. 858 3.11. AERO Interface Decapsulation 860 AERO interfaces decapsulate packets destined either to the AERO node 861 itself or to a destination reached via an interface other than the 862 AERO interface the packet was received on. Decapsulation is per the 863 procedures specified for the appropriate encapsulation format. 865 3.12. AERO Interface Data Origin Authentication 867 AERO nodes employ simple data origin authentication procedures for 868 encapsulated packets they receive from other nodes on the AERO link. 869 In particular: 871 o AERO Servers and Relays accept encapsulated packets with a link- 872 layer source address that matches a permanent neighbor cache 873 entry. 875 o AERO Servers accept authentic encapsulated DHCPv6 messages from 876 Clients, and create or update a static neighbor cache entry for 877 the Client based on the specific DHCPv6 message type. 879 o AERO Clients and Servers accept encapsulated packets if there is a 880 static neighbor cache entry with a link-layer address that matches 881 the packet's link-layer source address. 883 o AERO Clients, Servers and Relays accept encapsulated packets if 884 there is a dynamic neighbor cache entry with an AERO address that 885 matches the packet's network-layer source address, with a link- 886 layer address that matches the packet's link-layer source address, 887 and with a non-zero AcceptTime. 889 Note that this simple data origin authentication is effective in 890 environments in which link-layer addresses cannot be spoofed. In 891 other environments, each AERO message must include a signature that 892 the recipient can use to authenticate the message origin. 894 3.13. AERO Interface Packet Size Issues 896 The AERO interface is the node's attachment to the AERO link. The 897 AERO interface acts as a tunnel ingress when it sends a packet to an 898 AERO link neighbor and as a tunnel egress when it receives a packet 899 from an AERO link neighbor. AERO interfaces observe the packet 900 sizing considerations for tunnels discussed in 901 [I-D.ietf-intarea-tunnels] and as specified below. 903 IPv6 specifies a minimum link Maximum Transmission Unit (MTU) of 1280 904 bytes [RFC2460]. Although IPv4 specifies a smaller minimum link MTU 905 of 68 bytes [RFC0791], AERO interfaces also observe the IPv6 minimum 906 for IPv4 even if the packet may incur fragmentation in the network. 908 IPv6 specifies a minimum Maximum Reassembly Unit (MRU) of 1500 bytes 909 [RFC2460], while the minimum MRU for IPv4 is only 576 bytes 910 [RFC1122]. Note that IPv6 over IPv4 tunnels assume a larger MRU than 911 the IPv4 minimum. 913 Original sources expect that IP packets will either be delivered to 914 the final destination or a suitable Packet Too Big (PTB) message 915 returned. However, PTB messages may be crafted for malicious 916 purposes such as denial of service, or lost in the network [RFC2923] 917 resulting in failure of the IP Path MTU Discovery (PMTUD) mechanisms 918 [RFC1191][RFC1981]. For these reasons, AERO links employ operational 919 procedures that avoid all interactions with PMTUD. 921 AERO Servers advertise an MTU that MUST be no smaller than 1280 922 bytes, MUST be no larger than the minimum MRU among all nodes on the 923 AERO link minus the encapsulation overhead ("ENCAPS"), and SHOULD be 924 no smaller than 1500 bytes. AERO Servers advertise a Maximum 925 Fragment Unit (MFU) as the maximum size for the fragments of an 926 encapsulated packet that require fragmentation. The MFU value MUST 927 be no larger than 1280 bytes unless there is operational assurance 928 that a larger size can traverse the link along all paths without 929 fragmentation, and MUST be no larger than (MTU+ENCAPS). 931 AERO Clients set the AERO interface MTU/MFU based on the values 932 advertised by their Server, and configure an MRU large enough to 933 reassemble packets up to (MTU+ENCAPS) bytes. 935 All AERO nodes on the link MUST set the same MTU/MFU values for 936 reasons cited in [RFC3819][RFC4861], e.g., to support multicast. 938 In accordnace with these requirements, the ingress accommodates 939 packets of various sizes as follows: 941 o First, for original IPv4 packets that are larger than the AERO 942 interface MTU and with the DF bit set to 0, the ingress uses IPv4 943 fragmentation to break the packet into a minimum number of non- 944 overlapping fragments where the first fragment is no larger than 945 (MFU-ENCAPS) bytes and the remaining fragments are no larger than 946 the first. 948 o Next, for each original IP packet or fragment that is no larger 949 than (MFU-ENCAPS) bytes, the ingress encapsulates the packet and 950 admits it into the tunnel. For IPv4 AERO links, the ingress sets 951 the Don't Fragment (DF) bit to 0 so that these packets will be 952 delivered to the egress even if some fragmentation occurs in the 953 network. 955 o For all other original IP packets or fragments, if the packet is 956 larger than the AERO interface MTU, the ingress drops the packet 957 and returns a PTB message to the original source. Otherwise, the 958 ingress encapsulates the packet and fragments the encapsulated 959 packet into a minimum number of non-overlapping fragments where 960 the first fragment is no larger than MFU bytes and the remaining 961 fragments are no larger than the first. The ingress then admits 962 the fragments into the tunnel, and for IPv4 sets the DF bit to 0 963 in the IP encapsulation header. These fragmented encapsulated 964 packets will be delivered to the egress, which reassembles them 965 into a whole packet. 967 Several factors must be considered when fragmentation of the 968 encapsulated packet is needed. For AERO links over IPv4, the IP ID 969 field is only 16 bits in length, meaning that fragmentation at high 970 data rates could result in data corruption due to reassembly 971 misassociations [RFC6864][RFC4963]. For AERO links over both IPv4 972 and IPv6, studies have also shown that IP fragments are dropped 973 unconditionally over some network paths [I-D.taylor-v6ops-fragdrop]. 974 In environments where IP fragmentation issues could result in 975 operational problems, the ingress SHOULD employ intermediate-layer 976 fragmentation (see: [RFC2764] and [I-D.herbert-gue-fragmentation]) 977 before appending the outer encapsulation headers to each fragment. 979 Since the encapsulation fragment header reduces the room available 980 for packet data, but the original source has no way to control its 981 insertion, the ingress MUST include the fragment header length in the 982 ENCAPS length even for packets in which the header is absent. 984 3.14. AERO Interface Error Handling 986 When an AERO node admits encapsulated packets into the AERO 987 interface, it may receive link-layer (L2) or network-layer (L3) error 988 indications. 990 An L2 error indication is an ICMP error message generated by a router 991 on the path to the neighbor or by the neighbor itself. The message 992 includes an IP header with the address of the node that generated the 993 error as the source address and with the link-layer address of the 994 AERO node as the destination address. 996 The IP header is followed by an ICMP header that includes an error 997 Type, Code and Checksum. Valid type values include "Destination 998 Unreachable", "Time Exceeded" and "Parameter Problem" 999 [RFC0792][RFC4443]. (AERO interfaces ignore all L2 IPv4 1000 "Fragmentation Needed" and IPv6 "Packet Too Big" messages since they 1001 only emit packets that are guaranteed to be no larger than the IP 1002 minimum link MTU.) 1004 The ICMP header is followed by the leading portion of the packet that 1005 generated the error, also known as the "packet-in-error". For 1006 ICMPv6, [RFC4443] specifies that the packet-in-error includes: "As 1007 much of invoking packet as possible without the ICMPv6 packet 1008 exceeding the minimum IPv6 MTU" (i.e., no more than 1280 bytes). For 1009 ICMPv4, [RFC0792] specifies that the packet-in-error includes: 1010 "Internet Header + 64 bits of Original Data Datagram", however 1011 [RFC1812] Section 4.3.2.3 updates this specification by stating: "the 1012 ICMP datagram SHOULD contain as much of the original datagram as 1013 possible without the length of the ICMP datagram exceeding 576 1014 bytes". 1016 The L2 error message format is shown in Figure 3: 1018 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1019 ~ ~ 1020 | L2 IP Header of | 1021 | error message | 1022 ~ ~ 1023 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1024 | L2 ICMP Header | 1025 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ --- 1026 ~ ~ P 1027 | IP and other encapsulation | a 1028 | headers of original L3 packet | c 1029 ~ ~ k 1030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ e 1031 ~ ~ t 1032 | IP header of | 1033 | original L3 packet | i 1034 ~ ~ n 1035 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1036 ~ ~ e 1037 | Upper layer headers and | r 1038 | leading portion of body | r 1039 | of the original L3 packet | o 1040 ~ ~ r 1041 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ --- 1043 Figure 3: AERO Interface L2 Error Message Format 1045 The AERO node rules for processing these L2 error messages is as 1046 follows: 1048 o When an AERO node receives an L2 Parameter Problem message, it 1049 processes the message the same as described as for ordinary ICMP 1050 errors in the normative references [RFC0792][RFC4443]. 1052 o When an AERO node receives persistent L2 IPv4 Time Exceeded 1053 messages, the IP ID field may be wrapping before earlier fragments 1054 have been processed. In that case, the node SHOULD begin 1055 including integrity checks and/or institute rate limits for 1056 subseqent packets. 1058 o When an AERO Client receives persistent L2 Destination Unreachable 1059 messages in response to tunneled packets that it sends to one of 1060 its dynamic neighbor correspondents, the Client SHOULD test the 1061 path to the correspondent using Neighbor Unreachability Detection 1062 (NUD) (see Section 3.18). If NUD fails, the Client SHOULD set 1063 ForwardTime for the corresponding dynamic neighbor cache entry to 1064 0 and allow future packets destined to the correspondent to flow 1065 through a Server. 1067 o When an AERO Client receives persistent L2 Destination Unreachable 1068 messages in response to tunneled packets that it sends to one of 1069 its static neighbor Servers, the Client SHOULD test the path to 1070 the Server using NUD. If NUD fails, the Client SHOULD delete the 1071 neighbor cache entry and attempt to associate with a new Server. 1073 o When an AERO Server receives persistent L2 Destination Unreachable 1074 messages in response to tunneled packets that it sends to one of 1075 its static neighbor Clients, the Server SHOULD test the path to 1076 the Client using NUD. If NUD fails, the Server SHOULD cancel the 1077 DHCPv6 PD for the Client's ACP, withdraw its route for the ACP 1078 from the AERO routing system and delete the neighbor cache entry 1079 (see Section 3.18 and Section 3.19). 1081 o When an AERO Relay or Server receives an L2 Destination 1082 Unreachable message in response to a tunneled packet that it sends 1083 to one of its permanent neighbors, it discards the message since 1084 the AERO routing system is likely in a temporary transitional 1085 state that will soon re-converge. In case of a prolonged outage, 1086 however, the AERO routing system will compensate for Relays or 1087 Servers that have fallen silent. 1089 When an AERO Relay receives an L3 packet for which the destination 1090 address is covered by an ASP, if there is no more-specific routing 1091 information for the destination the Relay drops the packet and 1092 returns an L3 Destination Unreachable message. The Relay first 1093 writes the IP source address of the original L3 packet as the 1094 destination address of the L3 Destination Unreachable message and 1095 determines the next hop to the destination. If the next hop is 1096 reached via the AERO interface, the Relay uses the IPv6 address "::" 1097 or the IPv4 address "0.0.0.0" as the IP source address of the L3 1098 Destination Unreachable message and forwards the message to the next 1099 hop within the AERO interface. Otherwise, the Relay uses one of its 1100 non link-local addresses as the source address of the L3 Destination 1101 Unreachable message and forwards the message via a link outside the 1102 AERO interface. 1104 When an AERO node receives an encapsulated packet for which the 1105 reassembly buffer it too small, it drops the packet and returns an L3 1106 Packet To Big (PTB) message. The node first writes the IP source 1107 address of the original L3 packet as the destination address of the 1108 L3 PTB message and determines the next hop to the destination. If 1109 the next hop is reached via the AERO interface, the node uses the 1110 IPv6 address "::" or the IPv4 address "0.0.0.0" as the IP source 1111 address of the L3 PTB message and forwards the message to the next 1112 hop within the AERO interface. Otherwise, the node uses one of its 1113 non link-local addresses as the source address of the L3 PTB message 1114 and forwards the message via a link outside the AERO interface. 1116 When an AERO node receives any L3 error message via the AERO 1117 interface, it examines the destination address in the L3 IP header of 1118 the message. If the next hop toward the destination address of the 1119 error message is via the AERO interface, the node re-encapsulates and 1120 forwards the message to the next hop within the AERO interface. 1121 Otherwise, if the source address in the L3 IP header of the message 1122 is the IPv6 address "::" or the IPv4 address "0.0.0.0", the node 1123 writes one of its non link-local addresses as the source address of 1124 the L3 message and recalculates the IP and/or ICMP checksums. The 1125 node finally forwards the message via a link outside of the AERO 1126 interface. 1128 3.15. AERO Router Discovery, Prefix Delegation and Address 1129 Configuration 1131 3.15.1. AERO DHCPv6 Service Model 1133 Each AERO Server configures a DHCPv6 server function to facilitate PD 1134 requests from Clients. Each Server is provisioned with a database of 1135 ACP-to-Client ID mappings for all Clients enrolled in the AERO 1136 system, as well as any information necessary to authenticate each 1137 Client. The Client database is maintained by a central 1138 administrative authority for the AERO link and securely distributed 1139 to all Servers, e.g., via the Lightweight Directory Access Protocol 1140 (LDAP) [RFC4511] or a similar distributed database service. 1142 Therefore, no Server-to-Server DHCPv6 PD delegation state 1143 synchronization is necessary, and Clients can optionally hold 1144 separate delegations for the same ACPs from multiple Servers. In 1145 this way, Clients can associate with multiple Servers, and can 1146 receive new delegations from new Servers before deprecating 1147 delegations received from existing Servers. This provides the Client 1148 with a natural fault-tolerance and/or load balancing profile. 1150 AERO Clients and Servers exchange Client link-layer address 1151 information using an option format similar to the Client Link Layer 1152 Address Option (CLLAO) defined in [RFC6939]. Due to practical 1153 limitations of CLLAO, however, AERO interfaces instead use Vendor- 1154 Specific Information Options as described in the following sections. 1156 3.15.2. AERO Client Behavior 1158 AERO Clients discover the link-layer addresses of AERO Servers via 1159 static configuration (e.g., from a flat-file map of Server addresses 1160 and locations), or through an automated means such as DNS name 1161 resolution. In the absence of other information, the Client resolves 1162 the FQDN "linkupnetworks.[domainname]" where "linkupnetworks" is a 1163 constant text string and "[domainname]" is a DNS suffix for the 1164 Client's underlying network (e.g., "example.com"). After discovering 1165 the link-layer addresses, the Client associates with one or more of 1166 the corresponding Servers. 1168 To associate with a Server, the Client acts as a requesting router to 1169 request ACPs through a two-message (i.e., Solicit/Reply) DHCPv6 PD 1170 exchange [RFC3315][RFC3633]. The Client's Solicit message includes 1171 fe80::ffff:ffff:ffff:ffff as the IPv6 source address, 1172 'All_DHCP_Relay_Agents_and_Servers' as the IPv6 destination address 1173 and the link-layer address of the Server as the link-layer 1174 destination address. The Solicit message also includes a Client 1175 Identifier option with a DUID and an Identity Association for Prefix 1176 Delegation (IA_PD) option. If the Client is pre-provisioned with 1177 ACPs associated with the AERO service, it MAY also include the ACPs 1178 in the IA_PD to indicate its preferences to the DHCPv6 server. 1180 The Client also SHOULD include an AERO Link-registration Request 1181 (ALREQ) option in the Solicit message to register one or more links 1182 with the Server. The Server will include an AERO Link-registration 1183 Reply (ALREP) option in the corresponding Reply message as specified 1184 in Section 3.15.3. (The Client MAY omit the ALREQ option, in which 1185 case the Server will still include an ALREP option in its Reply with 1186 "Link ID" set to 0.) 1188 The format for the ALREQ option is shown in Figure 4: 1190 0 1 2 3 1191 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1192 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1193 | OPTION_VENDOR_OPTS | option-len (1) | 1194 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1195 | enterprise-number = 45282 | 1196 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1197 | opt-code = OPTION_ALREQ (0) | option-len (2) | 1198 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1199 | Link ID | DSCP #1 |Prf| DSCP #2 |Prf| ... 1200 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 1202 Figure 4: AERO Link-registration Request (ALREQ) Option 1204 In the above format, the Client sets 'option-code' to 1205 OPTION_VENDOR_OPTS, sets 'option-len (1)' to the length of the option 1206 following this field, sets 'enterprise-number' to 45282 (see: "IANA 1207 Considerations"), sets opt-code to the value 0 ("OPTION_ALREQ") and 1208 sets 'option-len (2)' to the length of the remainder of the option. 1209 The Client includes appropriate 'Link ID, 'DSCP' and 'Prf' values for 1210 the underlying interface over which the Solicit message will be 1211 issued the same as specified for an S/TLLAO Section 3.4. The Server 1212 will register each value with the Link ID in the Client's neighbor 1213 cache entry. The Client finally includes any necessary 1214 authentication options to identify itself to the DHCPv6 server, and 1215 sends the encapsulated Solicit message via the underlying interface 1216 corresponding to Link ID. (Note that this implies that the Client 1217 must send additional Rebind messages with ALREQ options to the server 1218 following the initial PD exchange using different underlying 1219 interfaces and their corresponding Link IDs if it wishes to register 1220 additional link-layer addresses and their associated DSCPs.) 1222 When the Client receives its ACP via a Reply from the AERO Server, it 1223 creates a static neighbor cache entry with the Server's link-local 1224 address as the network-layer address and the Server's encapsulation 1225 address as the link-layer address. The Client then considers the 1226 link-layer address of the Server as the primary default encapsulation 1227 address for forwarding packets for which no more-specific forwarding 1228 information is available. The Client further applies the MTU value 1229 in the ALREP option to its AERO interface, then caches any ASPs 1230 included in the ALREP option as ASPs to apply to the AERO link. 1232 Next, the Client autoconfigures an AERO address for each of the 1233 delegated ACPs, assigns the address(es) to the AERO interface and 1234 sub-delegates the ACPs to its attached EUNs and/or the Client's own 1235 internal virtual interfaces. Alternatively, the Client can configure 1236 as many addresses as it wants from /64 prefixes taken from the ACPs 1237 and assign them to either an internal virtual interface ("weak end- 1238 system") or to the AERO interface itself ("strong end-system") 1239 [RFC1122] while black-holing the remaining portions of the /64s. 1240 Finally, the Client assigns one or more default IP routes to the AERO 1241 interface with the link-local address of a Server as the next hop. 1243 After AERO address autoconfiguration, the Client SHOULD begin using 1244 the AERO address as the source address for further DHCPv6 messaging. 1245 The Client subsequently renews its ACP delegations through each of 1246 its Servers by sending Renew messages with the link-layer address of 1247 a Server as the link-layer destination address and the same options 1248 that were used in the initial PD request. Note that if the Client 1249 does not issue a Renew before the delegations expire (e.g., if the 1250 Client has been out of touch with the Server for a considerable 1251 amount of time) it must re-initiate the DHCPv6 PD procedure. 1253 Since the addresses assigned to the Client's AERO interface are 1254 obtained from the unique ACP delegations it receives, there is no 1255 need for DAD on AERO links. Other nodes maliciously attempting to 1256 hijack addresses from an authorized Client's ACPs will be denied 1257 access to the network by the Server due to an unacceptable link-layer 1258 address and/or security parameters (see: Security Considerations). 1260 When a Client attempts to perform a DHCPv6 PD exchange with a Server 1261 that is too busy to service the request, the Client may receive 1262 either a "NoPrefixAvail" status code in the Server's Reply per 1263 [RFC3633] or no reply at all. In that case, the Client SHOULD 1264 discontinue DHCPv6 PD attempts through this Server and try another 1265 Server. 1267 3.15.2.1. Autoconfiguration for Constrained Platforms 1269 On some platforms (e.g., popular cell phone operating systems), the 1270 act of assigning a default IPv6 route and/or assigning an address to 1271 an interface may not be permitted from a user application due to 1272 security policy. Typically, those platforms include a TUN/TAP 1273 interface [TUNTAP] that acts as a point-to-point conduit between user 1274 applications and the AERO interface. In that case, the Client can 1275 instead generate a "synthesized RA" message. The message conforms to 1276 [RFC4861] and is prepared as follows: 1278 o the IPv6 source address is the Client's AERO address 1280 o the IPv6 destination address is all-nodes multicast 1282 o the Router Lifetime is set to a time that is no longer than the 1283 ACP DHCPv6 lifetime 1285 o the message does not include a Source Link Layer Address Option 1286 (SLLAO) 1288 o the message includes a Prefix Information Option (PIO) with a /64 1289 prefix taken from the ACP as the prefix for autoconfiguration 1291 The Client then sends the synthesized RA message via the TUN/TAP 1292 interface, where the operating system kernel will interpret it as 1293 though it were generated by an actual router. The operating system 1294 will then install a default route and use StateLess Address 1295 AutoConfiguration (SLAAC) to configure an IPv6 address on the TUN/TAP 1296 interface. Methods for similarly installing an IPv4 default route 1297 and IPv4 address on the TUN/TAP interface are based on synthesized 1298 DHCPv4 messages [RFC2131]. 1300 3.15.3. AERO Server Behavior 1302 AERO Servers configure a DHCPv6 server function on their AERO links. 1303 AERO Servers arrange to add their encapsulation layer IP addresses 1304 (i.e., their link-layer addresses) to a static map of Server 1305 addresses for the link and/or the DNS resource records for the FQDN 1306 "linkupnetworks.[domainname]" before entering service. 1308 When an AERO Server receives a prospective Client's Solicit on its 1309 AERO interface, and the Server is too busy to service the message, it 1310 SHOULD return a Reply with status code "NoPrefixAvail" per [RFC3633]. 1311 Otherwise, the Server authenticates the message. If authentication 1312 succeeds, the Server determines the correct ACPs to delegate to the 1313 Client by searching the Client database. 1315 When the Server delegates the ACPs, it also creates IP forwarding 1316 table entries so that the AERO routing system will propagate the ACPs 1317 to all Relays that aggregate the corresponding ASP (see: 1318 Section 3.7). Next, the Server prepares a Reply message to send to 1319 the Client while using fe80::ID as the IPv6 source address, the link- 1320 local address taken from the Client's Solicit as the IPv6 destination 1321 address, the Server's link-layer address as the source link-layer 1322 address, and the Client's link-layer address as the destination link- 1323 layer address. The server also includes IA_PD options with the 1324 delegated ACPs. Since the Client may experience a fault that 1325 prevents it from issuing a Release before departing from the network, 1326 Servers should set a short prefix lifetime (e.g., 40 seconds) so that 1327 stale prefix delegation state can be flushed out of the network. 1329 The Server also includes an ALREP option that includes configuration 1330 information pertaining to the Client's ALREQ. (Note that if the 1331 Client did not include an ALREQ option in its DHCPv6 message, the 1332 Server MUST still include an ALREP option in the corresponding 1333 reply.)The ALREP option is formatted as shown in Figure 5: 1335 0 1 2 3 1336 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1337 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1338 | OPTION_VENDOR_OPTS | option-len (1) | 1339 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1340 | enterprise-number = 45282 | 1341 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1342 | opt-code = OPTION_ALREP (1) | option-len (2) | 1343 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1344 | Link ID | Reserved | UDP Port Number | 1345 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1346 | | 1347 + + 1348 | | 1349 + IP Address + 1350 | | 1351 + + 1352 | | 1353 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1354 |Maximum Transmission Unit (MTU)| Maximum Fragment Unit (MFU) | 1355 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1356 | | 1357 + AERO Service Prefix (ASP) #1 +-+-+-+-+-+-+-+-+ 1358 | | Prefix Len | 1359 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1360 | | 1361 + AERO Service Prefix (ASP) #2 +-+-+-+-+-+-+-+-+ 1362 | | Prefix Len | 1363 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1364 ~ ~ 1365 ~ ~ 1367 Figure 5: AERO Link-registration Reply (ALREP) Option 1369 In the ALREP, the Server sets 'option-code' to OPTION_VENDOR_OPTS, 1370 sets 'option-length (1)' to the length of the option, sets 1371 'enterprise-number' to 45282 (see: "IANA Considerations"), sets opt- 1372 code to OPTION_ALREP (1), and sets 'option-len (2)' to the length of 1373 the remainder of the option. Next, the Server sets 'Link ID' to the 1374 same value that appeared in the ALREQ (or '0' if the Client did not 1375 include an ALREQ), sets Reserved to 0 and sets 'UDP Port Number' and 1376 'IP address' to the link-layer address observed in the Client's 1377 DHCPv6 message. 1379 The Server next sets MTU and MFU according to the considerations 1380 specified in Section 3.13. 1382 The Server finally includes one or more ASP with the IP prefix as it 1383 would appear in the interface identifier portion of the corresponding 1384 AERO address (see: Section 3.3), except that the low-order 8 bits of 1385 the ASP field encode the prefix length instead of the low-order 8 1386 bits of the prefix. The longest prefix that can therefore appear as 1387 an ASP is /56 for IPv6 or /24 for IPv4. 1389 When the Server admits the Reply message into the AERO interface, it 1390 creates a static neighbor cache entry for the Client based on the 1391 DUID and AERO addresses with lifetime set to no more than the 1392 delegation lifetimes and the Client's link-layer address as the link- 1393 layer address for the Link ID specified in the ALREQ. The Server 1394 then uses the Client link-layer address information in the ALREQ 1395 option as the link-layer address for encapsulation based on the 1396 (DSCP, Prf) information. 1398 After the initial DHCPv6 PD exchange, the AERO Server maintains the 1399 neighbor cache entry for the Client until the delegation lifetimes 1400 expire. If the Client issues a Renew, the Server extends the 1401 lifetimes. If the Client issues a Release, or if the Client does not 1402 issue a Renew before the lifetime expires, the Server deletes the 1403 neighbor cache entry for the Client and withdraws the IP routes from 1404 the AERO routing system. 1406 3.15.3.1. Lightweight DHCPv6 Relay Agent (LDRA) 1408 AERO Clients and Servers are always on the same link (i.e., the AERO 1409 link) from the perspective of DHCPv6. However, in some 1410 implementations the DHCPv6 server and AERO interface driver may be 1411 located in separate modules. In that case, the Server's AERO 1412 interface driver module can act as a Lightweight DHCPv6 Relay Agent 1413 (LDRA)[RFC6221] to relay DHCPv6 messages to and from the DHCPv6 1414 server module. 1416 When the LDRA receives a DHCPv6 message from a client, it prepares an 1417 ALREP option the same as described above then wraps the option in a 1418 Relay-Supplied DHCP Option option (RSOO) [RFC6422]. The LDRA then 1419 incorporates the option into the Relay-Forward message and forwards 1420 the message to the DHCPv6 server. 1422 When the DHCPv6 server receives the Relay-Forward message, it caches 1423 the ALREP option and authenticates the encapsulated DHCPv6 message. 1424 The DHCPv6 server subsequently ignores the ALREQ option itself, since 1425 the relay has already included the ALREP option. 1427 When the DHCPv6 server prepares a Reply message, it then includes the 1428 ALREP option in the body of the message along with any other options, 1429 then wraps the message in a Relay-Reply message. The DHCPv6 server 1430 then delivers the Relay-Reply message to the LDRA, which discards the 1431 Relay-Reply wrapper and delivers the DHCPv6 message to the Client. 1433 3.15.4. Deleting Link Registrations 1435 After an AERO Client registers its Link IDs and their associated 1436 (DSCP,Prf) values with the AERO Server, the Client may wish to delete 1437 one or more Link registrations, e.g., if an underlying link becomes 1438 unavailable. To do so, the Client prepares a Rebind message that 1439 includes an AERO Link-registration Delete (ALDEL) option and sends 1440 the Rebind message to the Server over any available underlying link. 1441 The ALDEL option is formatted as shown in Figure 6: 1443 0 1 2 3 1444 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1445 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1446 | OPTION_VENDOR_OPTS | option-len (1) | 1447 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1448 | enterprise-number = 45282 | 1449 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1450 | opt-code = OPTION_ALDEL (2) | option-len (2) | 1451 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1452 | Link ID #1 | Link ID #2 | Link ID #3 | ... 1453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 1455 Figure 6: AERO Link-registration Delete (ALDEL) Option 1457 In the ALDEL, the Client sets 'option-code' to OPTION_VENDOR_OPTS, 1458 sets 'option-length (1)' to the length of the option, sets 1459 'enterprise-number' to 45282 (see: "IANA Considerations"), sets 1460 optcode to OPTION_ALDEL (2), and sets 'option-len (2)' to the length 1461 of the remainder of the option. Next, the Server includes each 'Link 1462 ID' value that it wishes to delete. 1464 If the Client wishes to discontinue use of a Server and thereby 1465 delete all of its Link ID associations, it must issue a Release to 1466 delete the entire neighbor cache entry, i.e., instead of issuing a 1467 Rebind with one or more ALDEL options. 1469 3.16. AERO Forwarding Agent Behavior 1471 AERO Servers MAY associate with one or more companion AERO Forwarding 1472 Agents as platforms for offloading high-speed data plane traffic. 1473 When an AERO Server receives a Client's Solicit/Renew/Rebind/Release 1474 message, it services the message then forwards the corresponding 1475 Reply message to the Forwarding Agent. When the Forwarding Agent 1476 receives the Reply message, it creates, updates or deletes a neighbor 1477 cache entry with the Client's AERO address and link-layer information 1478 included in the Reply message. The Forwarding Agent then forwards 1479 the Reply message back to the AERO Server, which forwards the message 1480 to the Client. In this way, Forwarding Agent state is managed in 1481 conjunction with Server state, with the Client responsible for 1482 reliability. 1484 When an AERO Server receives a data packet on an AERO interface with 1485 a network layer destination address for which it has distributed 1486 forwarding information to a Forwarding Agent, the Server returns a 1487 Redirect message to the source neighbor (subject to rate limiting) 1488 then forwards the data packet as usual. The Redirect message 1489 includes a TLLAO with the link-layer address of the Forwarding 1490 Engine. 1492 When the source neighbor receives the Redirect message, it SHOULD 1493 record the link-layer address in the TLLAO as the encapsulation 1494 addresses to use for sending subsequent data packets. However, the 1495 source MUST continue to use the primary link-layer address of the 1496 Server as the encapsulation address for sending control messages. 1498 3.17. AERO Intradomain Route Optimization 1500 When a source Client forwards packets to a prospective correspondent 1501 Client within the same AERO link domain (i.e., one for which the 1502 packet's destination address is covered by an ASP), the source Client 1503 MAY initiate an intra-domain AERO route optimization procedure. It 1504 is important to note that this procedure is initiated by the Client; 1505 if the procedure were initiated by the Server, the Server would have 1506 no way of knowing whether the Client was actually able to contact the 1507 correspondent over the route-optimized path. 1509 The procedure is based on an exchange of IPv6 ND messages using a 1510 chain of AERO Servers and Relays as a trust basis. This procedure is 1511 in contrast to the Return Routability procedure required for route 1512 optimization to a correspondent Client located in the Internet as 1513 described in Section 3.22. The following sections specify the AERO 1514 intradomain route optimization procedure. 1516 3.17.1. Reference Operational Scenario 1518 Figure 7 depicts the AERO intradomain route optimization reference 1519 operational scenario, using IPv6 addressing as the example (while not 1520 shown, a corresponding example for IPv4 addressing can be easily 1521 constructed). The figure shows an AERO Relay ('R1'), two AERO 1522 Servers ('S1', 'S2'), two AERO Clients ('C1', 'C2') and two ordinary 1523 IPv6 hosts ('H1', 'H2'): 1525 +--------------+ +--------------+ +--------------+ 1526 | Server S1 | | Relay R1 | | Server S2 | 1527 +--------------+ +--------------+ +--------------+ 1528 fe80::2 fe80::1 fe80::3 1529 L2(S1) L2(R1) L2(S2) 1530 | | | 1531 X-----+-----+------------------+-----------------+----+----X 1532 | AERO Link | 1533 L2(A) L2(B) 1534 fe80::2001:db8:0:0 fe80::2001:db8:1:0 1535 +--------------+ +--------------+ 1536 |AERO Client C1| |AERO Client C2| 1537 +--------------+ +--------------+ 1538 2001:DB8:0::/48 2001:DB8:1::/48 1539 | | 1540 .-. .-. 1541 ,-( _)-. 2001:db8:0::1 2001:db8:1::1 ,-( _)-. 1542 .-(_ IP )-. +---------+ +---------+ .-(_ IP )-. 1543 (__ EUN )--| Host H1 | | Host H2 |--(__ EUN ) 1544 `-(______)-' +---------+ +---------+ `-(______)-' 1546 Figure 7: AERO Reference Operational Scenario 1548 In Figure 7, Relay ('R1') assigns the address fe80::1 to its AERO 1549 interface with link-layer address L2(R1), Server ('S1') assigns the 1550 address fe80::2 with link-layer address L2(S1),and Server ('S2') 1551 assigns the address fe80::3 with link-layer address L2(S2). Servers 1552 ('S1') and ('S2') next arrange to add their link-layer addresses to a 1553 published list of valid Servers for the AERO link. 1555 AERO Client ('C1') receives the ACP 2001:db8:0::/48 in a DHCPv6 PD 1556 exchange via AERO Server ('S1') then assigns the address 1557 fe80::2001:db8:0:0 to its AERO interface with link-layer address 1558 L2(C1). Client ('C1') configures a default route and neighbor cache 1559 entry via the AERO interface with next-hop address fe80::2 and link- 1560 layer address L2(S1), then sub-delegates the ACP to its attached 1561 EUNs. IPv6 host ('H1') connects to the EUN, and configures the 1562 address 2001:db8:0::1. 1564 AERO Client ('C2') receives the ACP 2001:db8:1::/48 in a DHCPv6 PD 1565 exchange via AERO Server ('S2') then assigns the address 1566 fe80::2001:db8:1:0 to its AERO interface with link-layer address 1567 L2(C2). Client ('C2') configures a default route and neighbor cache 1568 entry via the AERO interface with next-hop address fe80::3 and link- 1569 layer address L2(S2), then sub-delegates the ACP to its attached 1570 EUNs. IPv6 host ('H2') connects to the EUN, and configures the 1571 address 2001:db8:1::1. 1573 3.17.2. Concept of Operations 1575 Again, with reference to Figure 7, when source host ('H1') sends a 1576 packet to destination host ('H2'), the packet is first forwarded over 1577 the source host's attached EUN to Client ('C1'). Client ('C1') then 1578 forwards the packet via its AERO interface to Server ('S1') and also 1579 sends a Predirect message toward Client ('C2') via Server ('S1'). 1580 Server ('S1') then re-encapsulates and forwards both the packet and 1581 the Predirect message out the same AERO interface toward Client 1582 ('C2') via Relay ('R1'). 1584 When Relay ('R1') receives the packet and Predirect message, it 1585 consults its forwarding table to discover Server ('S2') as the next 1586 hop toward Client ('C2'). Relay ('R1') then forwards both the packet 1587 and the Predirect message to Server ('S2'), which then forwards them 1588 to Client ('C2'). 1590 After Client ('C2') receives the Predirect message, it process the 1591 message and returns a Redirect message toward Client ('C1') via 1592 Server ('S2'). During the process, Client ('C2') also creates or 1593 updates a dynamic neighbor cache entry for Client ('C1'). 1595 When Server ('S2') receives the Redirect message, it re-encapsulates 1596 the message and forwards it on to Relay ('R1'), which forwards the 1597 message on to Server ('S1') which forwards the message on to Client 1598 ('C1'). After Client ('C1') receives the Redirect message, it 1599 processes the message and creates or updates a dynamic neighbor cache 1600 entry for Client ('C2'). 1602 Following the above Predirect/Redirect message exchange, forwarding 1603 of packets from Client ('C1') to Client ('C2') without involving any 1604 intermediate nodes is enabled. The mechanisms that support this 1605 exchange are specified in the following sections. 1607 3.17.3. Message Format 1609 AERO Redirect/Predirect messages use the same format as for IPv6 ND 1610 Redirect messages depicted in Section 4.5 of [RFC4861], but also 1611 include a new "Prefix Length" field taken from the low-order 8 bits 1612 of the Redirect message Reserved field. For IPv6, valid values for 1613 the Prefix Length field are 0 through 64; for IPv4, valid values are 1614 0 through 32. The Redirect/Predirect messages are formatted as shown 1615 in Figure 8: 1617 0 1 2 3 1618 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1619 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1620 | Type (=137) | Code (=0/1) | Checksum | 1621 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1622 | Reserved | Prefix Length | 1623 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1624 | | 1625 + + 1626 | | 1627 + Target Address + 1628 | | 1629 + + 1630 | | 1631 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1632 | | 1633 + + 1634 | | 1635 + Destination Address + 1636 | | 1637 + + 1638 | | 1639 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1640 | Options ... 1641 +-+-+-+-+-+-+-+-+-+-+-+- 1643 Figure 8: AERO Redirect/Predirect Message Format 1645 3.17.4. Sending Predirects 1647 When a Client forwards a packet with a source address from one of its 1648 ACPs toward a destination address covered by an ASP (i.e., toward 1649 another AERO Client connected to the same AERO link), the source 1650 Client MAY send a Predirect message forward toward the destination 1651 Client via the Server. 1653 In the reference operational scenario, when Client ('C1') forwards a 1654 packet toward Client ('C2'), it MAY also send a Predirect message 1655 forward toward Client ('C2'), subject to rate limiting (see 1656 Section 8.2 of [RFC4861]). Client ('C1') prepares the Predirect 1657 message as follows: 1659 o the link-layer source address is set to 'L2(C1)' (i.e., the link- 1660 layer address of Client ('C1')). 1662 o the link-layer destination address is set to 'L2(S1)' (i.e., the 1663 link-layer address of Server ('S1')). 1665 o the network-layer source address is set to fe80::2001:db8:0:0 1666 (i.e., the AERO address of Client ('C1')). 1668 o the network-layer destination address is set to fe80::2001:db8:1:0 1669 (i.e., the AERO address of Client ('C2')). 1671 o the Type is set to 137. 1673 o the Code is set to 1 to indicate "Predirect". 1675 o the Prefix Length is set to the length of the prefix to be 1676 assigned to the Target Address. 1678 o the Target Address is set to fe80::2001:db8:0:0 (i.e., the AERO 1679 address of Client ('C1')). 1681 o the Destination Address is set to the source address of the 1682 originating packet that triggered the Predirection event. (If the 1683 originating packet is an IPv4 packet, the address is constructed 1684 in IPv4-compatible IPv6 address format). 1686 o the message includes one or more TLLAOs with Link ID and DSCPs set 1687 to appropriate values for Client ('C1')'s underlying interfaces, 1688 and with UDP Port Number and IP Address set to 0'. 1690 o the message SHOULD include a Timestamp option and a Nonce option. 1692 o the message includes a Redirected Header Option (RHO) that 1693 contains the originating packet truncated if necessary to ensure 1694 that at least the network-layer header is included but the size of 1695 the message does not exceed 1280 bytes. 1697 Note that the act of sending Predirect messages is cited as "MAY", 1698 since Client ('C1') may have advanced knowledge that the direct path 1699 to Client ('C2') would be unusable or otherwise undesirable. If the 1700 direct path later becomes unusable after the initial route 1701 optimization, Client ('C1') simply allows packets to again flow 1702 through Server ('S1'). 1704 3.17.5. Re-encapsulating and Relaying Predirects 1706 When Server ('S1') receives a Predirect message from Client ('C1'), 1707 it first verifies that the TLLAOs in the Predirect are a proper 1708 subset of the Link IDs in Client ('C1')'s neighbor cache entry. If 1709 the Client's TLLAOs are not acceptable, Server ('S1') discards the 1710 message. Otherwise, Server ('S1') validates the message according to 1711 the Redirect message validation rules in Section 8.1 of [RFC4861], 1712 except that the Predirect has Code=1. Server ('S1') also verifies 1713 that Client ('C1') is authorized to use the Prefix Length in the 1714 Predirect when applied to the AERO address in the network-layer 1715 source address by searching for the AERO address in the neighbor 1716 cache. If validation fails, Server ('S1') discards the Predirect; 1717 otherwise, it copies the correct UDP Port numbers and IP Addresses 1718 for Client ('C1')'s links into the (previously empty) TLLAOs. 1720 Server ('S1') then examines the network-layer destination address of 1721 the Predirect to determine the next hop toward Client ('C2') by 1722 searching for the AERO address in the neighbor cache. Since Client 1723 ('C2') is not one of its neighbors, Server ('S1') re-encapsulates the 1724 Predirect and relays it via Relay ('R1') by changing the link-layer 1725 source address of the message to 'L2(S1)' and changing the link-layer 1726 destination address to 'L2(R1)'. Server ('S1') finally forwards the 1727 re-encapsulated message to Relay ('R1') without decrementing the 1728 network-layer TTL/Hop Limit field. 1730 When Relay ('R1') receives the Predirect message from Server ('S1') 1731 it determines that Server ('S2') is the next hop toward Client ('C2') 1732 by consulting its forwarding table. Relay ('R1') then re- 1733 encapsulates the Predirect while changing the link-layer source 1734 address to 'L2(R1)' and changing the link-layer destination address 1735 to 'L2(S2)'. Relay ('R1') then relays the Predirect via Server 1736 ('S2'). 1738 When Server ('S2') receives the Predirect message from Relay ('R1') 1739 it determines that Client ('C2') is a neighbor by consulting its 1740 neighbor cache. Server ('S2') then re-encapsulates the Predirect 1741 while changing the link-layer source address to 'L2(S2)' and changing 1742 the link-layer destination address to 'L2(C2)'. Server ('S2') then 1743 forwards the message to Client ('C2'). 1745 3.17.6. Processing Predirects and Sending Redirects 1747 When Client ('C2') receives the Predirect message, it accepts the 1748 Predirect only if the message has a link-layer source address of one 1749 of its Servers (e.g., L2(S2)). Client ('C2') further accepts the 1750 message only if it is willing to serve as a redirection target. 1751 Next, Client ('C2') validates the message according to the Redirect 1752 message validation rules in Section 8.1 of [RFC4861], except that it 1753 accepts the message even though Code=1 and even though the network- 1754 layer source address is not that of it's current first-hop router. 1756 In the reference operational scenario, when Client ('C2') receives a 1757 valid Predirect message, it either creates or updates a dynamic 1758 neighbor cache entry that stores the Target Address of the message as 1759 the network-layer address of Client ('C1') , stores the link-layer 1760 addresses found in the TLLAOs as the link-layer addresses of Client 1761 ('C1') and stores the Prefix Length as the length to be applied to 1762 the network-layer address for forwarding purposes. Client ('C2') 1763 then sets AcceptTime for the neighbor cache entry to ACCEPT_TIME. 1765 After processing the message, Client ('C2') prepares a Redirect 1766 message response as follows: 1768 o the link-layer source address is set to 'L2(C2)' (i.e., the link- 1769 layer address of Client ('C2')). 1771 o the link-layer destination address is set to 'L2(S2)' (i.e., the 1772 link-layer address of Server ('S2')). 1774 o the network-layer source address is set to fe80::2001:db8:1:0 1775 (i.e., the AERO address of Client ('C2')). 1777 o the network-layer destination address is set to fe80::2001:db8:0:0 1778 (i.e., the AERO address of Client ('C1')). 1780 o the Type is set to 137. 1782 o the Code is set to 0 to indicate "Redirect". 1784 o the Prefix Length is set to the length of the prefix to be applied 1785 to the Target Address. 1787 o the Target Address is set to fe80::2001:db8:1:0 (i.e., the AERO 1788 address of Client ('C2')). 1790 o the Destination Address is set to the destination address of the 1791 originating packet that triggered the Redirection event. (If the 1792 originating packet is an IPv4 packet, the address is constructed 1793 in IPv4-compatible IPv6 address format). 1795 o the message includes one or more TLLAOs with Link ID and DSCPs set 1796 to appropriate values for Client ('C2')'s underlying interfaces, 1797 and with UDP Port Number and IP Address set to '0'. 1799 o the message SHOULD include a Timestamp option and MUST echo the 1800 Nonce option received in the Predirect (i.e., if a Nonce option is 1801 included). 1803 o the message includes as much of the RHO copied from the 1804 corresponding Predirect message as possible such that at least the 1805 network-layer header is included but the size of the message does 1806 not exceed 1280 bytes. 1808 After Client ('C2') prepares the Redirect message, it sends the 1809 message to Server ('S2'). 1811 3.17.7. Re-encapsulating and Relaying Redirects 1813 When Server ('S2') receives a Redirect message from Client ('C2'), it 1814 first verifies that the TLLAOs in the Redirect are a proper subset of 1815 the Link IDs in Client ('C2')'s neighbor cache entry. If the 1816 Client's TLLAOs are not acceptable, Server ('S2') discards the 1817 message. Otherwise, Server ('S2') validates the message according to 1818 the Redirect message validation rules in Section 8.1 of [RFC4861]. 1819 Server ('S2') also verifies that Client ('C2') is authorized to use 1820 the Prefix Length in the Redirect when applied to the AERO address in 1821 the network-layer source address by searching for the AERO address in 1822 the neighbor cache. If validation fails, Server ('S2') discards the 1823 Redirect; otherwise, it copies the correct UDP Port numbers and IP 1824 Addresses for Client ('C2')'s links into the (previously empty) 1825 TLLAOs. 1827 Server ('S2') then examines the network-layer destination address of 1828 the Redirect to determine the next hop toward Client ('C1') by 1829 searching for the AERO address in the neighbor cache. Since Client 1830 ('C1') is not a neighbor, Server ('S2') re-encapsulates the Redirect 1831 and relays it via Relay ('R1') by changing the link-layer source 1832 address of the message to 'L2(S2)' and changing the link-layer 1833 destination address to 'L2(R1)'. Server ('S2') finally forwards the 1834 re-encapsulated message to Relay ('R1') without decrementing the 1835 network-layer TTL/Hop Limit field. 1837 When Relay ('R1') receives the Redirect message from Server ('S2') it 1838 determines that Server ('S1') is the next hop toward Client ('C1') by 1839 consulting its forwarding table. Relay ('R1') then re-encapsulates 1840 the Redirect while changing the link-layer source address to 'L2(R1)' 1841 and changing the link-layer destination address to 'L2(S1)'. Relay 1842 ('R1') then relays the Redirect via Server ('S1'). 1844 When Server ('S1') receives the Redirect message from Relay ('R1') it 1845 determines that Client ('C1') is a neighbor by consulting its 1846 neighbor cache. Server ('S1') then re-encapsulates the Redirect 1847 while changing the link-layer source address to 'L2(S1)' and changing 1848 the link-layer destination address to 'L2(C1)'. Server ('S1') then 1849 forwards the message to Client ('C1'). 1851 3.17.8. Processing Redirects 1853 When Client ('C1') receives the Redirect message, it accepts the 1854 message only if it has a link-layer source address of one of its 1855 Servers (e.g., ''L2(S1)'). Next, Client ('C1') validates the message 1856 according to the Redirect message validation rules in Section 8.1 of 1857 [RFC4861], except that it accepts the message even though the 1858 network-layer source address is not that of it's current first-hop 1859 router. Following validation, Client ('C1') then processes the 1860 message as follows. 1862 In the reference operational scenario, when Client ('C1') receives 1863 the Redirect message, it either creates or updates a dynamic neighbor 1864 cache entry that stores the Target Address of the message as the 1865 network-layer address of Client ('C2'), stores the link-layer 1866 addresses found in the TLLAOs as the link-layer addresses of Client 1867 ('C2') and stores the Prefix Length as the length to be applied to 1868 the network-layer address for forwarding purposes. Client ('C1') 1869 then sets ForwardTime for the neighbor cache entry to FORWARD_TIME. 1871 Now, Client ('C1') has a neighbor cache entry with a valid 1872 ForwardTime value, while Client ('C2') has a neighbor cache entry 1873 with a valid AcceptTime value. Thereafter, Client ('C1') may forward 1874 ordinary network-layer data packets directly to Client ('C2') without 1875 involving any intermediate nodes, and Client ('C2') can verify that 1876 the packets came from an acceptable source. (In order for Client 1877 ('C2') to forward packets to Client ('C1'), a corresponding 1878 Predirect/Redirect message exchange is required in the reverse 1879 direction; hence, the mechanism is asymmetric.) 1881 3.17.9. Server-Oriented Redirection 1883 In some environments, the Server nearest the target Client may need 1884 to serve as the redirection target, e.g., if direct Client-to-Client 1885 communications are not possible. In that case, the Server prepares 1886 the Redirect message the same as if it were the destination Client 1887 (see: Section 3.17.6), except that it writes its own link-layer 1888 address in the TLLAO option. The Server must then maintain a dynamic 1889 neighbor cache entry for the redirected source Client. 1891 3.17.10. Route Optimization Policy 1893 Although the Client is responsible for initiating route optimization 1894 through the transmission of Predirect messages, the Server is the 1895 policy enforcement point that determines whether route optimization 1896 is permitted. For example, on some AERO links route optimization 1897 would allow traffic to circumvent critical network-based traffic 1898 interception points. In those cases, the Server can deny route 1899 optimization requests by simply discarding any Predirect messages 1900 instead of forwarding them. 1902 3.17.11. Route Optimization and Multiple ACPs 1904 Clients that receive multiple non-contiguous ACP delegations must 1905 perform route optimization for each of the individual ACPs based on 1906 demand of traffic with source addresses taken from those prefixes. 1907 For example, if Client C1 has already performed route optimization 1908 for destination ACP X on behalf of its source ACP Y, it must also 1909 perform route optimization for X on behalf of its source ACP Z. As a 1910 result, source route optimization state cannot be shared between non- 1911 contiguous ACPs and must be managed separately. 1913 3.18. Neighbor Unreachability Detection (NUD) 1915 AERO nodes perform Neighbor Unreachability Detection (NUD) by sending 1916 unicast NS messages to elicit solicited NA messages from neighbors 1917 the same as described in [RFC4861]. NUD is performed either 1918 reactively in response to persistent L2 errors (see Section 3.14) or 1919 proactively to test existing neighbor cache entries. 1921 When an AERO node sends an NS/NA message, it MUST use its link-local 1922 address as the IPv6 source address and the link-local address of the 1923 neighbor as the IPv6 destination address. When an AERO node receives 1924 an NS message or a solicited NA message, it accepts the message if it 1925 has a neighbor cache entry for the neighbor; otherwise, it ignores 1926 the message. 1928 When a source Client is redirected to a target Client it SHOULD 1929 proactively test the direct path by sending an initial NS message to 1930 elicit a solicited NA response. While testing the path, the source 1931 Client can optionally continue sending packets via the Server, 1932 maintain a small queue of packets until target reachability is 1933 confirmed, or (optimistically) allow packets to flow directly to the 1934 target. The source Client SHOULD thereafter continue to test the 1935 direct path to the target Client (see Section 7.3 of [RFC4861]) 1936 periodically in order to keep dynamic neighbor cache entries alive. 1938 In particular, while the source Client is actively sending packets to 1939 the target Client it SHOULD also send NS messages separated by 1940 RETRANS_TIMER milliseconds in order to receive solicited NA messages. 1941 If the source Client is unable to elicit a solicited NA response from 1942 the target Client after MAX_RETRY attempts, it SHOULD set ForwardTime 1943 to 0 and resume sending packets via one of its Servers. Otherwise, 1944 the source Client considers the path usable and SHOULD thereafter 1945 process any link-layer errors as a hint that the direct path to the 1946 target Client has either failed or has become intermittent. 1948 When ForwardTime for a dynamic neighbor cache entry expires, the 1949 source Client resumes sending any subsequent packets via a Server and 1950 may (eventually) attempt to re-initiate the AERO redirection process. 1951 When AcceptTime for a dynamic neighbor cache entry expires, the 1952 target Client discards any subsequent packets received directly from 1953 the source Client. When both ForwardTime and AcceptTime for a 1954 dynamic neighbor cache entry expire, the Client deletes the neighbor 1955 cache entry. 1957 3.19. Mobility Management 1959 3.19.1. Announcing Link-Layer Address Changes 1961 When a Client needs to change its link-layer address, e.g., due to a 1962 mobility event, it issues an immediate Rebind to each of its Servers 1963 using the new link-layer address as the source address and with an 1964 ALREQ that includes the correct Link ID and DSCP values. If 1965 authentication succeeds, the Server then updates its neighbor cache 1966 and sends a Reply. Note that if the Client does not issue a Rebind 1967 before the prefix delegation lifetime expires (e.g., if the Client 1968 has been out of touch with the Server for a considerable amount of 1969 time), the Server's Reply will report NoBinding and the Client must 1970 re-initiate the DHCPv6 PD procedure. 1972 Next, the Client sends Predirect messages to each of its 1973 correspondent Client neighbors using the same procedures as specified 1974 in Section 3.17.4. The Client sends the Predirect messages via a 1975 Server the same as if it was performing the initial route 1976 optimization procedure with the correspondent. The Predirect message 1977 will update the correspondent' link layer address mapping for the 1978 Client. 1980 3.19.2. Bringing New Links Into Service 1982 When a Client needs to bring a new underlying interface into service 1983 (e.g., when it activates a new data link), it issues an immediate 1984 Rebind to each of its Servers using the new link-layer address as the 1985 source address and with an ALREQ that includes the new Link ID and 1986 DSCP values. If authentication succeeds, the Server then updates its 1987 neighbor cache and sends a Reply. The Client MAY then send Predirect 1988 messages to each of its correspondent Clients to inform them of the 1989 new link-layer address as described in Section 3.19.1. 1991 3.19.3. Removing Existing Links from Service 1993 When a Client needs to remove an existing underlying interface from 1994 service (e.g., when it de-activates an existing data link), it issues 1995 an immediate Rebind to each of its Servers over any available link 1996 with an ALDEL that includes the deprecated Link ID. If 1997 authentication succeeds, the Server then updates its neighbor cache 1998 and sends a Reply. The Client SHOULD then send Predirect messages to 1999 each of its correspondent Clients to inform them of the deprecated 2000 link-layer address as described in Section 3.19.1. 2002 3.19.4. Moving to a New Server 2004 When a Client associates with a new Server, it performs the Client 2005 procedures specified in Section 3.15.2. 2007 When a Client disassociates with an existing Server, it sends a 2008 Release message via a new Server to the unicast link-local network 2009 layer address of the old Server. The new Server then writes its own 2010 link-layer address in the Release message IP source address and 2011 forwards the message to the old Server. 2013 When the old Server receives the Release, it first authenticates the 2014 message. Next, it resets the Client's neighbor cache entry lifetime 2015 to 3 seconds, rewrites the link-layer address in the neighbor cache 2016 entry to the address of the new Server, then returns a Reply message 2017 to the Client via the old Server. When the lifetime expires, the old 2018 Server withdraws the IP route from the AERO routing system and 2019 deletes the neighbor cache entry for the Client. The Client can then 2020 use the Reply message to verify that the termination signal has been 2021 processed, and can delete both the default route and the neighbor 2022 cache entry for the old Server. (Note that since Release/Reply 2023 messages may be lost in the network the Client MUST retry until it 2024 gets a Reply indicating that the Release was successful. If the 2025 Client does not receive a Reply after MAX_RETRY attempts, the old 2026 Server may have failed and the Client should discontinue its Release 2027 attempts.) 2029 Clients SHOULD NOT move rapidly between Servers in order to avoid 2030 causing excessive oscillations in the AERO routing system. Such 2031 oscillations could result in intermittent reachability for the Client 2032 itself, while causing little harm to the network. Examples of when a 2033 Client might wish to change to a different Server include a Server 2034 that has gone unreachable, topological movements of significant 2035 distance, etc. 2037 3.19.5. Packet Queueing for Mobility 2039 AERO Clients and Servers should maintain a samll queue of packets 2040 they have recently sent to an AERO neighbor, e.g., a 1 second window. 2041 If the AERO neighbor moves, the AERO node MAY retransmit the queued 2042 packets to ensure that they are delviered to the AERO neighbor's new 2043 location. 2045 Note that this may have performance implications for asymmetric 2046 paths. For example, if the AERO neighbor moves from a 50mbps link to 2047 a 128kbps link, retransmitting a 1 second window could lead to 2048 significant congestion. 2050 3.20. Proxy AERO 2052 Proxy Mobile IPv6 (PMIPv6) [RFC5213][RFC5844][RFC5949] presents a 2053 network-based localized mobility management scheme for use within an 2054 access network domain. It is typically used in WiFi and cellular 2055 wireless access networks, and allows Mobile Nodes (MNs) to receive 2056 and retain an IP address that remains stable within the access 2057 network domain without needing to implement any special mobility 2058 protocols. In the PMIPv6 architecture, access network devices known 2059 as Mobility Access Gateways (MAGs) provide MNs with an access link 2060 abstraction and receive prefixes for the MNs from a Local Mobility 2061 Anchor (LMA). 2063 In a proxy AERO domain, a proxy AERO Client (acting as a MAG) can 2064 similarly provide proxy services for MNs that do not participate in 2065 AERO messaging. The proxy Client presents an access link abstraction 2066 to MNs, and performs DHCPv6 PD exchanges over the AERO interface with 2067 an AERO Server (acting as an LMA) to receive ACPs for address 2068 provisioning of new MNs that come onto an access link. This scheme 2069 assumes that proxy Clients act as fixed (non-mobile) infrastructure 2070 elements under the same administrative trust basis as for Relays and 2071 Servers. 2073 When an MN comes onto an access link within a proxy AERO domain for 2074 the first time, the proxy Client authenticates the MN and obtains a 2075 unique identifier that it can use as a DHCPv6 DUID then sends a 2076 Solicit message to its Server. When the Server delegates an ACP and 2077 returns a Reply, the proxy Client creates an AERO address for the MN 2078 and assigns the ACP to the MN's access link. The proxy Client then 2079 configures itself as a default router for the MN and provides address 2080 autoconfiguration services (e.g., SLAAC, DHCPv6, DHCPv4, etc.) for 2081 provisioning MN addresses from the ACP over the access link. Since 2082 the proxy Client may serve many such MNs simultaneously, it may 2083 receive multiple ACP prefix delegations and configure multiple AERO 2084 addresses, i.e., one for each MN. 2086 When two MNs are associated with the same proxy Client, the Client 2087 can forward traffic between the MNs without involving a Server since 2088 it configures the AERO addresses of both MNs and therefore also has 2089 the necessary routing information. When two MNs are associated with 2090 different proxy Clients, the source MN's Client can initiate standard 2091 AERO intradomain route optimization to discover a direct path to the 2092 target MN's Client through the exchange of Predirect/Redirect 2093 messages. 2095 When an MN in a proxy AERO domain leaves an access link provided by 2096 an old proxy Client, the MN issues an access link-specific "leave" 2097 message that informs the old Client of the link-layer address of a 2098 new Client on the planned new access link. This is known as a 2099 "predictive handover". When an MN comes onto an access link provided 2100 by a new proxy Client, the MN issues an access link-specific "join" 2101 message that informs the new Client of the link-layer address of the 2102 old Client on the actual old access link. This is known as a 2103 "reactive handover". 2105 Upon receiving a predictive handover indication, the old proxy Client 2106 sends a Solicit message directly to the new Client and queues any 2107 arriving data packets addressed to the departed MN. The Solicit 2108 message includes the MN's ID as the DUID, the ACP in an IA_PD option, 2109 the old Client's address as the link-layer source address and the new 2110 Client's address as the link-layer destination address. When the new 2111 Client receives the Solicit message, it changes the link-layer source 2112 address to its own address, changes the link-layer destination 2113 address to the address of its Server, and forwards the message to the 2114 Server. At the same time, the new Client creates access link state 2115 for the ACP in anticipation of the MN's arrival (while queuing any 2116 data packets until the MN arrives), creates a neighbor cache entry 2117 for the old Client with AcceptTime set to ACCEPT_TIME, then sends a 2118 Redirect message back to the old Client. When the old Client 2119 receives the Redirect message, it creates a neighbor cache entry for 2120 the new Client with ForwardTime set to FORWARD_TIME, then forwards 2121 any queued data packets to the new Client. At the same time, the old 2122 Client sends a Release message to its Server. Finally, the old 2123 Client sends unsolicited Redirect messages to any of the ACP's 2124 correspondents with a TLLAO containing the link-layer address of the 2125 new Client. 2127 Upon receiving a reactive handover indication, the new proxy Client 2128 creates access link state for the MN's ACP, sends a Solicit message 2129 to its Server, and sends a Release message directly to the old 2130 Client. The Release message includes the MN's ID as the DUID, the 2131 ACP in an IA_PD option, the new Client's address as the link-layer 2132 source address and the old Client's address as the link-layer 2133 destination address. When the old Client receives the Release 2134 message, it changes the link-layer source address to its own address, 2135 changes the link-layer destination address to the address of its 2136 Server, and forwards the message to the Server. At the same time, 2137 the old Client sends a Predirect message back to the new Client and 2138 queues any arriving data packets addressed to the departed MN. When 2139 the new Client receives the Predirect, it creates a neighbor cache 2140 entry for the old Client with AcceptTime set to ACCEPT_TIME, then 2141 sends a Redirect message back to the old Client. When the old Client 2142 receives the Redirect message, it creates a neighbor cache entry for 2143 the new Client with ForwardTime set to FORWARD_TIME, then forwards 2144 any queued data packets to the new Client. Finally, the old Client 2145 sends unsolicited Redirect messages to correspondents the same as for 2146 the predictive case. 2148 When a Server processes a Solicit message, it creates a neighbor 2149 cache entry for this ACP if none currently exists. If a neighbor 2150 cache entry already exists, however, the Server changes the link- 2151 layer address to the address of the new proxy Client (this satisfies 2152 the case of both the old Client and new Client using the same 2153 Server). 2155 When a Server processes a Release message, it resets the neighbor 2156 cache entry lifetime for this ACP to 3 seconds if the cached link- 2157 layer address matches the old proxy Client's address. Otherwise, the 2158 Server ignores the Release message (this satisfies the case of both 2159 the old Client and new Client using the same Server). 2161 When a correspondent Client receives an unsolicited Redirect message, 2162 it changes the link-layer address for the ACP's neighbor cache entry 2163 to the address of the new proxy Client. 2165 From an architectural perspective, in addition to the use of DHCPv6 2166 PD and IPv6 ND signaling the AERO approach differs from PMIPv6 in its 2167 use of the NBMA virtual link model instead of point-to-point tunnels. 2168 This provides a more agile interface for Client/Server and Client/ 2169 Client coordinations, and also facilitates simple route optimization. 2170 The AERO routing system is also arranged in such a fashion that 2171 Clients get the same service from any Server they happen to associate 2172 with. This provides a natural fault tolerance and load balancing 2173 capability such as desired for distributed mobility management. 2175 3.21. Extending AERO Links Through Security Gateways 2177 When an enterprise mobile device moves from a campus LAN connection 2178 to a public Internet link, it must re-enter the enterprise via a 2179 security gateway that has both a physical interface connection to the 2180 Internet and a physical interface connection to the enterprise 2181 internetwork. This most often entails the establishment of a Virtual 2182 Private Network (VPN) link over the public Internet from the mobile 2183 device to the security gateway. During this process, the mobile 2184 device supplies the security gateway with its public Internet address 2185 as the link-layer address for the VPN. The mobile device then acts 2186 as an AERO Client to negotiate with the security gateway to obtain 2187 its ACP. 2189 In order to satisfy this need, the security gateway also operates as 2190 an AERO Server with support for AERO Client proxying. In particular, 2191 when a mobile device (i.e., the Client) connects via the security 2192 gateway (i.e., the Server), the Server provides the Client with an 2193 ACP in a DHCPv6 PD exchange the same as if it were attached to an 2194 enterprise campus access link. The Server then replaces the Client's 2195 link-layer source address with the Server's enterprise-facing link- 2196 layer address in all AERO messages the Client sends toward neighbors 2197 on the AERO link. The AERO messages are then delivered to other 2198 devices on the AERO link as if they were originated by the security 2199 gateway instead of by the AERO Client. In the reverse direction, the 2200 AERO messages sourced by devices within the enterprise network can be 2201 forwarded to the security gateway, which then replaces the link-layer 2202 destination address with the Client's link-layer address and replaces 2203 the link-layer source address with its own (Internet-facing) link- 2204 layer address. 2206 After receiving the ACP, the Client can send IP packets that use an 2207 address taken from the ACP as the network layer source address, the 2208 Client's link-layer address as the link-layer source address, and the 2209 Server's Internet-facing link-layer address as the link-layer 2210 destination address. The Server will then rewrite the link-layer 2211 source address with the Server's own enterprise-facing link-layer 2212 address and rewrite the link-layer destination address with the 2213 target AERO node's link-layer address, and the packets will enter the 2214 enterprise network as though they were sourced from a device located 2215 within the enterprise. In the reverse direction, when a packet 2216 sourced by a node within the enterprise network uses a destination 2217 address from the Client's ACP, the packet will be delivered to the 2218 security gateway which then rewrites the link-layer destination 2219 address to the Client's link-layer address and rewrites the link- 2220 layer source address to the Server's Internet-facing link-layer 2221 address. The Server then delivers the packet across the VPN to the 2222 AERO Client. In this way, the AERO virtual link is essentially 2223 extended *through* the security gateway to the point at which the VPN 2224 link and AERO link are effectively grafted together by the link-layer 2225 address rewriting performed by the security gateway. All AERO 2226 messaging services (including route optimization and mobility 2227 signaling) are therefore extended to the Client. 2229 In order to support this virtual link grafting, the security gateway 2230 (acting as an AERO Server) must keep static neighbor cache entries 2231 for all of its associated Clients located on the public Internet. 2232 The neighbor cache entry is keyed by the AERO Client's AERO address 2233 the same as if the Client were located within the enterprise 2234 internetwork. The neighbor cache is then managed in all ways as 2235 though the Client were an ordinary AERO Client. This includes the 2236 AERO IPv6 ND messaging signaling for Route Optimization and Neighbor 2237 Unreachability Detection. 2239 Note that the main difference between a security gateway acting as an 2240 AERO Server and an enterprise-internal AERO Server is that the 2241 security gateway has at least one enterprise-internal physical 2242 interface and at least one public Internet physical interface. 2243 Conversely, the enterprise-internal AERO Server has only enterprise- 2244 internal physical interfaces. For this reason security gateway 2245 proxying is needed to ensure that the public Internet link-layer 2246 addressing space is kept separate from the enterprise-internal link- 2247 layer addressing space. This is afforded through a natural extension 2248 of the security association caching already performed for each VPN 2249 client by the security gateway. 2251 3.22. Extending IPv6 AERO Links to the Internet 2253 When an IPv6 host ('H1') with an address from an ACP owned by AERO 2254 Client ('C1') sends packets to a correspondent IPv6 host ('H2'), the 2255 packets eventually arrive at the IPv6 router that owns ('H2')s 2256 prefix. This IPv6 router may or may not be an AERO Client ('C2') 2257 either within the same home network as ('C1') or in a different home 2258 network. 2260 If Client ('C1') is currently located outside the boundaries of its 2261 home network, it will connect back into the home network via a 2262 security gateway acting as an AERO Server. The packets sent by 2263 ('H1') via ('C1') will then be forwarded through the security gateway 2264 then through the home network and finally to ('C2') where they will 2265 be delivered to ('H2'). This could lead to sub-optimal performance 2266 when ('C2') could instead be reached via a more direct route without 2267 involving the security gateway. 2269 Consider the case when host ('H1') has the IPv6 address 2270 2001:db8:1::1, and Client ('C1') has the ACP 2001:db8:1::/64 with 2271 underlying IPv6 Internet address of 2001:db8:1000::1. Also, host 2272 ('H2') has the IPv6 address 2001:db8:2::1, and Client ('C2') has the 2273 ACP 2001:db8:2::/64 with underlying IPv6 address of 2001:db8:2000::1. 2274 Client ('C1') can determine whether 'C2' is indeed also an AERO 2275 Client willing to serve as a route optimization correspondent by 2276 resolving the AAAA records for the DNS FQDN that matches ('H2')s 2277 prefix, i.e.: 2279 '0.0.0.0.2.0.0.0.8.b.d.0.1.0.0.2.aero.linkupnetworks.net' 2281 If ('C2') is indeed a candidate correspondent, the FQDN lookup will 2282 return a PTR resource record that contains the domain name for the 2283 AERO link that manages ('C2')s ASP. Client ('C1') can then attempt 2284 route optimization using an approach similar to the Return 2285 Routability procedure specified for Mobile IPv6 (MIPv6) [RFC6275]. 2286 In order to support this process, both Clients MUST intercept and 2287 decapsulate packets that have a subnet router anycast address 2288 corresponding to any of the /64 prefixes covered by their respective 2289 ACPs. 2291 To initiate the process, Client ('C1') creates a specially-crafted 2292 encapsulated Predirect message that will be routed through its home 2293 network then through ('C2')s home network and finally to ('C2') 2294 itself. Client ('C1') prepares the initial message in the exchange 2295 as follows: 2297 o The encapsulating IPv6 header source address is set to 2298 2001:db8:1:: (i.e., the IPv6 subnet router anycast address for 2299 ('C1')s ACP) 2301 o The encapsulating IPv6 header destination address is set to 2302 2001:db8:2:: (i.e., the IPv6 subnet router anycast address for 2303 ('C2')s ACP) 2305 o The encapsulating IPv6 header is followed by any additional 2306 encapsulation headers 2308 o The encapsulated IPv6 header source address is set to 2309 fe80::2001:db8:1:0 (i.e., the AERO address for ('C1')) 2311 o The encapsulated IPv6 header destination address is set to 2312 fe80::2001:db8:2:0 (i.e., the AERO address for ('C2')) 2314 o The encapsulated Predirect message includes all of the securing 2315 information that would occur in a MIPv6 "Home Test Init" message 2316 (format TBD) 2318 Client ('C1') then further encapsulates the message in the 2319 encapsulating headers necessary to convey the packet to the security 2320 gateway (e.g., through IPsec encapsulation) so that the message now 2321 appears "double-encapsulated". ('C1') then sends the message to the 2322 security gateway, which re-encapsulates and forwards it over the home 2323 network from where it will eventually reach ('C2'). 2325 At the same time, ('C1') creates and sends a second encapsulated 2326 Predirect message that will be routed through the IPv6 Internet 2327 without involving the security gateway. Client ('C1') prepares the 2328 message as follows: 2330 o The encapsulating IPv6 header source address is set to 2331 2001:db8:1000:1 (i.e., the Internet IPv6 address of ('C1')) 2333 o The encapsulating IPv6 header destination address is set to 2334 2001:db8:2:: (i.e., the IPv6 subnet router anycast address for 2335 ('C2')s ACP) 2337 o The encapsulating IPv6 header is followed by any additional 2338 encapsulation headers 2340 o The encapsulated IPv6 header source address is set to 2341 fe80::2001:db8:1:0 (i.e., the AERO address for ('C1')) 2343 o The encapsulated IPv6 header destination address is set to 2344 fe80::2001:db8:2:0 (i.e., the AERO address for ('C2')) 2346 o The encapsulated Predirect message includes all of the securing 2347 information that would occur in a MIPv6 "Care-of Test Init" 2348 message (format TBD) 2350 ('C2') will receive both Predirect messages through its home network 2351 then return a corresponding Redirect for each of the Predirect 2352 messages with the source and destination addresses in the inner and 2353 outer headers reversed. The first message includes all of the 2354 securing information that would occur in a MIPv6 "Home Test" message, 2355 while the second message includes all of the securing information 2356 that would occur in a MIPv6 "Care-of Test" message (formats TBD). 2358 When ('C1') receives the Redirect messages, it performs the necessary 2359 security procedures per the MIPv6 specification. It then prepares an 2360 encapsulated NS message that includes the same source and destination 2361 addresses as for the "Care-of Test Init" Predirect message, and 2362 includes all of the securing information that would occur in a MIPv6 2363 "Binding Update" message (format TBD) and sends the message to 2364 ('C2'). 2366 When ('C2') receives the NS message, if the securing information is 2367 correct it creates or updates a neighbor cache entry for ('C1') with 2368 fe80::2001:db8:1:0 as the network-layer address, 2001:db8:1000::1 as 2369 the link-layer address and with AcceptTime set to ACCEPT_TIME. 2370 ('C2') then sends an encapsulated NA message back to ('C1') that 2371 includes the same source and destination addresses as for the "Care- 2372 of Test" Redirect message, and includes all of the securing 2373 information that would occur in a MIPv6 "Binding Acknowledgement" 2374 message (format TBD) and sends the message to ('C1'). 2376 When ('C1') receives the NA message, it creates or updates a neighbor 2377 cache entry for ('C2') with fe80::2001:db8:2:0 as the network-layer 2378 address and 2001:db8:2:: as the link-layer address and with 2379 ForwardTime set to FORWARD_TIME, thus completing the route 2380 optimization in the forward direction. 2382 ('C1') subsequently forwards encapsulated packets with outer source 2383 address 2001:db8:1000::1, with outer destination address 2384 2001:db8:2::, with inner source address taken from the 2001:db8:1::, 2385 and with inner destination address taken from 2001:db8:2:: due to the 2386 fact that it has a securely-established neighbor cache entry with 2387 non-zero ForwardTime. ('C2') subsequently accepts any such 2388 encapsulated packets due to the fact that it has a securely- 2389 established neighbor cache entry with non-zero AcceptTime. 2391 In order to keep neighbor cache entries alive, ('C1') periodically 2392 sends additional NS messages to ('C2') and receives any NA responses. 2393 If ('C1') moves to a different point of attachment after the initial 2394 route optimization, it sends a new secured NS message to ('C2') as 2395 above to update ('C2')s neighbor cache. 2397 If ('C2') has packets to send to ('C1'), it performs a corresponding 2398 route optimization in the opposite direction following the same 2399 procedures described above. In the process, the already-established 2400 unidirectional neighbor cache entries within ('C1') and ('C2') are 2401 updated to include the now-bidirectional information. In particular, 2402 the AcceptTime and ForwardTime variables for both neighbor cache 2403 entries are updated to non-zero values, and the link-layer address 2404 for ('C1')s neighbor cache entry for ('C2') is reset to 2405 2001:db8:2000::1. 2407 Note that two AERO Clients can use full security protocol messaging 2408 instead of Return Routability, e.g., if strong authentication and/or 2409 confidentiality are desired. In that case, security protocol key 2410 exchanges such as specified for MOBIKE [RFC4555] would be used to 2411 establish security associations and neighbor cache entries between 2412 the AERO clients. Thereafter, NS/NA messaging can be used to 2413 maintain neighbor cache entries, test reachability, and to announce 2414 mobility events. If reachability testing fails, e.g., if both 2415 Clients move at roughly the same time, the Clients can tear down the 2416 security association and neighbor cache entries and again allow 2417 packets to flow through their home network. 2419 3.23. Encapsulation Protocol Version Considerations 2421 A source Client may connect only to an IPvX underlying network, while 2422 the target Client connects only to an IPvY underlying network. In 2423 that case, the target and source Clients have no means for reaching 2424 each other directly (since they connect to underlying networks of 2425 different IP protocol versions) and so must ignore any redirection 2426 messages and continue to send packets via their Servers. 2428 3.24. Multicast Considerations 2430 When the underlying network does not support multicast, AERO Clients 2431 map link-scoped multicast addresses to the link-layer address of a 2432 Server, which acts as a multicast forwarding agent. The AERO Client 2433 also serves as an IGMP/MLD Proxy for its EUNs and/or hosted 2434 applications per [RFC4605] while using the link-layer address of the 2435 Server as the link-layer address for all multicast packets. 2437 When the underlying network supports multicast, AERO nodes use the 2438 multicast address mapping specification found in [RFC2529] for IPv4 2439 underlying networks and use a TBD site-scoped multicast mapping for 2440 IPv6 underlying networks. In that case, border routers must ensure 2441 that the encapsulated site-scoped multicast packets do not leak 2442 outside of the site spanned by the AERO link. 2444 3.25. Operation on AERO Links Without DHCPv6 Services 2446 When Servers on the AERO link do not provide DHCPv6 services, 2447 operation can still be accommodated through administrative 2448 configuration of ACPs on AERO Clients. In that case, administrative 2449 configurations of AERO interface neighbor cache entries on both the 2450 Server and Client are also necessary. However, this may interfere 2451 with the ability for Clients to dynamically change to new Servers, 2452 and can expose the AERO link to misconfigurations unless the 2453 administrative configurations are carefully coordinated. 2455 3.26. Operation on Server-less AERO Links 2457 In some AERO link scenarios, there may be no Servers on the link and/ 2458 or no need for Clients to use a Server as an intermediary trust 2459 anchor. In that case, each Client acts as a Server unto itself to 2460 establish neighbor cache entries by performing direct Client-to- 2461 Client IPv6 ND message exchanges, and some other form of trust basis 2462 must be applied so that each Client can verify that the prospective 2463 neighbor is authorized to use its claimed ACP. 2465 When there is no Server on the link, Clients must arrange to receive 2466 ACPs and publish them via a secure alternate prefix delegation 2467 authority through some means outside the scope of this document. 2469 3.27. Manually-Configured AERO Tunnels 2471 In addition to the dynamic neighbor discovery procedures for AERO 2472 link neighbors described above, AERO encapsulation can be applied to 2473 manually-configured tunnels. In that case, the tunnel endpoints use 2474 an administratively-assigned link-local address and exchange NS/NA 2475 messages the same as for dynamically-established tunnels. 2477 3.28. Intradomain Routing 2479 After a tunnel neighbor relationship has been established, neighbors 2480 can use a traditional dynamic routing protocol over the tunnel to 2481 exchange routing information without having to inject the routes into 2482 the AERO routing system. 2484 4. Implementation Status 2486 User-level and kernel-level AERO implementations have been developed 2487 and are undergoing internal testing within Boeing. 2489 An initial public release of the AERO source code was announced on 2490 the intarea mailing list on August 21, 2015, and a pointer to the 2491 code is available in the list archives. 2493 5. IANA Considerations 2495 The IANA has assigned a 4-octet Private Enterprise Number "45282" for 2496 AERO in the "enterprise-numbers" registry. 2498 The IANA has assigned the UDP port number "8060" for an earlier 2499 experimental version of AERO [RFC6706]. This document obsoletes 2500 [RFC6706] and claims the UDP port number "8060" for all future use. 2502 No further IANA actions are required. 2504 6. Security Considerations 2506 AERO link security considerations are the same as for standard IPv6 2507 Neighbor Discovery [RFC4861] except that AERO improves on some 2508 aspects. In particular, AERO uses a trust basis between Clients and 2509 Servers, where the Clients only engage in the AERO mechanism when it 2510 is facilitated by a trust anchor. Unless there is some other means 2511 of authenticating the Client's identity (e.g., link-layer security), 2512 AERO nodes SHOULD also use DHCPv6 securing services (e.g., DHCPv6 2513 authentication, Secure DHCPv6 [I-D.ietf-dhc-sedhcpv6], etc.) for 2514 Client authentication and network admission control. In particular, 2515 Clients SHOULD include authenticating information on each 2516 Solicit/Rebind/Release message they send, but omit authenticating 2517 information on Renew messages. Renew messages are exempt due to the 2518 fact that the Renew must already be checked for having a correct 2519 link-layer address and does not update any link-layer addresses. 2520 Therefore, asking the Server to also authenticate the Renew message 2521 would be unnecessary and could result in excessive processing 2522 overhead. 2524 Redirect, Predirect and unsolicited NA messages SHOULD include a 2525 Timestamp option (see Section 5.3 of [RFC3971]) that other AERO nodes 2526 can use to verify the message time of origin. Predirect, NS and RS 2527 messages SHOULD include a Nonce option (see Section 5.3 of [RFC3971]) 2528 that recipients echo back in corresponding responses. 2530 AERO links must be protected against link-layer address spoofing 2531 attacks in which an attacker on the link pretends to be a trusted 2532 neighbor. Links that provide link-layer securing mechanisms (e.g., 2533 IEEE 802.1X WLANs) and links that provide physical security (e.g., 2534 enterprise network wired LANs) provide a first line of defense that 2535 is often sufficient. In other instances, additional securing 2536 mechanisms such as Secure Neighbor Discovery (SeND) [RFC3971], IPsec 2537 [RFC4301] or TLS [RFC5246] may be necessary. 2539 AERO Clients MUST ensure that their connectivity is not used by 2540 unauthorized nodes on their EUNs to gain access to a protected 2541 network, i.e., AERO Clients that act as routers MUST NOT provide 2542 routing services for unauthorized nodes. (This concern is no 2543 different than for ordinary hosts that receive an IP address 2544 delegation but then "share" the address with unauthorized nodes via 2545 some form of Internet connection sharing.) 2547 On some AERO links, establishment and maintenance of a direct path 2548 between neighbors requires secured coordination such as through the 2549 Internet Key Exchange (IKEv2) protocol [RFC5996] to establish a 2550 security association. 2552 An AERO Client's link-layer address could be rewritten by a link- 2553 layer switching element on the path from the Client to the Server and 2554 not detected by the DHCPv6 security mechanism. However, such a 2555 condition would only be a matter of concern on unmanaged/unsecured 2556 links where the link-layer switching elements themselves present a 2557 man-in-the-middle attack threat. For this reason, IP security MUST 2558 be used when AERO is employed over unmanaged/unsecured links. 2560 7. Acknowledgements 2562 Discussions both on IETF lists and in private exchanges helped shape 2563 some of the concepts in this work. Individuals who contributed 2564 insights include Mikael Abrahamsson, Mark Andrews, Fred Baker, 2565 Stewart Bryant, Brian Carpenter, Wojciech Dec, Ralph Droms, Adrian 2566 Farrel, Sri Gundavelli, Brian Haberman, Joel Halpern, Tom Herbert, 2567 Sascha Hlusiak, Lee Howard, Andre Kostur, Ted Lemon, Andy Malis, 2568 Satoru Matsushima, Tomek Mrugalski, Alexandru Petrescu, Behcet 2569 Saikaya, Joe Touch, Bernie Volz, Ryuji Wakikawa and Lloyd Wood. 2570 Members of the IESG also provided valuable input during their review 2571 process that greatly improved the document. Discussions on the v6ops 2572 list in the December 2015 through January 2016 timeframe further 2573 helped clarify AERO multi-addressing capabilities. Special thanks go 2574 to Stewart Bryant, Joel Halpern and Brian Haberman for their 2575 shepherding guidance during the publication of the AERO first 2576 edition. 2578 This work has further been encouraged and supported by Boeing 2579 colleagues including M. Wayne Benson, Dave Bernhardt, Cam Brodie, 2580 Balaguruna Chidambaram, Irene Chin, Bruce Cornish, Claudiu Danilov, 2581 Wen Fang, Anthony Gregory, Jeff Holland, Ed King, Gen MacLean, Rob 2582 Muszkiewicz, Sean O'Sullivan, Kent Shuey, Brian Skeen, Mike Slane, 2583 Brendan Williams, Julie Wulff, Yueli Yang, and other members of the 2584 BR&T and BIT mobile networking teams. Wayne Benson is especially 2585 acknowledged for his outstanding work in converting the AERO proof- 2586 of-concept implementation into production-ready code. 2588 Earlier works on NBMA tunneling approaches are found in 2589 [RFC2529][RFC5214][RFC5569]. 2591 Many of the constructs presented in this second edition of AERO are 2592 based on the author's earlier works, including: 2594 o The Internet Routing Overlay Network (IRON) 2595 [RFC6179][I-D.templin-ironbis] 2597 o Virtual Enterprise Traversal (VET) 2598 [RFC5558][I-D.templin-intarea-vet] 2600 o The Subnetwork Encapsulation and Adaptation Layer (SEAL) 2601 [RFC5320][I-D.templin-intarea-seal] 2603 o AERO, First Edition [RFC6706] 2605 Note that these works cite numerous earlier efforts that are not also 2606 cited here due to space limitations. The authors of those earlier 2607 works are acknowledged for their insights. 2609 8. References 2611 8.1. Normative References 2613 [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, 2614 DOI 10.17487/RFC0768, August 1980, 2615 . 2617 [RFC0791] Postel, J., "Internet Protocol", STD 5, RFC 791, 2618 DOI 10.17487/RFC0791, September 1981, 2619 . 2621 [RFC0792] Postel, J., "Internet Control Message Protocol", STD 5, 2622 RFC 792, DOI 10.17487/RFC0792, September 1981, 2623 . 2625 [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, 2626 DOI 10.17487/RFC2003, October 1996, 2627 . 2629 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2630 Requirement Levels", BCP 14, RFC 2119, 2631 DOI 10.17487/RFC2119, March 1997, 2632 . 2634 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 2635 (IPv6) Specification", RFC 2460, DOI 10.17487/RFC2460, 2636 December 1998, . 2638 [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in 2639 IPv6 Specification", RFC 2473, DOI 10.17487/RFC2473, 2640 December 1998, . 2642 [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, 2643 "Definition of the Differentiated Services Field (DS 2644 Field) in the IPv4 and IPv6 Headers", RFC 2474, 2645 DOI 10.17487/RFC2474, December 1998, 2646 . 2648 [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, 2649 C., and M. Carney, "Dynamic Host Configuration Protocol 2650 for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July 2651 2003, . 2653 [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic 2654 Host Configuration Protocol (DHCP) version 6", RFC 3633, 2655 DOI 10.17487/RFC3633, December 2003, 2656 . 2658 [RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander, 2659 "SEcure Neighbor Discovery (SEND)", RFC 3971, 2660 DOI 10.17487/RFC3971, March 2005, 2661 . 2663 [RFC4213] Nordmark, E. and R. Gilligan, "Basic Transition Mechanisms 2664 for IPv6 Hosts and Routers", RFC 4213, 2665 DOI 10.17487/RFC4213, October 2005, 2666 . 2668 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 2669 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 2670 DOI 10.17487/RFC4861, September 2007, 2671 . 2673 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 2674 Address Autoconfiguration", RFC 4862, 2675 DOI 10.17487/RFC4862, September 2007, 2676 . 2678 [RFC6434] Jankiewicz, E., Loughney, J., and T. Narten, "IPv6 Node 2679 Requirements", RFC 6434, DOI 10.17487/RFC6434, December 2680 2011, . 2682 8.2. Informative References 2684 [I-D.herbert-gue-fragmentation] 2685 Herbert, T. and F. Templin, "Fragmentation option for 2686 Generic UDP Encapsulation", draft-herbert-gue- 2687 fragmentation-02 (work in progress), October 2015. 2689 [I-D.ietf-dhc-sedhcpv6] 2690 Jiang, S., Li, L., Cui, Y., Jinmei, T., Lemon, T., and D. 2691 Zhang, "Secure DHCPv6", draft-ietf-dhc-sedhcpv6-13 (work 2692 in progress), July 2016. 2694 [I-D.ietf-intarea-tunnels] 2695 Touch, D. and W. Townsley, "IP Tunnels in the Internet 2696 Architecture", draft-ietf-intarea-tunnels-03 (work in 2697 progress), July 2016. 2699 [I-D.ietf-nvo3-gue] 2700 Herbert, T., Yong, L., and O. Zia, "Generic UDP 2701 Encapsulation", draft-ietf-nvo3-gue-04 (work in progress), 2702 July 2016. 2704 [I-D.templin-intarea-grefrag] 2705 Templin, F., "GRE Tunnel Fragmentation", draft-templin- 2706 intarea-grefrag-02 (work in progress), January 2016. 2708 [I-D.templin-intarea-seal] 2709 Templin, F., "The Subnetwork Encapsulation and Adaptation 2710 Layer (SEAL)", draft-templin-intarea-seal-68 (work in 2711 progress), January 2014. 2713 [I-D.templin-intarea-vet] 2714 Templin, F., "Virtual Enterprise Traversal (VET)", draft- 2715 templin-intarea-vet-40 (work in progress), May 2013. 2717 [I-D.templin-ironbis] 2718 Templin, F., "The Interior Routing Overlay Network 2719 (IRON)", draft-templin-ironbis-16 (work in progress), 2720 March 2014. 2722 [RFC0879] Postel, J., "The TCP Maximum Segment Size and Related 2723 Topics", RFC 879, DOI 10.17487/RFC0879, November 1983, 2724 . 2726 [RFC1035] Mockapetris, P., "Domain names - implementation and 2727 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 2728 November 1987, . 2730 [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - 2731 Communication Layers", STD 3, RFC 1122, 2732 DOI 10.17487/RFC1122, October 1989, 2733 . 2735 [RFC1191] Mogul, J. and S. Deering, "Path MTU discovery", RFC 1191, 2736 DOI 10.17487/RFC1191, November 1990, 2737 . 2739 [RFC1812] Baker, F., Ed., "Requirements for IP Version 4 Routers", 2740 RFC 1812, DOI 10.17487/RFC1812, June 1995, 2741 . 2743 [RFC1930] Hawkinson, J. and T. Bates, "Guidelines for creation, 2744 selection, and registration of an Autonomous System (AS)", 2745 BCP 6, RFC 1930, DOI 10.17487/RFC1930, March 1996, 2746 . 2748 [RFC1981] McCann, J., Deering, S., and J. Mogul, "Path MTU Discovery 2749 for IP version 6", RFC 1981, DOI 10.17487/RFC1981, August 2750 1996, . 2752 [RFC2131] Droms, R., "Dynamic Host Configuration Protocol", 2753 RFC 2131, DOI 10.17487/RFC2131, March 1997, 2754 . 2756 [RFC2529] Carpenter, B. and C. Jung, "Transmission of IPv6 over IPv4 2757 Domains without Explicit Tunnels", RFC 2529, 2758 DOI 10.17487/RFC2529, March 1999, 2759 . 2761 [RFC2675] Borman, D., Deering, S., and R. Hinden, "IPv6 Jumbograms", 2762 RFC 2675, DOI 10.17487/RFC2675, August 1999, 2763 . 2765 [RFC2764] Gleeson, B., Lin, A., Heinanen, J., Armitage, G., and A. 2766 Malis, "A Framework for IP Based Virtual Private 2767 Networks", RFC 2764, DOI 10.17487/RFC2764, February 2000, 2768 . 2770 [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 2771 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, 2772 DOI 10.17487/RFC2784, March 2000, 2773 . 2775 [RFC2890] Dommety, G., "Key and Sequence Number Extensions to GRE", 2776 RFC 2890, DOI 10.17487/RFC2890, September 2000, 2777 . 2779 [RFC2923] Lahey, K., "TCP Problems with Path MTU Discovery", 2780 RFC 2923, DOI 10.17487/RFC2923, September 2000, 2781 . 2783 [RFC2983] Black, D., "Differentiated Services and Tunnels", 2784 RFC 2983, DOI 10.17487/RFC2983, October 2000, 2785 . 2787 [RFC3168] Ramakrishnan, K., Floyd, S., and D. Black, "The Addition 2788 of Explicit Congestion Notification (ECN) to IP", 2789 RFC 3168, DOI 10.17487/RFC3168, September 2001, 2790 . 2792 [RFC3596] Thomson, S., Huitema, C., Ksinant, V., and M. Souissi, 2793 "DNS Extensions to Support IP Version 6", RFC 3596, 2794 DOI 10.17487/RFC3596, October 2003, 2795 . 2797 [RFC3819] Karn, P., Ed., Bormann, C., Fairhurst, G., Grossman, D., 2798 Ludwig, R., Mahdavi, J., Montenegro, G., Touch, J., and L. 2799 Wood, "Advice for Internet Subnetwork Designers", BCP 89, 2800 RFC 3819, DOI 10.17487/RFC3819, July 2004, 2801 . 2803 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 2804 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 2805 DOI 10.17487/RFC4271, January 2006, 2806 . 2808 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2809 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 2810 2006, . 2812 [RFC4301] Kent, S. and K. Seo, "Security Architecture for the 2813 Internet Protocol", RFC 4301, DOI 10.17487/RFC4301, 2814 December 2005, . 2816 [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet 2817 Control Message Protocol (ICMPv6) for the Internet 2818 Protocol Version 6 (IPv6) Specification", RFC 4443, 2819 DOI 10.17487/RFC4443, March 2006, 2820 . 2822 [RFC4459] Savola, P., "MTU and Fragmentation Issues with In-the- 2823 Network Tunneling", RFC 4459, DOI 10.17487/RFC4459, April 2824 2006, . 2826 [RFC4511] Sermersheim, J., Ed., "Lightweight Directory Access 2827 Protocol (LDAP): The Protocol", RFC 4511, 2828 DOI 10.17487/RFC4511, June 2006, 2829 . 2831 [RFC4555] Eronen, P., "IKEv2 Mobility and Multihoming Protocol 2832 (MOBIKE)", RFC 4555, DOI 10.17487/RFC4555, June 2006, 2833 . 2835 [RFC4592] Lewis, E., "The Role of Wildcards in the Domain Name 2836 System", RFC 4592, DOI 10.17487/RFC4592, July 2006, 2837 . 2839 [RFC4605] Fenner, B., He, H., Haberman, B., and H. Sandick, 2840 "Internet Group Management Protocol (IGMP) / Multicast 2841 Listener Discovery (MLD)-Based Multicast Forwarding 2842 ("IGMP/MLD Proxying")", RFC 4605, DOI 10.17487/RFC4605, 2843 August 2006, . 2845 [RFC4821] Mathis, M. and J. Heffner, "Packetization Layer Path MTU 2846 Discovery", RFC 4821, DOI 10.17487/RFC4821, March 2007, 2847 . 2849 [RFC4963] Heffner, J., Mathis, M., and B. Chandler, "IPv4 Reassembly 2850 Errors at High Data Rates", RFC 4963, 2851 DOI 10.17487/RFC4963, July 2007, 2852 . 2854 [RFC4994] Zeng, S., Volz, B., Kinnear, K., and J. Brzozowski, 2855 "DHCPv6 Relay Agent Echo Request Option", RFC 4994, 2856 DOI 10.17487/RFC4994, September 2007, 2857 . 2859 [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., 2860 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 2861 RFC 5213, DOI 10.17487/RFC5213, August 2008, 2862 . 2864 [RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site 2865 Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, 2866 DOI 10.17487/RFC5214, March 2008, 2867 . 2869 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 2870 (TLS) Protocol Version 1.2", RFC 5246, 2871 DOI 10.17487/RFC5246, August 2008, 2872 . 2874 [RFC5320] Templin, F., Ed., "The Subnetwork Encapsulation and 2875 Adaptation Layer (SEAL)", RFC 5320, DOI 10.17487/RFC5320, 2876 February 2010, . 2878 [RFC5494] Arkko, J. and C. Pignataro, "IANA Allocation Guidelines 2879 for the Address Resolution Protocol (ARP)", RFC 5494, 2880 DOI 10.17487/RFC5494, April 2009, 2881 . 2883 [RFC5522] Eddy, W., Ivancic, W., and T. Davis, "Network Mobility 2884 Route Optimization Requirements for Operational Use in 2885 Aeronautics and Space Exploration Mobile Networks", 2886 RFC 5522, DOI 10.17487/RFC5522, October 2009, 2887 . 2889 [RFC5558] Templin, F., Ed., "Virtual Enterprise Traversal (VET)", 2890 RFC 5558, DOI 10.17487/RFC5558, February 2010, 2891 . 2893 [RFC5569] Despres, R., "IPv6 Rapid Deployment on IPv4 2894 Infrastructures (6rd)", RFC 5569, DOI 10.17487/RFC5569, 2895 January 2010, . 2897 [RFC5720] Templin, F., "Routing and Addressing in Networks with 2898 Global Enterprise Recursion (RANGER)", RFC 5720, 2899 DOI 10.17487/RFC5720, February 2010, 2900 . 2902 [RFC5844] Wakikawa, R. and S. Gundavelli, "IPv4 Support for Proxy 2903 Mobile IPv6", RFC 5844, DOI 10.17487/RFC5844, May 2010, 2904 . 2906 [RFC5949] Yokota, H., Chowdhury, K., Koodli, R., Patil, B., and F. 2907 Xia, "Fast Handovers for Proxy Mobile IPv6", RFC 5949, 2908 DOI 10.17487/RFC5949, September 2010, 2909 . 2911 [RFC5996] Kaufman, C., Hoffman, P., Nir, Y., and P. Eronen, 2912 "Internet Key Exchange Protocol Version 2 (IKEv2)", 2913 RFC 5996, DOI 10.17487/RFC5996, September 2010, 2914 . 2916 [RFC6146] Bagnulo, M., Matthews, P., and I. van Beijnum, "Stateful 2917 NAT64: Network Address and Protocol Translation from IPv6 2918 Clients to IPv4 Servers", RFC 6146, DOI 10.17487/RFC6146, 2919 April 2011, . 2921 [RFC6179] Templin, F., Ed., "The Internet Routing Overlay Network 2922 (IRON)", RFC 6179, DOI 10.17487/RFC6179, March 2011, 2923 . 2925 [RFC6204] Singh, H., Beebee, W., Donley, C., Stark, B., and O. 2926 Troan, Ed., "Basic Requirements for IPv6 Customer Edge 2927 Routers", RFC 6204, DOI 10.17487/RFC6204, April 2011, 2928 . 2930 [RFC6221] Miles, D., Ed., Ooghe, S., Dec, W., Krishnan, S., and A. 2931 Kavanagh, "Lightweight DHCPv6 Relay Agent", RFC 6221, 2932 DOI 10.17487/RFC6221, May 2011, 2933 . 2935 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 2936 and A. Bierman, Ed., "Network Configuration Protocol 2937 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 2938 . 2940 [RFC6275] Perkins, C., Ed., Johnson, D., and J. Arkko, "Mobility 2941 Support in IPv6", RFC 6275, DOI 10.17487/RFC6275, July 2942 2011, . 2944 [RFC6355] Narten, T. and J. Johnson, "Definition of the UUID-Based 2945 DHCPv6 Unique Identifier (DUID-UUID)", RFC 6355, 2946 DOI 10.17487/RFC6355, August 2011, 2947 . 2949 [RFC6422] Lemon, T. and Q. Wu, "Relay-Supplied DHCP Options", 2950 RFC 6422, DOI 10.17487/RFC6422, December 2011, 2951 . 2953 [RFC6438] Carpenter, B. and S. Amante, "Using the IPv6 Flow Label 2954 for Equal Cost Multipath Routing and Link Aggregation in 2955 Tunnels", RFC 6438, DOI 10.17487/RFC6438, November 2011, 2956 . 2958 [RFC6691] Borman, D., "TCP Options and Maximum Segment Size (MSS)", 2959 RFC 6691, DOI 10.17487/RFC6691, July 2012, 2960 . 2962 [RFC6706] Templin, F., Ed., "Asymmetric Extended Route Optimization 2963 (AERO)", RFC 6706, DOI 10.17487/RFC6706, August 2012, 2964 . 2966 [RFC6864] Touch, J., "Updated Specification of the IPv4 ID Field", 2967 RFC 6864, DOI 10.17487/RFC6864, February 2013, 2968 . 2970 [RFC6935] Eubanks, M., Chimento, P., and M. Westerlund, "IPv6 and 2971 UDP Checksums for Tunneled Packets", RFC 6935, 2972 DOI 10.17487/RFC6935, April 2013, 2973 . 2975 [RFC6936] Fairhurst, G. and M. Westerlund, "Applicability Statement 2976 for the Use of IPv6 UDP Datagrams with Zero Checksums", 2977 RFC 6936, DOI 10.17487/RFC6936, April 2013, 2978 . 2980 [RFC6939] Halwasia, G., Bhandari, S., and W. Dec, "Client Link-Layer 2981 Address Option in DHCPv6", RFC 6939, DOI 10.17487/RFC6939, 2982 May 2013, . 2984 [RFC6980] Gont, F., "Security Implications of IPv6 Fragmentation 2985 with IPv6 Neighbor Discovery", RFC 6980, 2986 DOI 10.17487/RFC6980, August 2013, 2987 . 2989 [RFC7078] Matsumoto, A., Fujisaki, T., and T. Chown, "Distributing 2990 Address Selection Policy Using DHCPv6", RFC 7078, 2991 DOI 10.17487/RFC7078, January 2014, 2992 . 2994 [TUNTAP] Wikipedia, W., "http://en.wikipedia.org/wiki/TUN/TAP", 2995 October 2014. 2997 Appendix A. AERO Alternate Encapsulations 2999 When GUE encapsulation is not needed, AERO can use common 3000 encapsulations such as IP-in-IP [RFC2003][RFC2473][RFC4213], Generic 3001 Routing Encapsulation (GRE) [RFC2784][RFC2890] and others. The 3002 encapsulation is therefore only differentiated from non-AERO tunnels 3003 through the application of AERO control messaging and not through, 3004 e.g., a well-known UDP port number. 3006 As for GUE encapsulation, alternate AERO encapsulation formats may 3007 require encapsulation layer fragmentation. For simple IP-in-IP 3008 encapsulation, an IPv6 fragment header is inserted directly between 3009 the inner and outer IP headers when needed, i.e., even if the outer 3010 header is IPv4. The IPv6 Fragment Header is identified to the outer 3011 IP layer by its IP protocol number, and the Next Header field in the 3012 IPv6 Fragment Header identifies the inner IP header version. For GRE 3013 encapsulation, a GRE fragment header is inserted within the GRE 3014 header [I-D.templin-intarea-grefrag]. 3016 Figure 9 shows the AERO IP-in-IP encapsulation format before any 3017 fragmentation is applied: 3019 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3020 | Outer IPv4 Header | | Outer IPv6 Header | 3021 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3022 |IPv6 Frag Header (optional)| |IPv6 Frag Header (optional)| 3023 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3024 | Inner IP Header | | Inner IP Header | 3025 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3026 | | | | 3027 ~ ~ ~ ~ 3028 ~ Inner Packet Body ~ ~ Inner Packet Body ~ 3029 ~ ~ ~ ~ 3030 | | | | 3031 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3033 Minimal Encapsulation in IPv4 Minimal Encapsulation in IPv6 3035 Figure 9: Minimal Encapsulation Format using IP-in-IP 3037 Figure 10 shows the AERO GRE encapsulation format before any 3038 fragmentation is applied: 3040 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3041 | Outer IP Header | 3042 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3043 | GRE Header | 3044 | (with checksum, key, etc..) | 3045 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3046 | GRE Fragment Header (optional)| 3047 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3048 | Inner IP Header | 3049 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3050 | | 3051 ~ ~ 3052 ~ Inner Packet Body ~ 3053 ~ ~ 3054 | | 3055 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 3057 Figure 10: Minimal Encapsulation Using GRE 3059 Alternate encapsulation may be preferred in environments where GUE 3060 encapsulation would add unnecessary overhead. For example, certain 3061 low-bandwidth wireless data links may benefit from a reduced 3062 encapsulation overhead. 3064 GUE encapsulation can traverse network paths that are inaccessible to 3065 non-UDP encapsulations, e.g., for crossing Network Address 3066 Translators (NATs). More and more, network middleboxes are also 3067 being configured to discard packets that include anything other than 3068 a well-known IP protocol such as UDP and TCP. It may therefore be 3069 necessary to determine the potential for middlebox filtering before 3070 enabling alternate encapsulation in a given environment. 3072 In addition to IP-in-IP, GRE and GUE, AERO can also use security 3073 encapsulations such as IPsec and SSL/TLS. In that case, AERO control 3074 messaging and route determination occur before security encapsulation 3075 is applied for outgoing packets and after security decapsulation is 3076 applied for incoming packets. 3078 Appendix B. When to Insert an Encapsulation Fragment Header 3080 An encapsulation fragment header is inserted when the AERO tunnel 3081 ingress needs to apply fragmentation to accommodate packets that must 3082 be delivered without loss due to a size restriction. Fragmentation 3083 is performed on the inner packet while encapsulating each inner 3084 packet fragment in outer IP and encapsulation layer headers that 3085 differ only in the fragment header fields. 3087 The fragment header can also be inserted in order to include a 3088 coherent Identification value with each packet, e.g., to aid in 3089 Duplicate Packet Detection (DPD). In this way, network nodes can 3090 cache the Identification values of recently-seen packets and use the 3091 cached values to determine whether a newly-arrived packet is in fact 3092 a duplicate. The Identification value within each packet could 3093 further provide a rough indicator of packet reordering, e.g., in 3094 cases when the tunnel egress wishes to discard packets that are 3095 grossly out of order. 3097 In some use cases, there may be operational assurance that no 3098 fragmentation of any kind will be necessary, or that only occasional 3099 large control messages will require fragmentation. In that case, the 3100 encapsulation fragment header can be omitted and ordinary 3101 fragmentation of the outer IP protocol version can be applied when 3102 necessary. 3104 Author's Address 3106 Fred L. Templin (editor) 3107 Boeing Research & Technology 3108 P.O. Box 3707 3109 Seattle, WA 98124 3110 USA 3112 Email: fltemplin@acm.org