idnits 2.17.1 draft-templin-6man-omni-interface-16.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 20, 2020) is 1439 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) -- Looks like a reference, but probably isn't: '00' on line 786 -- Looks like a reference, but probably isn't: '03' on line 780 -- Looks like a reference, but probably isn't: '04' on line 781 -- Looks like a reference, but probably isn't: '07' on line 781 -- Looks like a reference, but probably isn't: '28' on line 782 -- Looks like a reference, but probably isn't: '31' on line 782 -- Looks like a reference, but probably isn't: '63' on line 786 -- Looks like a reference, but probably isn't: '64' on line 788 -- Looks like a reference, but probably isn't: '65' on line 789 -- Looks like a reference, but probably isn't: '66' on line 789 == Missing Reference: 'RFCXXXX' is mentioned on line 1242, but not defined -- Looks like a reference, but probably isn't: '67' on line 1490 -- Looks like a reference, but probably isn't: '70' on line 1491 -- Looks like a reference, but probably isn't: '76' on line 1491 == Unused Reference: 'RFC2225' is defined on line 1382, but no explicit reference was found in the text == Unused Reference: 'RFC3692' is defined on line 1402, but no explicit reference was found in the text == Unused Reference: 'RFC7421' is defined on line 1460, but no explicit reference was found in the text == Outdated reference: A later version (-11) exists of draft-templin-6man-dhcpv6-ndopt-09 == Outdated reference: A later version (-99) exists of draft-templin-intarea-6706bis-44 Summary: 0 errors (**), 0 flaws (~~), 7 warnings (==), 14 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 The Boeing Company 4 Intended status: Standards Track A. Whyman 5 Expires: October 22, 2020 MWA Ltd c/o Inmarsat Global Ltd 6 April 20, 2020 8 Transmission of IPv6 Packets over Overlay Multilink Network (OMNI) 9 Interfaces 10 draft-templin-6man-omni-interface-16 12 Abstract 14 Mobile nodes (e.g., aircraft of various configurations, terrestrial 15 vehicles, seagoing vessels, mobile enterprise devices, etc.) 16 communicate with networked correspondents over multiple access 17 network data links and configure mobile routers to connect end user 18 networks. A multilink interface specification is therefore needed 19 for coordination with the network-based mobility service. This 20 document specifies the transmission of IPv6 packets over Overlay 21 Multilink Network (OMNI) Interfaces. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on October 22, 2020. 40 Copyright Notice 42 Copyright (c) 2020 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 59 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 6 60 4. Overlay Multilink Network (OMNI) Interface Model . . . . . . 6 61 5. Maximum Transmission Unit (MTU) and Fragmentation . . . . . . 10 62 6. Frame Format . . . . . . . . . . . . . . . . . . . . . . . . 11 63 7. Link-Local Addresses . . . . . . . . . . . . . . . . . . . . 11 64 8. The SPAN . . . . . . . . . . . . . . . . . . . . . . . . . . 12 65 9. Address Mapping - Unicast . . . . . . . . . . . . . . . . . . 13 66 9.1. Sub-Options . . . . . . . . . . . . . . . . . . . . . . . 14 67 9.1.1. Pad1 . . . . . . . . . . . . . . . . . . . . . . . . 15 68 9.1.2. PadN . . . . . . . . . . . . . . . . . . . . . . . . 16 69 9.1.3. ifIndex-tuple (Type 1) . . . . . . . . . . . . . . . 16 70 9.1.4. ifIndex-tuple (Type 2) . . . . . . . . . . . . . . . 18 71 9.1.5. MS-Register . . . . . . . . . . . . . . . . . . . . . 19 72 9.1.6. MS-Release . . . . . . . . . . . . . . . . . . . . . 19 73 10. Address Mapping - Multicast . . . . . . . . . . . . . . . . . 20 74 11. Conceptual Sending Algorithm . . . . . . . . . . . . . . . . 20 75 11.1. Multiple OMNI Interfaces . . . . . . . . . . . . . . . . 20 76 12. Router Discovery and Prefix Registration . . . . . . . . . . 21 77 13. Secure Redirection . . . . . . . . . . . . . . . . . . . . . 24 78 14. AR and MSE Resilience . . . . . . . . . . . . . . . . . . . . 24 79 15. Detecting and Responding to MSE Failures . . . . . . . . . . 25 80 16. Transition Considerations . . . . . . . . . . . . . . . . . . 25 81 17. OMNI Interfaces on the Open Internet . . . . . . . . . . . . 26 82 18. Time-Varying MNPs . . . . . . . . . . . . . . . . . . . . . . 26 83 19. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 84 20. Security Considerations . . . . . . . . . . . . . . . . . . . 27 85 21. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 28 86 22. References . . . . . . . . . . . . . . . . . . . . . . . . . 28 87 22.1. Normative References . . . . . . . . . . . . . . . . . . 28 88 22.2. Informative References . . . . . . . . . . . . . . . . . 30 89 Appendix A. Type 1 ifIndex-tuple Traffic Classifier Preference 90 Encoding . . . . . . . . . . . . . . . . . . . . . . 32 91 Appendix B. VDL Mode 2 Considerations . . . . . . . . . . . . . 34 92 Appendix C. MN / AR Isolation Through L2 Address Mapping . . . . 35 93 Appendix D. Change Log . . . . . . . . . . . . . . . . . . . . . 36 94 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 41 96 1. Introduction 98 Mobile Nodes (MNs) (e.g., aircraft of various configurations, 99 terrestrial vehicles, seagoing vessels, mobile enterprise devices, 100 etc.) often have multiple data links for communicating with networked 101 correspondents. These data links may have diverse performance, cost 102 and availability properties that can change dynamically according to 103 mobility patterns, flight phases, proximity to infrastructure, etc. 104 MNs coordinate their data links in a discipline known as "multilink", 105 in which a single virtual interface is configured over the underlying 106 data links. 108 The MN configures a virtual interface (termed the "Overlay Multilink 109 Network (OMNI) interface") as a thin layer over the underlying Access 110 Network (ANET) interfaces. The OMNI interface is therefore the only 111 interface abstraction exposed to the IPv6 layer and behaves according 112 to the Non-Broadcast, Multiple Access (NBMA) interface principle, 113 while underlying interfaces appear as link layer communication 114 channels in the architecture. The OMNI interface connects to a 115 virtual overlay service known as the "OMNI link". The OMNI link 116 spans a worldwide Internetwork that may include private-use 117 infrastructures and/or the global public Internet itself. 119 Each MN receives a Mobile Network Prefix (MNP) for numbering 120 downstream-attached End User Networks (EUNs) independently of the 121 access network data links selected for data transport. The MN 122 performs router discovery over the OMNI interface (i.e., similar to 123 IPv6 customer edge routers [RFC7084]) and acts as a mobile router on 124 behalf of its EUNs. The router discovery process is iterated over 125 each of the OMNI interface's underlying interfaces in order to 126 register per-link parameters (see Section 12). 128 The OMNI interface provides a multilink nexus for exchanging inbound 129 and outbound traffic via the correct underlying interface(s). The 130 IPv6 layer sees the OMNI interface as a point of connection to the 131 OMNI link. Each OMNI link has one or more associated Mobility 132 Service Prefixes (MSPs) from which OMNI link MNPs are derived. If 133 there are multiple OMNI links, the IPv6 layer will see multiple OMNI 134 interfaces. 136 The OMNI interface interacts with a network-based Mobility Service 137 (MS) through IPv6 Neighbor Discovery (ND) control message exchanges 138 [RFC4861]. The MS provides Mobility Service Endpoints (MSEs) that 139 track MN movements and represent their MNPs in a global routing or 140 mapping system. 142 This document specifies the transmission of IPv6 packets [RFC8200] 143 and MN/MS control messaging over OMNI interfaces. 145 2. Terminology 147 The terminology in the normative references applies; especially, the 148 terms "link" and "interface" are the same as defined in the IPv6 149 [RFC8200] and IPv6 Neighbor Discovery (ND) [RFC4861] specifications. 150 Also, the Protocol Constants defined in Section 10 of [RFC4861] are 151 used in their same format and meaning in this document. The terms 152 "All-Routers multicast", "All-Nodes multicast" and "Subnet-Router 153 anycast" are defined in [RFC4291] (with Link-Local scope assumed). 155 The following terms are defined within the scope of this document: 157 Mobile Node (MN) 158 an end system with multiple distinct upstream data link 159 connections that are managed together as a single logical unit. 160 The MN's data link connection parameters can change over time due 161 to, e.g., node mobility, link quality, etc. The MN further 162 connects a downstream-attached End User Network (EUN). The term 163 MN used here is distinct from uses in other documents, and does 164 not imply a particular mobility protocol. 166 End User Network (EUN) 167 a simple or complex downstream-attached mobile network that 168 travels with the MN as a single logical unit. The IPv6 addresses 169 assigned to EUN devices remain stable even if the MN's upstream 170 data link connections change. 172 Mobility Service (MS) 173 a mobile routing service that tracks MN movements and ensures that 174 MNs remain continuously reachable even across mobility events. 175 Specific MS details are out of scope for this document. 177 Mobility Service Endpoint (MSE) 178 an entity in the MS (either singluar or aggregate) that 179 coordinates the mobility events of one or more MN. 181 Mobility Service Prefix (MSP) 182 an aggregated IPv6 prefix (e.g., 2001:db8::/32) advertised to the 183 rest of the Internetwork by the MS, and from which more-specific 184 Mobile Network Prefixes (MNPs) are derived. 186 Mobile Network Prefix (MNP) 187 a longer IPv6 prefix taken from an MSP (e.g., 188 2001:db8:1000:2000::/56) and assigned to a MN. MNs sub-delegate 189 the MNP to devices located in EUNs. 191 Access Network (ANET) 192 a data link service network (e.g., an aviation radio access 193 network, satellite service provider network, cellular operator 194 network, wifi network, etc.) that connects MNs. Physical and/or 195 data link level security between the MN and ANET are assumed. 197 Access Router (AR) 198 a first-hop router in the ANET for connecting MNs to 199 correspondents in outside Internetworks. 201 ANET interface 202 a MN's attachment to a link in an ANET. 204 Internetwork (INET) 205 a connected network region with a coherent IP addressing plan that 206 provides transit forwarding services for ANET MNs and INET 207 correspondents. Examples include private enterprise networks, 208 ground domain aviation service networks and the global public 209 Internet itself. 211 INET interface 212 a node's attachment to a link in an INET. 214 OMNI link 215 a virtual overlay configured over one or more INETs and their 216 connected ANETs. An OMNI link can comprise multiple INET segments 217 joined by bridges the same as for any link; the addressing plans 218 in each segment may be mutually exclusive and managed by different 219 administrative entities. 221 OMNI interface 222 a node's attachment to an OMNI link, and configured over one or 223 more underlying ANET/INET interfaces. 225 OMNI link local address (LLA) 226 an IPv6 link-local address constructed as specified in Section 7, 227 and assigned to an OMNI interface. 229 OMNI Option 230 an IPv6 Neighbor Discovery option providing multilink parameters 231 for the OMNI interface as specified in Section 9. 233 Multilink 234 an OMNI interface's manner of managing diverse underlying data 235 link interfaces as a single logical unit. The OMNI interface 236 provides a single unified interface to upper layers, while 237 underlying data link selections are performed on a per-packet 238 basis considering factors such as DSCP, flow label, application 239 policy, signal quality, cost, etc. Multilinking decisions are 240 coordinated in both the outbound (i.e. MN to correspondent) and 241 inbound (i.e., correspondent to MN) directions. 243 L2 244 The second layer in the OSI network model. Also known as "layer- 245 2", "link-layer", "sub-IP layer", "data link layer", etc. 247 L3 248 The third layer in the OSI network model. Also known as "layer- 249 3", "network-layer", "IPv6 layer", etc. 251 underlying interface 252 an ANET/INET interface over which an OMNI interface is configured. 253 The OMNI interface is seen as a L3 interface by the IP layer, and 254 each underlying interface is seen as a L2 interface by the OMNI 255 interface. 257 Mobility Service Identification (MSID) 258 Each MSE and AR is assigned a unique 32-bit Identification (MSID) 259 as specified in Section 7. 261 Spanning Partitioned Administrative Networks (SPAN) 262 A means for bridging disjoint INET partitions as segments of a 263 unified OMNI link the same as for a bridged campus LAN. The SPAN 264 is a mid-layer IPv6 encapsulation service that supports a unified 265 OMNI link view for all segments. 267 3. Requirements 269 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 270 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 271 "OPTIONAL" in this document are to be interpreted as described in BCP 272 14 [RFC2119][RFC8174] when, and only when, they appear in all 273 capitals, as shown here. 275 An implementation is not required to internally use the architectural 276 constructs described here so long as its external behavior is 277 consistent with that described in this document. 279 4. Overlay Multilink Network (OMNI) Interface Model 281 An OMNI interface is a MN virtual interface configured over one or 282 more underlying interfaces, which may be physical (e.g., an 283 aeronautical radio link) or virtual (e.g., an Internet or higher- 284 layer "tunnel"). The MN receives a MNP from the MS, and coordinates 285 with the MS through IPv6 ND message exchanges. The MN uses the MNP 286 to construct a unique OMNI LLA through the algorithmic derivation 287 specified in Section 7 and assigns the LLA to the OMNI interface. 289 The OMNI interface architectural layering model is the same as in 290 [RFC7847], and augmented as shown in Figure 1. The IP layer 291 therefore sees the OMNI interface as a single L3 interface with 292 multiple underlying interfaces that appear as L2 communication 293 channels in the architecture. 295 +----------------------------+ 296 | Upper Layer Protocol | 297 Session-to-IP +---->| | 298 Address Binding | +----------------------------+ 299 +---->| IP (L3) | 300 IP Address +---->| | 301 Binding | +----------------------------+ 302 +---->| OMNI Interface | 303 Logical-to- +---->| (OMNI LLA) | 304 Physical | +----------------------------+ 305 Interface +---->| L2 | L2 | | L2 | 306 Binding |(IF#1)|(IF#2)| ..... |(IF#n)| 307 +------+------+ +------+ 308 | L1 | L1 | | L1 | 309 | | | | | 310 +------+------+ +------+ 312 Figure 1: OMNI Interface Architectural Layering Model 314 The OMNI virtual interface model gives rise to a number of 315 opportunities: 317 o since OMNI LLAs are uniquely derived from an MNP, no Duplicate 318 Address Detection (DAD) or Muticast Listener Discovery (MLD) 319 messaging is necessary. 321 o ANET interfaces do not require any L3 addresses (i.e., not even 322 link-local) in environments where communications are coordinated 323 entirely over the OMNI interface. (An alternative would be to 324 also assign the same OMNI LLA to all ANET interfaces.) 326 o as ANET interface properties change (e.g., link quality, cost, 327 availability, etc.), any active ANET interface can be used to 328 update the profiles of multiple additional ANET interfaces in a 329 single message. This allows for timely adaptation and service 330 continuity under dynamically changing conditions. 332 o coordinating ANET interfaces in this way allows them to be 333 represented in a unified MS profile with provisions for mobility 334 and multilink operations. 336 o exposing a single virtual interface abstraction to the IPv6 layer 337 allows for multilink operation (including QoS based link 338 selection, packet replication, load balancing, etc.) at L2 while 339 still permitting L3 traffic shaping based on, e.g., DSCP, flow 340 label, etc. 342 o L3 sees the OMNI interface as a point of connection to the OMNI 343 link; if there are multiple OMNI links (i.e., multiple MS's), L3 344 will see multiple OMNI interfaces. 346 Other opportunities are discussed in [RFC7847]. 348 Figure 2 depicts the architectural model for a MN connecting to the 349 MS via multiple independent ANETs. When an underlying interface 350 becomes active, the MN's OMNI interface sends native (i.e., 351 unencapsulated) IPv6 ND messages via the underlying interface. IPv6 352 ND messages traverse the ground domain ANETs until they reach an 353 Access Router (AR#1, AR#2, .., AR#n). The AR then coordinates with a 354 Mobility Service Endpoint (MSE#1, MSE#2, ..., MSE#m) in the INET and 355 returns an IPv6 ND message response to the MN. IPv6 ND messages 356 traverse the ANET at layer 2; hence, the Hop Limit is not 357 decremented. 359 +--------------+ 360 | MN | 361 +--------------+ 362 |OMNI interface| 363 +----+----+----+ 364 +--------|IF#1|IF#2|IF#n|------ + 365 / +----+----+----+ \ 366 / | \ 367 / <---- Native | IP ----> \ 368 v v v 369 (:::)-. (:::)-. (:::)-. 370 .-(::ANET:::) .-(::ANET:::) .-(::ANET:::) 371 `-(::::)-' `-(::::)-' `-(::::)-' 372 +----+ +----+ +----+ 373 ... |AR#1| .......... |AR#2| ......... |AR#n| ... 374 . +-|--+ +-|--+ +-|--+ . 375 . | | | 376 . v v v . 377 . <----- Encapsulation -----> . 378 . . 379 . +-----+ (:::)-. . 380 . |MSE#2| .-(::::::::) +-----+ . 381 . +-----+ .-(::: INET :::)-. |MSE#m| . 382 . (::::: Routing ::::) +-----+ . 383 . `-(::: System :::)-' . 384 . +-----+ `-(:::::::-' . 385 . |MSE#1| +-----+ +-----+ . 386 . +-----+ |MSE#3| |MSE#4| . 387 . +-----+ +-----+ . 388 . . 389 . . 390 . <----- Worldwide Connected Internetwork ----> . 391 ........................................................... 393 Figure 2: MN/MS Coordination via Multiple ANETs 395 After the initial IPv6 ND message exchange, the MN can send and 396 receive unencapsulated IPv6 data packets over the OMNI interface. 397 OMNI interface multilink services will forward the packets via ARs in 398 the correct underlying ANETs. The AR encapsulates the packets 399 according to the capabilities provided by the MS and forwards them to 400 the next hop within the worldwide connected Internetwork via optimal 401 routes. 403 5. Maximum Transmission Unit (MTU) and Fragmentation 405 All IPv6 interfaces are REQUIRED to configure a minimum Maximum 406 Transmission Unit (MTU) of 1280 bytes [RFC8200]. The network 407 therefore MUST forward packets of at least 1280 bytes without 408 generating an IPv6 Path MTU Discovery (PMTUD) Packet Too Big (PTB) 409 message [RFC8201]. 411 The OMNI interface configures an MTU of 9180 bytes [RFC2492]; the 412 size is therefore not a reflection of the underlying interface MTUs, 413 but rather determines the largest packet the OMNI interface can 414 forward or reassemble. The OMNI interface therefore accommodates IP 415 packets up to 9180 bytes while generating IPv6 Path MTU Discovery 416 (PMTUD) Packet Too Big (PTB) messages [RFC8201] as necessary (see 417 below). 419 OMNI interfaces employ mid-layer IPv6 encapsulation and 420 fragmentation/reassembly per [RFC2473] (also known as "SPAN 421 encapsulation" - see Section 8) to accommodate the 9180 byte MTU. 422 The OMNI interface returns internally-generated PTB messages for 423 packets admitted into the interface that it deems too large (e.g., 424 according to link performance characteristics, reassembly cost, etc.) 425 while either dropping or forwarding the packet as necessary. The 426 OMNI interface performs PMTUD even if the destination appears to be 427 on the same link since an OMNI link node on the path may return a 428 PTB. This ensures that the path MTU is adaptive and reflects the 429 current path used for a given data flow. 431 OMNI interfaces perform SPAN encapsulation and fragmentation/ 432 reassembly as follows: 434 o When an OMNI interface sends a packet toward a final destination 435 via an ANET peer, it sends without SPAN encapsulation if the 436 packet is no larger than the underlying interface MTU. Otherwise, 437 it encapsulates the packet in a SPAN header with source address 438 set to the node's own SPAN address and destination set to the SPAN 439 address of the ANET peer. The OMNI interface then uses IPv6 440 fragmentation to break the encapsulated packet into a minimum 441 number of non-overlapping fragments, where the largest fragment 442 size is determined by the underlying interface MTU and the 443 smallest fragment is no smaller than 640 bytes. The OMNI 444 interface then sends the fragments to the ANET peer, which 445 reassembles before forwarding toward the final destination. 447 o When an OMNI interface sends a packet toward a final destination 448 via an INET interface, it sends packets no larger than 1280 bytes 449 without SPAN encapsulation if the destination is reached via an 450 INET address within the same SPAN segment. Otherwise, it 451 encapsulates the packet in a SPAN header with source address set 452 to the node's SPAN address and destination set to the SPAN address 453 of the next hop OMNI node toward the final destination. The OMNI 454 interface then uses IPv6 fragmentation to break the encapsulated 455 packet into a minimum number of non-overlapping fragments, where 456 the largest fragment size is 1280 bytes and the smallest fragment 457 is no smaller than 640 bytes. The OMNI interface then sends the 458 fragments to the SPAN destination, which reassembles before 459 forwarding toward the final destination. 461 In order to avoid a "tiny fragment" attack, OMNI interfaces 462 unconditionally drop all SPAN fragments smaller than 640 bytes. In 463 order to set the correct context for reassembly, the OMNI interface 464 that inserts a SPAN header MUST also be the one that inserts the IPv6 465 Fragment Header Identification value. Although all fragmnets of the 466 same fragmented SPAN packet are typically sent via the same 467 underlying interface, this is not strictly required since all 468 fragments will arrive at the OMNI interface that performs reassembly 469 even if they travel over different paths. 471 Note that the OMNI interface can forward large packets via 472 encapsulation and fragmentation while at the same time returning 473 advisory PTB messages, e.g., subject to rate limiting. The receiving 474 node that performs reassembly can also send advisory PTB messages if 475 reassembly conditions become unfavorable. The AERO interface can 476 therefore continuously forward large packets without loss while 477 returning advisory messages recommending a smaller size. Advisory 478 PTB messages are differentiated from PTB messages that report loss by 479 setting the Code field in the ICMPv6 message header to the value 1. 480 This document therefore updates [RFC4443] and [RFC8201]. 482 6. Frame Format 484 The OMNI interface transmits IPv6 packets according to the native 485 frame format of each underlying interface. For example, for 486 Ethernet-compatible interfaces the frame format is specified in 487 [RFC2464], for aeronautical radio interfaces the frame format is 488 specified in standards such as ICAO Doc 9776 (VDL Mode 2 Technical 489 Manual), for tunnels over IPv6 the frame format is specified in 490 [RFC2473], etc. 492 7. Link-Local Addresses 494 OMNI interfaces assign IPv6 Link-Local Addresses (i.e., "OMNI LLAs") 495 using the following constructs: 497 o IPv6 MN OMNI LLAs encode the most-significant 112 bits of a MNP 498 within the least-significant 112 bits of the the IPv6 link-local 499 prefix fe80::/16. For example, for the MNP 500 2001:db8:1000:2000::/56 the corresponding LLA is 501 fe80:2001:db8:1000:2000::. See: [RFC4291], Section 2.5.6) for a 502 discussion of IPv6 link-local addresses. 504 o IPv4-compatible MN OMNI LLAs are assigned as fe80::ffff:[v4addr], 505 i.e., the most significant 16 bits of the prefix fe80::/16, 506 followed by 64 '0' bits, followed by 16 '1' bits, followed by a 507 32bit IPv4 address. For example, the IPv4-Compatible MN OMNI LLA 508 for 192.0.2.1 is fe80::ffff:192.0.2.1 (also written as 509 fe80::ffff:c000:0201). 511 o MS OMNI LLAs are assigned to ARs and MSEs from the range 512 fe80::/96, and MUST be managed for uniqueness. The lower 32 bits 513 of the LLA includes a unique integer "MSID" value between 514 0x00000001 and 0xfeffffff, e.g., as in fe80::1, fe80::2, fe80::3, 515 etc., fe80::feff:ffff. The MSID 0x00000000 corresponds to the 516 link-local Subnet-Router anycast address (fe80::) [RFC4291]. The 517 MSID range 0xff000000 through 0xffffffff is reserved for future 518 use. 520 o The OMNI LLA range fe80::/32 is used as the Teredo service prefix 521 for OMNI interfaces according to the format in Section 4 of 522 [RFC4380] (see Section 17 for further discussion). 524 Since the prefix 0000::/8 is "Reserved by the IETF" [RFC4291], no 525 MNPs can be allocated from that block ensuring that there is no 526 possibility for overlap between the above OMNI LLA constructs. 528 Since MN OMNI LLAs are based on the distribution of administratively 529 assured unique MNPs, and since MS OMNI LLAs are guaranteed unique 530 through administrative assignment, OMNI interfaces set the 531 autoconfiguration variable DupAddrDetectTransmits to 0 [RFC4862]. 533 8. The SPAN 535 OMNI links employ an overlay network instance called "The SPAN" 536 (Spanning Partitioned Administrative Networks) that supports 537 forwarding of encapsulated link-scoped messages over an IPv6 overlay 538 routing instance that spans the entire link without decrementing the 539 (link-local) Hop Limit. The OMNI link reserves the Unique Local 540 Address (ULA) prefix fd80::/16 [RFC4193] used for mapping OMNI LLAs 541 to routable SPAN addresses. 543 SPAN addresses are configured in one-to-one correspondence with MN/MS 544 OMNI LLAs by simply rewriting the first 16 bits of the LLA. For 545 example: 547 o the SPAN address corresponding to fe80:2001:db8:1:2:: is simply 548 fd80:2001:db8:1:2:: 550 o the SPAN address corresponding to fe80::ffff:192.0.2.1 is simply 551 fd80::ffff:192.0.2.1 553 o the SPAN address corresponding to fe80::1000 is simply fd80::1000 555 The SPAN address presents an IPv6 address format that is routable 556 within the OMNI link routing system and can be used to convey link- 557 scoped messages across multiple hops using IPv6 encapsulation 558 [RFC2473]. The SPAN extends over the entire OMNI link to include all 559 ARs and MSEs. All MNs are also consideed to be "on the SPAN", 560 however SPAN encapsulation is omitted over ANET links when possible 561 to conserve bandwidth (see: Section 11). 563 The SPAN allows the OMNI link to be subdivided into "segments" that 564 often correspond to administrative domains. OMNI nodes can use IPv6 565 Segment Routing [RFC8402] when necessary to support efficient packet 566 forwarding to destinations located in other SPAN segments. A full 567 discussion of Segment Routing over the SPAN appears in 568 [I-D.templin-intarea-6706bis]. 570 9. Address Mapping - Unicast 572 OMNI interfaces maintain a neighbor cache for tracking per-neighbor 573 state and use the link-local address format specified in Section 7. 574 IPv6 Neighbor Discovery (ND) [RFC4861] messages on MN OMNI interfaces 575 observe the native Source/Target Link-Layer Address Option (S/TLLAO) 576 formats of the underlying interfaces (e.g., for Ethernet the S/TLLAO 577 is specified in [RFC2464]). 579 MNs such as aircraft typically have many wireless data link types 580 (e.g. satellite-based, cellular, terrestrial, air-to-air directional, 581 etc.) with diverse performance, cost and availability properties. 582 The OMNI interface would therefore appear to have multiple L2 583 connections, and may include information for multiple underlying 584 interfaces in a single IPv6 ND message exchange. 586 OMNI interfaces use an IPv6 ND option called the "OMNI option" 587 formatted as shown in Figure 3: 589 0 1 2 3 590 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 591 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 592 | Type | Length | Prefix Length |R| Reserved | 593 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 594 | | 595 ~ Sub-Options ~ 596 | | 597 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 599 Figure 3: OMNI Option Format 601 In this format: 603 o Type is set to TBD. 605 o Length is set to the number of 8 octet blocks in the option. 607 o Prefix Length is set according to the IPv6 source address type. 608 For MN OMNI LLAs, the value is set to the length of the embedded 609 MNP. For IPv4-compatible MN OMNI LLAs, the value is set to 96 610 plus the length of the embedded IPv4 prefix. For MS OMNI LLAs, 611 the value is set to 128. 613 o R (the "Register/Release" bit) is set to 1/0 to request the 614 message recipient to register/release a MN's MNP. The OMNI option 615 may additionally include MSIDs for the recipient to contact to 616 also register/release the MNP. 618 o Reserved is set to the value '0' on transmission and ignored on 619 reception. 621 o Sub-Options is a Variable-length field, of length such that the 622 complete OMNI Option is an integer multiple of 8 octets long. 623 Contains one or more options, as described in Section 8.1. 625 9.1. Sub-Options 627 The OMNI option includes zero or more Sub-Options, some of which may 628 appear multiple times in the same message. Each consecutive Sub- 629 Option is concatenated immediately after its predecessor. All Sub- 630 Options except Pad1 (see below) are type-length-value (TLV) encoded 631 in the following format: 633 0 1 2 634 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 635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 636 | Sub-Type | Sub-length | Sub-Option Data ... 637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 639 Figure 4: Sub-Option Format 641 o Sub-Type is a 1-byte field that encodes the Sub-Option type. Sub- 642 Options defined in this document are: 644 Option Name Sub-Type 645 Pad1 0 646 PadN 1 647 ifIndex-tuple (Type 1) 2 648 ifIndex-tuple (Type 2) 3 649 MS-Register 4 650 MS-Release 5 652 Figure 5 654 Sub-Types 253 and 254 are reserved for experimentation, as 655 recommended in[RFC3692]]. 657 o Sub-Length is a 1-byte field that encodes the length of the Sub- 658 Option Data, in bytes 660 o Sub-Option Data is a byte string with format determined by Sub- 661 Type 663 During processing, unrecognized Sub-Options are ignored and the next 664 Sub-Option processed until the end of the OMNI option. 666 The following Sub-Option types and formats are defined in this 667 document: 669 9.1.1. Pad1 671 0 672 0 1 2 3 4 5 6 7 673 +-+-+-+-+-+-+-+-+ 674 | Sub-Type=0 | 675 +-+-+-+-+-+-+-+-+ 677 Figure 6: Pad1 679 o Sub-Type is set to 0. 681 o No Sub-Length or Sub-Option Data follows (i.e., the "Sub-Option" 682 consists of a single zero octet). 684 9.1.2. PadN 686 0 1 2 687 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 688 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 689 | Sub-Type=1 |Sub-length=N-2 | N-2 padding bytes ... 690 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 692 Figure 7: PadN 694 o Sub-Type is set to 1. 696 o Sub-Length is set to N-2 being the number of padding bytes that 697 follow. 699 o Sub-Option Data consists of N-2 zero-valued octets. 701 9.1.3. ifIndex-tuple (Type 1) 703 0 1 2 3 704 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 705 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 706 | Sub-Type=2 | Sub-length=4+N| ifIndex | ifType | 707 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 708 | Provider ID | Link |S|I|RSV| Bitmap(0)=0xff|P00|P01|P02|P03| 709 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 710 |P04|P05|P06|P07|P08|P09|P10|P11|P12|P13|P14|P15|P16|P17|P18|P19| 711 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 712 |P20|P21|P22|P23|P24|P25|P26|P27|P28|P29|P30|P31| Bitmap(1)=0xff| 713 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 714 |P32|P33|P34|P35|P36|P37|P38|P39| ... 715 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 717 Figure 8: ifIndex-tuple (Type 1) 719 o Sub-Type is set to 2. 721 o Sub-Length is set to 4+N (the number of Sub-Option Data bytes that 722 follow). 724 o Sub-Option Data contains an "ifIndex-tuple" (Type 1) encoded as 725 follows (note that the first four bytes must be present): 727 * ifIndex is set to an 8-bit integer value corresponding to a 728 specific underlying interface. OMNI options MAY include 729 multiple ifIndex-tuples, and MUST number each with an ifIndex 730 value between '1' and '255' that represents a MN-specific 8-bit 731 mapping for the actual ifIndex value assigned to the underlying 732 interface by network management [RFC2863] (the ifIndex value 733 '0' is reserved for use by the MS). Multiple ifIndex-tuples 734 with the same ifIndex value MAY appear in the same OMNI option. 736 * ifType is set to an 8-bit integer value corresponding to the 737 underlying interface identified by ifIndex. The value 738 represents an OMNI interface-specific 8-bit mapping for the 739 actual IANA ifType value registered in the 'IANAifType-MIB' 740 registry [http://www.iana.org]. 742 * Provider ID is set to an OMNI interface-specific 8-bit ID value 743 for the network service provider associated with this ifIndex. 745 * Link encodes a 4-bit link metric. The value '0' means the link 746 is DOWN, and the remaining values mean the link is UP with 747 metric ranging from '1' ("lowest") to '15' ("highest"). 749 * S is set to '1' if this ifIndex-tuple corresponds to the 750 underlying interface that is the source of the ND message. Set 751 to '0' otherwise. 753 * I is set to '0' ("Simplex") if the index for each singleton 754 Bitmap byte in the Sub-Option Data is inferred from its 755 sequential position (i.e., 0, 1, 2, ...), or set to '1' 756 ("Indexed") if each Bitmap is preceded by an Index byte. 757 Figure 8 shows the simplex case for I set to '0'. For I set to 758 '1', each Bitmap is instead preceded by an Index byte that 759 encodes a value "i" = (0 - 255) as the index for its companion 760 Bitmap as follows: 762 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 763 | Index=i | Bitmap(i) |P[*] values ... 764 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 766 Figure 9 768 * RSV is set to the value 0 on transmission and ignored on 769 reception. 771 * The remainder of the Sub-Option Data contains N = (0 - 251) 772 bytes of traffic classifier preferences consisting of a first 773 (indexed) Bitmap (i.e., "Bitmap(i)") followed by 0-8 1-byte 774 blocks of 2-bit P[*] values, followed by a second Bitmap (i), 775 followed by 0-8 blocks of P[*] values, etc. Reading from bit 0 776 to bit 7, the bits of each Bitmap(i) that are set to '1'' 777 indicate the P[*] blocks from the range P[(i*32)] through 778 P[(i*32) + 31] that follow; if any Bitmap(i) bits are '0', then 779 the corresponding P[*] block is instead omitted. For example, 780 if Bitmap(0) contains 0xff then the block with P[00]-P[03], 781 followed by the block with P[04]-P[07], etc., and ending with 782 the block with P[28]-P[31] are included (as showin in 783 Figure 8). The next Bitmap(i) is then consulted with its bits 784 indicating which P[*] blocks follow, etc. out to the end of the 785 Sub-Option. The first 16 P[*] blocks correspond to the 64 786 Differentiated Service Code Point (DSCP) values P[00] - P[63] 787 [RFC2474]. If additional P[*] blocks follow, their values 788 correspond to "pseudo-DSCP" traffic classifier values P[64], 789 P[65], P[66], etc. See Appendix A for further discussion and 790 examples. 792 * Each 2-bit P[*] field is set to the value '0' ("disabled"), '1' 793 ("low"), '2' ("medium") or '3' ("high") to indicate a QoS 794 preference level for underlying interface selection purposes. 795 Not all P[*] values need to be included in all OMNI option 796 instances of a given ifIndex-tuple. Any P[*] values 797 represented in an earlier OMNI option but ommitted in the 798 current OMNI option remain unchanged. Any P[*] values not yet 799 represented in any OMNI option default to "medium". 801 9.1.4. ifIndex-tuple (Type 2) 803 0 1 2 3 804 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 805 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 806 | Sub-Type=3 | Sub-length=4+N| ifIndex | ifType | 807 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 808 | Provider ID | Link |S|Resvd| ~ 809 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ 810 ~ ~ 811 ~ RFC 6088 Format Traffic Selector ~ 812 ~ ~ 813 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 815 Figure 10: ifIndex-tuple (Type 2) 817 o Sub-Type is set to 3. 819 o Sub-Length is set to 4+N (the number of Sub-Option Data bytes that 820 follow). 822 o Sub-Option Data contains an "ifIndex-tuple" (Type 2) encoded as 823 follows (note that the first four bytes must be present): 825 * ifIndex, ifType, Provider ID, Link and S are set exactly as for 826 Type 1 ifIndex-tuples as specified in Section 9.1.3. 828 * the remainder of the Sub-Option body encodes a variable-length 829 traffic selector formatted per [RFC6088], beginning with the 830 "TS Format" field. 832 9.1.5. MS-Register 834 0 1 2 3 835 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 836 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 837 | Sub-Type=4 | Sub-length=4 | MSID (bits 0 - 15) | 838 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 839 | MSID (bits 16 - 32) | 840 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 842 Figure 11: MS-Register Sub-option 844 o Sub-Type is set to 4. 846 o Sub-Length is set to 4. 848 o MSID contains the 32 bit ID of an MSE or AR, in network byte 849 order. OMNI options contain zero or more MS-Register sub-options. 851 9.1.6. MS-Release 853 0 1 2 3 854 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 855 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 856 | Sub-Type=5 | Sub-length=4 | MSID (bits 0 - 15) | 857 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 858 | MSID (bits 16 - 32) | 859 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 861 Figure 12: MS-Release Sub-option 863 o Sub-Type is set to 5. 865 o Sub-Length is set to 4. 867 o MSIID contains the 32 bit ID of an MS or AR, in network byte 868 order. OMNI options contain zero or more MS-Release sub-options. 870 10. Address Mapping - Multicast 872 The multicast address mapping of the native underlying interface 873 applies. The mobile router on board the aircraft also serves as an 874 IGMP/MLD Proxy for its EUNs and/or hosted applications per [RFC4605] 875 while using the L2 address of the router as the L2 address for all 876 multicast packets. 878 11. Conceptual Sending Algorithm 880 The MN's IPv6 layer selects the outbound OMNI interface according to 881 standard IPv6 requirements when forwarding data packets from local or 882 EUN applications to external correspondents. The OMNI interface 883 maintains a neighbor cache the same as for any IPv6 interface, but 884 with additional state for multilink coordination. 886 After a packet enters the OMNI interface, an outbound underlying 887 interface is selected based on multilink parameters such as DSCP, 888 application port number, cost, performance, message size, etc. OMNI 889 interface multilink selections could also be configured to perform 890 replication across multiple underlying interfaces for increased 891 reliability at the expense of packet duplication. 893 When an OMNI interface sends a packet over a selected outbound 894 underlying interface, it omits SPAN encapsulation if the packet does 895 not require fragmentation and the neighbor can determine the SPAN 896 addresses through other means (e.g., the packet's OMNI LLAs, neighbor 897 cache information, etc.). Otherwise, the OMNI interface inserts a 898 SPAN header and performs fragmentation if necessary. 900 OMNI interface multilink service designers MUST observe the BCP 901 guidance in Section 15 [RFC3819] in terms of implications for 902 reordering when packets from the same flow may be spread across 903 multiple underlying interfaces having diverse properties. 905 11.1. Multiple OMNI Interfaces 907 MNs may associate with multiple MS instances concurrently. Each MS 908 instance represents a distinct OMNI link distinguished by its 909 associated MSPs. The MN configures a separate OMNI interface for 910 each link so that multiple interfaces (e.g., omni0, omni1, omni2, 911 etc.) are exposed to the IPv6 layer. 913 Depending on local policy and configuration, an MN may choose between 914 alternative active OMNI interfaces using a packet's DSCP, routing 915 information or static configuration. Interface selection based on 916 per-packet source addresses is also enabled when the MSPs for each 917 OMNI interface are known (e.g., discovered through Prefix Information 918 Options (PIOs) and/or Route Information Options (RIOs)). 920 Each OMNI interface can be configured over the same or different sets 921 of underlying interfaces. Each ANET distinguishes between the 922 different OMNI links based on the MSPs represented in per-packet IPv6 923 addresses. 925 Multiple distinct OMNI links can therefore be used to support fault 926 tolerance, load balancing, reliability, etc. The architectural model 927 parallels Layer 2 Virtual Local Area Networks (VLANs), where the MSPs 928 serve as (virtual) VLAN tags. 930 12. Router Discovery and Prefix Registration 932 MNs interface with the MS by sending RS messages with OMNI options 933 under the assumption that a single AR on the ANET will proocess the 934 message and respond. This places a requirement on each ANET, which 935 may be enforced by physical/logical partitioning, L2 AR beaconing, 936 etc. The manner in which the ANET ensures single AR coordination is 937 link-specific and outside the scope of this document. 939 For each underlying interface, the MN sends an RS message with an 940 OMNI option with prefix registration information, ifIndex-tuples, MS- 941 Register/Release suboptions containing MSIDs, and with destination 942 address set to All-Routers multicast (ff02::2) [RFC4291]. Example 943 MSID discovery methods are given in [RFC5214], including data link 944 login parameters, name service lookups, static configuration, etc. 945 Alternatively, MNs can discover indiviual MSIDs by sending an initial 946 RS with MS-Register MSID set to 0x00000000. 948 MNs configure OMNI interfaces that observe the properties discussed 949 in the previous section. The OMNI interface and its underlying 950 interfaces are said to be in either the "UP" or "DOWN" state 951 according to administrative actions in conjunction with the interface 952 connectivity status. An OMNI interface transitions to UP or DOWN 953 through administrative action and/or through state transitions of the 954 underlying interfaces. When a first underlying interface transitions 955 to UP, the OMNI interface also transitions to UP. When all 956 underlying interfaces transition to DOWN, the OMNI interface also 957 transitions to DOWN. 959 When an OMNI interface transitions to UP, the MN sends RS messages to 960 register its MNP and an initial set of underlying interfaces that are 961 also UP. The MN sends additional RS messages to refresh lifetimes 962 and to register/deregister underlying interfaces as they transition 963 to UP or DOWN. The MN sends initial RS messages over an UP 964 underlying interface with its OMNI LLA as the source and with 965 destination set to All-Routers multicast. The RS messages include an 966 OMNI option per Section 9 with valid prefix registration information, 967 ifIndex-tuples appropriate for underlying interfaces and MS-Register/ 968 Release sub-options. 970 ARs process IPv6 ND messages with OMNI options and act as a proxy for 971 MSEs. ARs receive RS messages and create a neighbor cache entry for 972 the MN, then coordinate with any named MSIDs in a manner outside the 973 scope of this document. The AR returns an RA message with 974 destination address set to the MN OMNI LLA (i.e., unicast), with 975 source address set to its MS OMNI LLA, with the P(roxy) bit set in 976 the RA flags [RFC4389], with an OMNI option with valid prefix 977 registration information, ifIndex-tuples, MS-Register/Release sub- 978 options, and with any information for the link that would normally be 979 delivered in a solicited RA message. ARs return RA messages with 980 configuration information in response to a MN's RS messages. The AR 981 sets the RA Cur Hop Limit, M and O flags, Router Lifetime, Reachable 982 Time and Retrans Timer values, and includes any necessary options 983 such as: 985 o PIOs with (A; L=0) that include MSPs for the link [RFC8028]. 987 o RIOs [RFC4191] with more-specific routes. 989 o an MTU option that specifies the maximum acceptable packet size 990 for this ANET interface. 992 The AR coordinates with each Register/Release MSID then sends an 993 immediate unicast RA response without delay; therefore, the IPv6 ND 994 MAX_RA_DELAY_TIME and MIN_DELAY_BETWEEN_RAS constants for multicast 995 RAs do not apply. The AR MAY send periodic and/or event-driven 996 unsolicited RA messages according to the standard [RFC4861]. 998 When the MSE processes the OMNI information, it first validates the 999 prefix registration information. The MSE then injects/withdraws the 1000 MNP in the routing/mapping system and caches/discards the new Prefix 1001 Length, MNP and ifIndex-tuples. The MSE then informs the AR of 1002 registration success/failure, and the AR adds the MSE to the list of 1003 Register/Release MSIDs to return in an RA message OMNI option per 1004 Section 9. 1006 When the MN receives the RA message, it creates an OMNI interface 1007 neighbor cache entry with the AR's address as an L2 address and 1008 records the MSIDs that have confirmed MNP registration via this AR. 1009 If the MN connects to multiple ANETs, it establishes additional AR L2 1010 addresses (i.e., as a Multilink neighbor). The MN then manages its 1011 underlying interfaces according to their states as follows: 1013 o When an underlying interface transitions to UP, the MN sends an RS 1014 over the underlying interface with an OMNI option with R set to 1. 1015 The OMNI option contains at least one ifIndex-tuple with values 1016 specific to this underlying interface, and may contain additional 1017 ifIndex-tuples specific to this and/or other underlying 1018 interfaces. The option also includes any Register/Release MSIDs. 1020 o When an underlying interface transitions to DOWN, the MN sends an 1021 RS or unsolicited NA message over any UP underlying interface with 1022 an OMNI option containing an ifIndex-tuple for the DOWN underlying 1023 interface with Link set to '0'. The MN sends an RS when an 1024 acknowledgement is required, or an unsolicited NA when reliability 1025 is not thought to be a concern (e.g., if redundant transmissions 1026 are sent on multiple underlying interfaces). 1028 o When the Router Lifetime for a specific AR nears expiration, the 1029 MN sends an RS over the underlying interface to receive a fresh 1030 RA. If no RA is received, the MN marks the underlying interface 1031 as DOWN. 1033 o When a MN wishes to release from one or more current MSIDs, it 1034 sends an RS or unsolicited NA message over any UP underlying 1035 interfaces with an OMNI option with a Release MSID. Each MSID 1036 then withdraws the MNP from the routing/mapping system and informs 1037 the AR that the release was successful. 1039 o When all of a MNs underlying interfaces have transitioned to DOWN 1040 (or if the prefix registration lifetime expires), any associated 1041 MSEs withdraw the MNP the same as if they had received a message 1042 with a release indication. 1044 The MN is responsible for retrying each RS exchange up to 1045 MAX_RTR_SOLICITATIONS times separated by RTR_SOLICITATION_INTERVAL 1046 seconds until an RA is received. If no RA is received over a an UP 1047 underlying interface, the MN declares this underlying interface as 1048 DOWN. 1050 The IPv6 layer sees the OMNI interface as an ordinary IPv6 interface. 1051 Therefore, when the IPv6 layer sends an RS message the OMNI interface 1052 returns an internally-generated RA message as though the message 1053 originated from an IPv6 router. The internally-generated RA message 1054 contains configuration information that is consistent with the 1055 information received from the RAs generated by the MS. Whether the 1056 OMNI interface IPv6 ND messaging process is initiated from the 1057 receipt of an RS message from the IPv6 layer is an implementation 1058 matter. Some implementations may elect to defer the IPv6 ND 1059 messaging process until an RS is received from the IPv6 layer, while 1060 others may elect to initiate the process proactively. 1062 Note: The Router Lifetime value in RA messages indicates the time 1063 before which the MN must send another RS message over this underlying 1064 interface (e.g., 600 seconds), however that timescale may be 1065 significantly longer than the lifetime the MS has committed to retain 1066 the prefix registration (e.g., REACHABLETIME seconds). ARs are 1067 therefore responsible for keeping MS state alive on a shorter 1068 timescale than the MN is required to do on its own behalf. 1070 13. Secure Redirection 1072 If the ANET link model is multiple access, the AR is responsible for 1073 assuring that address duplication cannot corrupt the neighbor caches 1074 of other nodes on the link. When the MN sends an RS message on a 1075 multiple access ANET link, the AR verifys that the MN is authorized 1076 to use the address and returns an RA with a non-zero Router Lifetime 1077 only if the MN is authorized. 1079 After verifying MN authorization and returning an RA, the AR MAY 1080 return IPv6 ND Redirect messages to direct MNs located on the same 1081 ANET link to exchange packets directly without transiting the AR. In 1082 that case, the MNs can exchange packets according to their unicast L2 1083 addresses discovered from the Redirect message instead of using the 1084 dogleg path through the AR. In some ANET links, however, such direct 1085 communications may be undesirable and continued use of the dogleg 1086 path through the AR may provide better performance. In that case, 1087 the AR can refrain from sending Redirects, and/or MNs can ignore 1088 them. 1090 14. AR and MSE Resilience 1092 ANETs SHOULD deploy ARs in Virtual Router Redundancy Protocol (VRRP) 1093 [RFC5798] configurations so that service continuity is maintained 1094 even if one or more ARs fail. Using VRRP, the MN is unaware which of 1095 the (redundant) ARs is currently providing service, and any service 1096 discontinuity will be limited to the failover time supported by VRRP. 1097 Widely deployed public domain implementations of VRRP are available. 1099 MSEs SHOULD use high availability clustering services so that 1100 multiple redundant systems can provide coordinated response to 1101 failures. As with VRRP, widely deployed public domain 1102 implementations of high availability clustering services are 1103 available. Note that special-purpose and expensive dedicated 1104 hardware is not necessary, and public domain implementations can be 1105 used even between lightweight virtual machines in cloud deployments. 1107 15. Detecting and Responding to MSE Failures 1109 In environments where fast recovery from MSE failure is required, ARs 1110 SHOULD use proactive Neighbor Unreachability Detection (NUD) in a 1111 manner that parallels Bidirectional Forwarding Detection (BFD) 1112 [RFC5880] to track MSE reachability. ARs can then quickly detect and 1113 react to failures so that cached information is re-established 1114 through alternate paths. Proactive NUD control messaging is carried 1115 only over well-connected ground domain networks (i.e., and not low- 1116 end ANET links such as aeronautical radios) and can therefore be 1117 tuned for rapid response. 1119 ARs perform proactive NUD for MSEs for which there are currently 1120 active MNs on the ANET. If an MSE fails, ARs can quickly inform MNs 1121 of the outage by sending multicast RA messages on the ANET interface. 1122 The AR sends RA messages to the MN via the ANET interface with an 1123 OMNI option with a Release ID for the failed MSE, and with 1124 destination address set to All-Nodes multicast (ff02::1) [RFC4291]. 1126 The AR SHOULD send MAX_FINAL_RTR_ADVERTISEMENTS RA messages separated 1127 by small delays [RFC4861]. Any MNs on the ANET interface that have 1128 been using the (now defunct) MSE will receive the RA messages and 1129 associate with a new MSE. 1131 16. Transition Considerations 1133 When a MN connects to an ANET link for the first time, it sends an RS 1134 message with an OMNI option. If the first hop AR recognizes the 1135 option, it returns an RA with its MS OMNI LLA as the source, the MN 1136 OMNI LLA as the destination, the P(roxy) bit set in the RA flags and 1137 with an OMNI option included. The MN then engages the AR according 1138 to the OMNI link model specified above. If the first hop AR is a 1139 legacy IPv6 router, however, it instead returns an RA message with no 1140 OMNI option and with a non-OMNI unicast source LLA as specified in 1141 [RFC4861]. In that case, the MN engages the ANET according to the 1142 legacy IPv6 link model and without the OMNI extensions specified in 1143 this document. 1145 If the ANET link model is multiple access, there must be assurance 1146 that address duplication cannot corrupt the neighbor caches of other 1147 nodes on the link. When the MN sends an RS message on a multiple 1148 access ANET link with an OMNI LLA source address and an OMNI option, 1149 ARs that recognize the option ensure that the MN is authorized to use 1150 the address and return an RA with a non-zero Router Lifetime only if 1151 the MN is authorized. ARs that do not recognize the option instead 1152 return an RA that makes no statement about the MN's authorization to 1153 use the source address. In that case, the MN should perform 1154 Duplicate Address Detection to ensure that it does not interfere with 1155 other nodes on the link. 1157 An alternative approach for multiple access ANET links to ensure 1158 isolation for MN / AR communications is through L2 address mappings 1159 as discussed in Appendix C. This arrangement imparts a (virtual) 1160 point-to-point link model over the (physical) multiple access link. 1162 17. OMNI Interfaces on the Open Internet 1164 OMNI interfaces that connect to the open Internet via INET interfaces 1165 can apply symmetric security services such as VPNs to establish 1166 secured tunnels to MSEs. In environments where an explicit VPN may 1167 be too restrictive, OMNI interfaces can instead ensure neighbor cache 1168 integrity using SEcure Neighbor Discovery (SEND) [RFC3971] and 1169 Cryptographically Generated Addresses (CGAs) [RFC3972]. 1171 When SEND/CGA are used, the IPv6 ND control plane messages used to 1172 establish neighbor cache state are authenticated while data plane 1173 messages are delivered the same as for ordinary best-effort Internet 1174 traffic. Instead, data plane communications via OMNI interfaces that 1175 connect over the open Internet without an explicit VPN must emply 1176 transport- or higher-layer security to ensure integrity and/or 1177 confidentiality. 1179 In addition to secured OMNI interface RS/RA exchanges, SEND/CGA 1180 supports safe address resolution and neighbor unreachability 1181 detection as discused in Asymmetric Extended Route Optimization 1182 (AERO) [I-D.templin-intarea-6706bis]. This allows for efficient 1183 multilink operations over the open Internet with assured neighbor 1184 cache integrity. 1186 OMNI interfaces in the open Internet are often located behind Network 1187 Address Translators (NATs). The OMNI interface accommodates NAT 1188 traversal using the OMNI LLA prefix fe80::/32 for Teredo IPv6 1189 addresses formatted as discussed in Section 4 of [RFC4380]. Further 1190 specifications for NAT traversal are discussed in 1191 [I-D.templin-intarea-6706bis][RFC6081][RFC4380]. 1193 18. Time-Varying MNPs 1195 In some use cases, it is desireable, beneficial and efficient for the 1196 MN to receive a contstant MNP that travels with the MN wherever it 1197 moves. For example, this would allow air traffic controllers to 1198 easily track aircraft, etc. In other cases, however (e.g., 1199 intelligent transportation systems), the MN may be willing to 1200 sacrifice a modicum of efficiency in order to have time-varying MNPs 1201 that can be changed every so often to defeat adversarial tracking. 1203 Prefix delegation services such as those discussed in 1204 [I-D.templin-6man-dhcpv6-ndopt] and [I-D.templin-intarea-6706bis] 1205 allow OMNI MNs that desire time-varying MNPs to obtain short-lived 1206 prefixes. In that case, the identity of the MN would not be bound to 1207 the MNP but rather to the prefix delegation ID and used as the seed 1208 for Prefix Delegation. The MN would then be obligated to renumber 1209 its internal networks whenever its MNP (and therefore also its OMNI 1210 address) changes. This should not present a challenge for MNs with 1211 automated network renumbering services, however presents limits for 1212 the durations of ongoing sessions that would prefer to use a constant 1213 address. 1215 19. IANA Considerations 1217 The IANA is instructed to allocate an official Type number TBD from 1218 the registry "IPv6 Neighbor Discovery Option Formats" for the OMNI 1219 option. Implementations set Type to 253 as an interim value 1220 [RFC4727]. 1222 The IANA is instructed to allocate one Ethernet unicast address TBD2 1223 (suggest 00-00-5E-00-52-14 [RFC5214]) in the registry "IANA Ethernet 1224 Address Block - Unicast Use". 1226 The OMNI option also defines an 8-bit Sub-Type field, for which IANA 1227 is instructed to create and maintain a new registry entitled "OMNI 1228 option Sub-Type values". Initial values for the OMNI option Sub-Type 1229 values registry are given below; future assignments are to be made 1230 through Expert Review [RFC8126]. 1232 Value Sub-Type name Reference 1233 ----- ------------- ---------- 1234 0 Pad1 [RFCXXXX] 1235 1 PadN [RFCXXXX] 1236 2 ifIndex-tuple (Type 1) [RFCXXXX] 1237 3 ifIndex-tuple (Type 2) [RFCXXXX] 1238 4 MS-Register [RFCXXXX] 1239 5 MS-Release [RFCXXXX] 1240 6-252 Unassigned 1241 253-254 Experimental [RFCXXXX] 1242 255 Reserved [RFCXXXX] 1244 Figure 13: OMNI Option Sub-Type Values 1246 20. Security Considerations 1248 Security considerations for IPv6 [RFC8200] and IPv6 Neighbor 1249 Discovery [RFC4861] apply. OMNI interface IPv6 ND messages SHOULD 1250 include Nonce and Timestamp options [RFC3971] when synchronized 1251 transaction confirmation is needed. 1253 OMNI interfaces configured over secured underlying ANET interfaces 1254 inherit the physical and/or link-layer security aspects of the 1255 connected ANETs. OMNI interfaces configured over open Internet 1256 interfaces must use symmetric securing services such as VPNs or 1257 asymmetric services such as SEND/CGA [RFC3971][RFC3972]. 1259 Security considerations for specific access network interface types 1260 are covered under the corresponding IP-over-(foo) specification 1261 (e.g., [RFC2464], [RFC2492], etc.). 1263 21. Acknowledgements 1265 The first version of this document was prepared per the consensus 1266 decision at the 7th Conference of the International Civil Aviation 1267 Organization (ICAO) Working Group-I Mobility Subgroup on March 22, 1268 2019. Consensus to take the document forward to the IETF was reached 1269 at the 9th Conference of the Mobility Subgroup on November 22, 2019. 1270 Attendees and contributors included: Guray Acar, Danny Bharj, 1271 Francois D'Humieres, Pavel Drasil, Nikos Fistas, Giovanni Garofolo, 1272 Bernhard Haindl, Vaughn Maiolla, Tom McParland, Victor Moreno, Madhu 1273 Niraula, Brent Phillips, Liviu Popescu, Jacky Pouzet, Aloke Roy, Greg 1274 Saccone, Robert Segers, Michal Skorepa, Michel Solery, Stephane 1275 Tamalet, Fred Templin, Jean-Marc Vacher, Bela Varkonyi, Tony Whyman, 1276 Fryderyk Wrobel and Dongsong Zeng. 1278 The following individuals are acknowledged for their useful comments: 1279 Michael Matyas, Madhu Niraula, Greg Saccone, Stephane Tamalet, Eric 1280 Vyncke. Pavel Drasil, Zdenek Jaron and Michal Skorepa are recognized 1281 for their many helpful ideas and suggestions. 1283 This work is aligned with the NASA Safe Autonomous Systems Operation 1284 (SASO) program under NASA contract number NNA16BD84C. 1286 This work is aligned with the FAA as per the SE2025 contract number 1287 DTFAWA-15-D-00030. 1289 22. References 1291 22.1. Normative References 1293 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1294 Requirement Levels", BCP 14, RFC 2119, 1295 DOI 10.17487/RFC2119, March 1997, 1296 . 1298 [RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, 1299 "Definition of the Differentiated Services Field (DS 1300 Field) in the IPv4 and IPv6 Headers", RFC 2474, 1301 DOI 10.17487/RFC2474, December 1998, 1302 . 1304 [RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander, 1305 "SEcure Neighbor Discovery (SEND)", RFC 3971, 1306 DOI 10.17487/RFC3971, March 2005, 1307 . 1309 [RFC3972] Aura, T., "Cryptographically Generated Addresses (CGA)", 1310 RFC 3972, DOI 10.17487/RFC3972, March 2005, 1311 . 1313 [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and 1314 More-Specific Routes", RFC 4191, DOI 10.17487/RFC4191, 1315 November 2005, . 1317 [RFC4193] Hinden, R. and B. Haberman, "Unique Local IPv6 Unicast 1318 Addresses", RFC 4193, DOI 10.17487/RFC4193, October 2005, 1319 . 1321 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 1322 Architecture", RFC 4291, DOI 10.17487/RFC4291, February 1323 2006, . 1325 [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet 1326 Control Message Protocol (ICMPv6) for the Internet 1327 Protocol Version 6 (IPv6) Specification", STD 89, 1328 RFC 4443, DOI 10.17487/RFC4443, March 2006, 1329 . 1331 [RFC4727] Fenner, B., "Experimental Values In IPv4, IPv6, ICMPv4, 1332 ICMPv6, UDP, and TCP Headers", RFC 4727, 1333 DOI 10.17487/RFC4727, November 2006, 1334 . 1336 [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, 1337 "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, 1338 DOI 10.17487/RFC4861, September 2007, 1339 . 1341 [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless 1342 Address Autoconfiguration", RFC 4862, 1343 DOI 10.17487/RFC4862, September 2007, 1344 . 1346 [RFC6088] Tsirtsis, G., Giarreta, G., Soliman, H., and N. Montavont, 1347 "Traffic Selectors for Flow Bindings", RFC 6088, 1348 DOI 10.17487/RFC6088, January 2011, 1349 . 1351 [RFC8028] Baker, F. and B. Carpenter, "First-Hop Router Selection by 1352 Hosts in a Multi-Prefix Network", RFC 8028, 1353 DOI 10.17487/RFC8028, November 2016, 1354 . 1356 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 1357 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 1358 May 2017, . 1360 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 1361 (IPv6) Specification", STD 86, RFC 8200, 1362 DOI 10.17487/RFC8200, July 2017, 1363 . 1365 [RFC8201] McCann, J., Deering, S., Mogul, J., and R. Hinden, Ed., 1366 "Path MTU Discovery for IP version 6", STD 87, RFC 8201, 1367 DOI 10.17487/RFC8201, July 2017, 1368 . 1370 22.2. Informative References 1372 [I-D.templin-6man-dhcpv6-ndopt] 1373 Templin, F., "A Unified Stateful/Stateless Configuration 1374 Service for IPv6", draft-templin-6man-dhcpv6-ndopt-09 1375 (work in progress), January 2020. 1377 [I-D.templin-intarea-6706bis] 1378 Templin, F., "Asymmetric Extended Route Optimization 1379 (AERO)", draft-templin-intarea-6706bis-44 (work in 1380 progress), April 2020. 1382 [RFC2225] Laubach, M. and J. Halpern, "Classical IP and ARP over 1383 ATM", RFC 2225, DOI 10.17487/RFC2225, April 1998, 1384 . 1386 [RFC2464] Crawford, M., "Transmission of IPv6 Packets over Ethernet 1387 Networks", RFC 2464, DOI 10.17487/RFC2464, December 1998, 1388 . 1390 [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in 1391 IPv6 Specification", RFC 2473, DOI 10.17487/RFC2473, 1392 December 1998, . 1394 [RFC2492] Armitage, G., Schulter, P., and M. Jork, "IPv6 over ATM 1395 Networks", RFC 2492, DOI 10.17487/RFC2492, January 1999, 1396 . 1398 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1399 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 1400 . 1402 [RFC3692] Narten, T., "Assigning Experimental and Testing Numbers 1403 Considered Useful", BCP 82, RFC 3692, 1404 DOI 10.17487/RFC3692, January 2004, 1405 . 1407 [RFC3819] Karn, P., Ed., Bormann, C., Fairhurst, G., Grossman, D., 1408 Ludwig, R., Mahdavi, J., Montenegro, G., Touch, J., and L. 1409 Wood, "Advice for Internet Subnetwork Designers", BCP 89, 1410 RFC 3819, DOI 10.17487/RFC3819, July 2004, 1411 . 1413 [RFC4380] Huitema, C., "Teredo: Tunneling IPv6 over UDP through 1414 Network Address Translations (NATs)", RFC 4380, 1415 DOI 10.17487/RFC4380, February 2006, 1416 . 1418 [RFC4389] Thaler, D., Talwar, M., and C. Patel, "Neighbor Discovery 1419 Proxies (ND Proxy)", RFC 4389, DOI 10.17487/RFC4389, April 1420 2006, . 1422 [RFC4605] Fenner, B., He, H., Haberman, B., and H. Sandick, 1423 "Internet Group Management Protocol (IGMP) / Multicast 1424 Listener Discovery (MLD)-Based Multicast Forwarding 1425 ("IGMP/MLD Proxying")", RFC 4605, DOI 10.17487/RFC4605, 1426 August 2006, . 1428 [RFC5213] Gundavelli, S., Ed., Leung, K., Devarapalli, V., 1429 Chowdhury, K., and B. Patil, "Proxy Mobile IPv6", 1430 RFC 5213, DOI 10.17487/RFC5213, August 2008, 1431 . 1433 [RFC5214] Templin, F., Gleeson, T., and D. Thaler, "Intra-Site 1434 Automatic Tunnel Addressing Protocol (ISATAP)", RFC 5214, 1435 DOI 10.17487/RFC5214, March 2008, 1436 . 1438 [RFC5798] Nadas, S., Ed., "Virtual Router Redundancy Protocol (VRRP) 1439 Version 3 for IPv4 and IPv6", RFC 5798, 1440 DOI 10.17487/RFC5798, March 2010, 1441 . 1443 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 1444 (BFD)", RFC 5880, DOI 10.17487/RFC5880, June 2010, 1445 . 1447 [RFC6081] Thaler, D., "Teredo Extensions", RFC 6081, 1448 DOI 10.17487/RFC6081, January 2011, 1449 . 1451 [RFC6543] Gundavelli, S., "Reserved IPv6 Interface Identifier for 1452 Proxy Mobile IPv6", RFC 6543, DOI 10.17487/RFC6543, May 1453 2012, . 1455 [RFC7084] Singh, H., Beebee, W., Donley, C., and B. Stark, "Basic 1456 Requirements for IPv6 Customer Edge Routers", RFC 7084, 1457 DOI 10.17487/RFC7084, November 2013, 1458 . 1460 [RFC7421] Carpenter, B., Ed., Chown, T., Gont, F., Jiang, S., 1461 Petrescu, A., and A. Yourtchenko, "Analysis of the 64-bit 1462 Boundary in IPv6 Addressing", RFC 7421, 1463 DOI 10.17487/RFC7421, January 2015, 1464 . 1466 [RFC7847] Melia, T., Ed. and S. Gundavelli, Ed., "Logical-Interface 1467 Support for IP Hosts with Multi-Access Support", RFC 7847, 1468 DOI 10.17487/RFC7847, May 2016, 1469 . 1471 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 1472 Writing an IANA Considerations Section in RFCs", BCP 26, 1473 RFC 8126, DOI 10.17487/RFC8126, June 2017, 1474 . 1476 [RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L., 1477 Decraene, B., Litkowski, S., and R. Shakir, "Segment 1478 Routing Architecture", RFC 8402, DOI 10.17487/RFC8402, 1479 July 2018, . 1481 Appendix A. Type 1 ifIndex-tuple Traffic Classifier Preference Encoding 1483 Adaptation of the OMNI option Type 1 ifIndex-tuple's traffic 1484 classifier Bitmap to specific Internetworks such as the Aeronautical 1485 Telecommunications Network with Internet Protocol Services (ATN/IPS) 1486 may include link selection preferences based on other traffic 1487 classifiers (e.g., transport port numbers, etc.) in addition to the 1488 existing DSCP-based preferences. Nodes on specific Internetworks 1489 maintain a map of traffic classifiers to additional P[*] preference 1490 fields beyond the first 64. For example, TCP port 22 maps to P[67], 1491 TCP port 443 maps to P[70], UDP port 8060 maps to P[76], etc. 1493 Implementations use Simplex or Indexed encoding formats for P[*] 1494 encoding in order to encode a given set of traffic classifiers in the 1495 most efficient way. Some use cases may be more efficiently coded 1496 using Simplex form, while others may be more efficient using Indexed. 1497 Once a format is selected for preparation of a single ifIndex-tuple 1498 the same format must be used for the entire Sub-Option. Different 1499 Sub-Options may use different formats. 1501 The following figures show coding examples for various Simplex and 1502 Indexed formats: 1504 0 1 2 3 1505 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 1506 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1507 | Sub-Type=2 | Sub-length=4+N| ifIndex | ifType | 1508 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1509 | Provider ID | Link |S|0|RSV| Bitmap(0)=0xff|P00|P01|P02|P03| 1510 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1511 |P04|P05|P06|P07|P08|P09|P10|P11|P12|P13|P14|P15|P16|P17|P18|P19| 1512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1513 |P20|P21|P22|P23|P24|P25|P26|P27|P28|P29|P30|P31| Bitmap(1)=0xff| 1514 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1515 |P32|P33|P34|P35|P36|P37|P38|P39|P40|P41|P42|P43|P44|P45|P46|P47| 1516 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1517 |P48|P49|P50|P51|P52|P53|P54|P55|P56|P57|P58|P59|P60|P61|P62|P63| 1518 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1519 | Bitmap(2)=0xff|P64|P65|P67|P68| ... 1520 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 1522 Figure 14: Example 1: Dense Simplex Encoding 1524 0 1 2 3 1525 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 1526 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1527 | Sub-Type=2 | Sub-length=4+N| ifIndex | ifType | 1528 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1529 | Provider ID | Link |S|0|RSV| Bitmap(0)=0x00| Bitmap(1)=0x0f| 1530 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1531 |P48|P49|P50|P51|P52|P53|P54|P55|P56|P57|P58|P59|P60|P61|P62|P63| 1532 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1533 | Bitmap(2)=0x00| Bitmap(3)=0x00| Bitmap(4)=0x00| Bitmap(5)=0x00| 1534 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1535 | Bitmap(6)=0xf0|192|193|194|195|196|197|198|199|200|201|202|203| 1536 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1537 |204|205|206|207| Bitmap(7)=0x00| Bitmap(8)=0x0f|272|273|274|275| 1538 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1539 |276|277|278|279|280|281|282|283|284|285|286|287| Bitmap(9)=0x00| 1540 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1541 |Bitmap(10)=0x00| ... 1542 +-+-+-+-+-+-+-+-+-+-+- 1544 Figure 15: Example 2: Sparse Simplex Encoding 1546 0 1 2 3 1547 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 1548 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1549 | Sub-Type=2 | Sub-length=4+N| ifIndex | ifType | 1550 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1551 | Provider ID | Link |S|1|RSV| Index = 0x00 | Bitmap = 0x80 | 1552 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1553 |P00|P01|P02|P03| Index = 0x01 | Bitmap = 0x01 |P60|P61|P62|P63| 1554 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1555 | Index = 0x10 | Bitmap = 0x80 |512|513|514|515| Index = 0x18 | 1556 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1557 | Bitmap = 0x01 |796|797|798|799| ... 1558 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 1560 Figure 16: Example 3: Indexed Encoding 1562 Appendix B. VDL Mode 2 Considerations 1564 ICAO Doc 9776 is the "Technical Manual for VHF Data Link Mode 2" 1565 (VDLM2) that specifies an essential radio frequency data link service 1566 for aircraft and ground stations in worldwide civil aviation air 1567 traffic management. The VDLM2 link type is "multicast capable" 1568 [RFC4861], but with considerable differences from common multicast 1569 links such as Ethernet and IEEE 802.11. 1571 First, the VDLM2 link data rate is only 31.5Kbps - multiple orders of 1572 magnitude less than most modern wireless networking gear. Second, 1573 due to the low available link bandwidth only VDLM2 ground stations 1574 (i.e., and not aircraft) are permitted to send broadcasts, and even 1575 so only as compact layer 2 "beacons". Third, aircraft employ the 1576 services of ground stations by performing unicast RS/RA exchanges 1577 upon receipt of beacons instead of listening for multicast RA 1578 messages and/or sending multicast RS messages. 1580 This beacon-oriented unicast RS/RA approach is necessary to conserve 1581 the already-scarce available link bandwidth. Moreover, since the 1582 numbers of beaconing ground stations operating within a given spatial 1583 range must be kept as sparse as possible, it would not be feasible to 1584 have different classes of ground stations within the same region 1585 observing different protocols. It is therefore highly desirable that 1586 all ground stations observe a common language of RS/RA as specified 1587 in this document. 1589 Note that links of this nature may benefit from compression 1590 techniques that reduce the bandwidth necessary for conveying the same 1591 amount of data. The IETF lpwan working group is considering possible 1592 alternatives: [https://datatracker.ietf.org/wg/lpwan/documents]. 1594 Appendix C. MN / AR Isolation Through L2 Address Mapping 1596 Per [RFC4861], IPv6 ND messages may be sent to either a multicast or 1597 unicast link-scoped IPv6 destination address. However, IPv6 ND 1598 messaging should be coordinated between the MN and AR only without 1599 invoking other nodes on the ANET. This implies that MN / AR 1600 coordinations should be isolated and not overheard by other nodes on 1601 the link. 1603 To support MN / AR isolation on some ANET links, ARs can maintain an 1604 OMNI-specific unicast L2 address ("MSADDR"). For Ethernet-compatible 1605 ANETs, this specification reserves one Ethernet unicast address TBD2 1606 (see: Section 19). For non-Ethernet statically-addressed ANETs, 1607 MSADDR is reserved per the assigned numbers authority for the ANET 1608 addressing space. For still other ANETs, MSADDR may be dynamically 1609 discovered through other means, e.g., L2 beacons. 1611 MNs map the L3 addresses of all IPv6 ND messages they send (i.e., 1612 both multicast and unicast) to MSADDR instead of to an ordinary 1613 unicast or multicast L2 address. In this way, all of the MN's IPv6 1614 ND messages will be received by ARs that are configured to accept 1615 packets destined to MSADDR. Note that multiple ARs on the link could 1616 be configured to accept packets destined to MSADDR, e.g., as a basis 1617 for supporting redundancy. 1619 Therefore, ARs must accept and process packets destined to MSADDR, 1620 while all other devices must not process packets destined to MSADDR. 1621 This model has well-established operational experience in Proxy 1622 Mobile IPv6 (PMIP) [RFC5213][RFC6543]. 1624 Appendix D. Change Log 1626 << RFC Editor - remove prior to publication >> 1628 Differences from draft-templin-6man-omni-interface-14 to draft- 1629 templin-6man-omni-interface-15: 1631 o Prefix length discussions removed. 1633 Differences from draft-templin-6man-omni-interface-12 to draft- 1634 templin-6man-omni-interface-13: 1636 o Teredo 1638 Differences from draft-templin-6man-omni-interface-11 to draft- 1639 templin-6man-omni-interface-12: 1641 o Major simplifications and clarifications on MTU and fragmentation. 1643 o Document now udates RFC4443 and RFC8201. 1645 Differences from draft-templin-6man-omni-interface-10 to draft- 1646 templin-6man-omni-interface-11: 1648 o Removed /64 assumption, resulting in new OMNI address format. 1650 Differences from draft-templin-6man-omni-interface-07 to draft- 1651 templin-6man-omni-interface-08: 1653 o OMNI MNs in the open Internet 1655 Differences from draft-templin-6man-omni-interface-06 to draft- 1656 templin-6man-omni-interface-07: 1658 o Brought back L2 MSADDR mapping text for MN / AR isolation based on 1659 L2 addressing. 1661 o Explanded "Transition Considerations". 1663 Differences from draft-templin-6man-omni-interface-05 to draft- 1664 templin-6man-omni-interface-06: 1666 o Brought back OMNI option "R" flag, and dicussed its use. 1668 Differences from draft-templin-6man-omni-interface-04 to draft- 1669 templin-6man-omni-interface-05: 1671 o Transition considerations, and overhaul of RS/RA addressing with 1672 the inclusion of MSE addresses within the OMNI option instead of 1673 as RS/RA addresses (developed under FAA SE2025 contract number 1674 DTFAWA-15-D-00030). 1676 Differences from draft-templin-6man-omni-interface-02 to draft- 1677 templin-6man-omni-interface-03: 1679 o Added "advisory PTB messages" under FAA SE2025 contract number 1680 DTFAWA-15-D-00030. 1682 Differences from draft-templin-6man-omni-interface-01 to draft- 1683 templin-6man-omni-interface-02: 1685 o Removed "Primary" flag and supporting text. 1687 o Clarified that "Router Lifetime" applies to each ANET interface 1688 independently, and that the union of all ANET interface Router 1689 Lifetimes determines MSE lifetime. 1691 Differences from draft-templin-6man-omni-interface-00 to draft- 1692 templin-6man-omni-interface-01: 1694 o "All-MSEs" OMNI LLA defined. Also reserverd fe80::ff00:0000/104 1695 for future use (most likely as "pseudo-multicast"). 1697 o Non-normative discussion of alternate OMNI LLA construction form 1698 made possible if the 64-bit assumption were relaxed. 1700 Differences from draft-templin-atn-aero-interface-21 to draft- 1701 templin-6man-omni-interface-00: 1703 o Minor clarification on Type-2 ifIndex-tuple encoding. 1705 o Draft filename change (replaces draft-templin-atn-aero-interface). 1707 Differences from draft-templin-atn-aero-interface-20 to draft- 1708 templin-atn-aero-interface-21: 1710 o OMNI option format 1712 o MTU 1714 Differences from draft-templin-atn-aero-interface-19 to draft- 1715 templin-atn-aero-interface-20: 1717 o MTU 1719 Differences from draft-templin-atn-aero-interface-18 to draft- 1720 templin-atn-aero-interface-19: 1722 o MTU 1724 Differences from draft-templin-atn-aero-interface-17 to draft- 1725 templin-atn-aero-interface-18: 1727 o MTU and RA configuration information updated. 1729 Differences from draft-templin-atn-aero-interface-16 to draft- 1730 templin-atn-aero-interface-17: 1732 o New "Primary" flag in OMNI option. 1734 Differences from draft-templin-atn-aero-interface-15 to draft- 1735 templin-atn-aero-interface-16: 1737 o New note on MSE OMNI LLA uniqueness assurance. 1739 o General cleanup. 1741 Differences from draft-templin-atn-aero-interface-14 to draft- 1742 templin-atn-aero-interface-15: 1744 o General cleanup. 1746 Differences from draft-templin-atn-aero-interface-13 to draft- 1747 templin-atn-aero-interface-14: 1749 o General cleanup. 1751 Differences from draft-templin-atn-aero-interface-12 to draft- 1752 templin-atn-aero-interface-13: 1754 o Minor re-work on "Notify-MSE" (changed to Notification ID). 1756 Differences from draft-templin-atn-aero-interface-11 to draft- 1757 templin-atn-aero-interface-12: 1759 o Removed "Request/Response" OMNI option formats. Now, there is 1760 only one OMNI option format that applies to all ND messages. 1762 o Added new OMNI option field and supporting text for "Notify-MSE". 1764 Differences from draft-templin-atn-aero-interface-10 to draft- 1765 templin-atn-aero-interface-11: 1767 o Changed name from "aero" to "OMNI" 1769 o Resolved AD review comments from Eric Vyncke (posted to atn list) 1771 Differences from draft-templin-atn-aero-interface-09 to draft- 1772 templin-atn-aero-interface-10: 1774 o Renamed ARO option to AERO option 1776 o Re-worked Section 13 text to discuss proactive NUD. 1778 Differences from draft-templin-atn-aero-interface-08 to draft- 1779 templin-atn-aero-interface-09: 1781 o Version and reference update 1783 Differences from draft-templin-atn-aero-interface-07 to draft- 1784 templin-atn-aero-interface-08: 1786 o Removed "Classic" and "MS-enabled" link model discussion 1788 o Added new figure for MN/AR/MSE model. 1790 o New Section on "Detecting and responding to MSE failure". 1792 Differences from draft-templin-atn-aero-interface-06 to draft- 1793 templin-atn-aero-interface-07: 1795 o Removed "nonce" field from AR option format. Applications that 1796 require a nonce can include a standard nonce option if they want 1797 to. 1799 o Various editorial cleanups. 1801 Differences from draft-templin-atn-aero-interface-05 to draft- 1802 templin-atn-aero-interface-06: 1804 o New Appendix C on "VDL Mode 2 Considerations" 1806 o New Appendix D on "RS/RA Messaging as a Single Standard API" 1808 o Various significant updates in Section 5, 10 and 12. 1810 Differences from draft-templin-atn-aero-interface-04 to draft- 1811 templin-atn-aero-interface-05: 1813 o Introduced RFC6543 precedent for focusing IPv6 ND messaging to a 1814 reserved unicast link-layer address 1816 o Introduced new IPv6 ND option for Aero Registration 1818 o Specification of MN-to-MSE message exchanges via the ANET access 1819 router as a proxy 1821 o IANA Considerations updated to include registration requests and 1822 set interim RFC4727 option type value. 1824 Differences from draft-templin-atn-aero-interface-03 to draft- 1825 templin-atn-aero-interface-04: 1827 o Removed MNP from aero option format - we already have RIOs and 1828 PIOs, and so do not need another option type to include a Prefix. 1830 o Clarified that the RA message response must include an aero option 1831 to indicate to the MN that the ANET provides a MS. 1833 o MTU interactions with link adaptation clarified. 1835 Differences from draft-templin-atn-aero-interface-02 to draft- 1836 templin-atn-aero-interface-03: 1838 o Sections re-arranged to match RFC4861 structure. 1840 o Multiple aero interfaces 1842 o Conceptual sending algorithm 1844 Differences from draft-templin-atn-aero-interface-01 to draft- 1845 templin-atn-aero-interface-02: 1847 o Removed discussion of encapsulation (out of scope) 1849 o Simplified MTU section 1851 o Changed to use a new IPv6 ND option (the "aero option") instead of 1852 S/TLLAO 1854 o Explained the nature of the interaction between the mobility 1855 management service and the air interface 1857 Differences from draft-templin-atn-aero-interface-00 to draft- 1858 templin-atn-aero-interface-01: 1860 o Updates based on list review comments on IETF 'atn' list from 1861 4/29/2019 through 5/7/2019 (issue tracker established) 1863 o added list of opportunities afforded by the single virtual link 1864 model 1866 o added discussion of encapsulation considerations to Section 6 1868 o noted that DupAddrDetectTransmits is set to 0 1870 o removed discussion of IPv6 ND options for prefix assertions. The 1871 aero address already includes the MNP, and there are many good 1872 reasons for it to continue to do so. Therefore, also including 1873 the MNP in an IPv6 ND option would be redundant. 1875 o Significant re-work of "Router Discovery" section. 1877 o New Appendix B on Prefix Length considerations 1879 First draft version (draft-templin-atn-aero-interface-00): 1881 o Draft based on consensus decision of ICAO Working Group I Mobility 1882 Subgroup March 22, 2019. 1884 Authors' Addresses 1886 Fred L. Templin (editor) 1887 The Boeing Company 1888 P.O. Box 3707 1889 Seattle, WA 98124 1890 USA 1892 Email: fltemplin@acm.org 1894 Tony Whyman 1895 MWA Ltd c/o Inmarsat Global Ltd 1896 99 City Road 1897 London EC1Y 1AX 1898 England 1900 Email: tony.whyman@mccallumwhyman.com