Automatic Extended Route Optimization (AERO)

3.2.1. AERO/OMNI Reference Model

Figure 1 presents the basic OMNI link reference model:¶

                      +-----------------+
                      | AERO Gateway G1 |
                      | Nbr: S1, S2, P1 |
                      |(X1->S1; X2->S2) |
                      |      MSP M1     |
                      +--------+--------+
    +--------------+           |            +--------------+
    |  AERO P/S S1 |           |            |  AERO P/S S2 |
    |  Nbr: C1, G1 |           |            |  Nbr: C2, G1 |
    |  default->G1 |           |            |  default->G1 |
    |    X1->C1    |           |            |    X2->C2    |
    +-------+------+           |            +------+-------+
            |       OMNI link  |                   |
    X===+===+==================+===================+===+===X
        |                                              |
  +-----+--------+                            +--------+-----+
  |AERO Client C1|                            |AERO Client C2|
  |    Nbr: S1   |                            |   Nbr: S2    |
  | default->S1  |                            | default->S2  |
  |    MNP X1    |                            |    MNP X2    |
  +------+-------+                            +-----+--------+
         |                                          |
        .-.                                        .-.
     ,-(  _)-.     +-------+     +-------+      ,-(  _)-.
  .-(_  IP   )-.   |  AERO |     |  AERO |    .-(_  IP   )-.
(__    ENET     )--|Host H1|     |Host H2|--(__    ENET     )
   `-(______)-'    +-------+     +-------+     `-(______)-'

In this model:¶

• the OMNI link is an overlay network service configured over one or more underlay SRT segments which may be managed by different administrative authorities and have incompatible protocols and/or addressing plans.¶
• AERO Gateway G1 aggregates Mobility Service Prefix (MSP) M1, discovers Mobile Network Prefixes (MNPs) X* and advertises the MSP via BGP peerings over secured tunnels to Proxy/Servers (S1, S2). Gateways provide the backbone for an SRT spanning tree for the OMNI link.¶
• AERO Proxy/Servers S1 and S2 configure secured tunnels with Gateway G1 and also provide mobility, multilink, multicast and default router services for the MNPs of their associated Clients C1 and C2. (Proxy/Servers that act as Relays can also advertise non-MNP routes for non-mobile correspondent nodes the same as for MNP Clients.)¶
• AERO Clients C1 and C2 associate with Proxy/Servers S1 and S2, respectively. They receive MNP delegations X1 and X2, and also act as default routers for their associated physical or internal virtual ENETs.¶
• AERO Hosts H1 and H2 attach to the ENETs served by Clients C1 and C2, respectively.¶

An OMNI link configured over a single underlay network appears as a single unified link with a consistent addressing plan; all nodes on the link can exchange carrier packets via simple L2 encapsulation (i.e., following any necessary NAT traversal) since the underlay is connected. In common practice, however, OMNI links are often configured over an SRT spanning tree that bridges multiple distinct underlay network segments managed under different administrative authorities (e.g., as for worldwide aviation service providers such as ARINC, SITA, Inmarsat, etc.). Individual underlay networks may also be partitioned internally, in which case each internal partition appears as a separate segment.¶

The addressing plan of each SRT segment is consistent internally but will often bear no relation to the addressing plans of other segments. Each segment is also likely to be separated from others by network security devices (e.g., firewalls, proxys, packet filtering gateways, etc.), and disjoint segments often have no common physical link connections. Therefore, nodes can only be assured of exchanging carrier packets directly with correspondents in the same segment, and not with those in other segments. The only means for joining the segments therefore is through inter-domain peerings between AERO Gateways.¶

The OMNI link spans multiple SRT segments using the OMNI Adaptation Layer (OAL) [I-D.templin-6man-omni] to provide the network layer with a virtual abstraction similar to a bridged campus LAN. The OAL is an OMNI interface sublayer that inserts a mid-layer IPv6 encapsulation header for inter-segment forwarding (i.e., bridging) without decrementing the network-layer TTL/Hop Limit of the original IP packet. An example OMNI link SRT is shown in Figure 2:¶

              . . . . . . . . . . . . . . . . . . . . . . .
            .                                               .
            .              .-(::::::::)                     .
            .           .-(::::::::::::)-.   +-+            .
            .          (:::: Segment A :::)--|G|---+        .
            .           `-(::::::::::::)-'   +-+   |        .
            .              `-(::::::)-'            |        .
            .                                      |        .
            .              .-(::::::::)            |        .
            .           .-(::::::::::::)-.   +-+   |        .
            .          (:::: Segment B :::)--|G|---+        .
            .           `-(::::::::::::)-'   +-+   |        .
            .              `-(::::::)-'            |        .
            .                                      |        .
            .              .-(::::::::)            |        .
            .           .-(::::::::::::)-.   +-+   |        .
            .          (:::: Segment C :::)--|G|---+        .
            .           `-(::::::::::::)-'   +-+   |        .
            .              `-(::::::)-'            |        .
            .                                      |        .
            .                ..(etc)..             x        .
            .                                               .
            .                                               .
            .    <-    Segment Routing Topology (SRT) ->    .
            .             (Spanned by OMNI Link)            .
              . . . . . . . . . . . . . .. . . . . . . . .

Gateway, Proxy/Server and Relay OMNI interfaces are configured over both secured tunnels and open INET underlay interfaces within their respective SRT segments. Within each segment, Gateways configure "hub-and-spokes" BGP peerings with Proxy/Servers and Relays as "spokes". Adjacent SRT segments are joined by Gateway-to-Gateway peerings to collectively form a spanning tree over the entire SRT. The "secured" spanning tree supports authentication and integrity for critical control plane messages. The "unsecured" spanning tree conveys ordinary carrier packets without security codes and that must be treated by destinations according to data origin authentication procedures. AERO nodes can employ route optimization to cause carrier packets to take more direct paths between OMNI link neighbors without having to follow strict spanning tree paths.¶

The AERO Multinet service concatenates SRT segments to form larger networks through Gateway-to-Gateway peerings as originally described in the "Catenet Model for Internetworking" [IEN48]; especially Figure 2 follows directly from the illustrations in [IEN48-2]. The Catenet model inspired the global public Internet as it is known today, while AERO applies the Catenet concepts to provide true Multinet services for the future architecture.¶

3.2.2. Addressing and Node Identification

AERO nodes on OMNI links use the Link-Local Address (LLA) prefix fe80::/64 [RFC4291] to assign LLAs to the OMNI interface in a latent state and do not employ LLAs for any operational purposes. (Instead, the LLAs are assigned solely to satisfy the requirements of [RFC4861].) AERO Clients configure LLAs constructed from MNPs (i.e., "MNP-LLAs") while AERO infrastructure nodes construct LLAs based on 56-bit random values ("RND-LLAs") per [I-D.templin-6man-omni]. Non-MNP routes are also represented the same as for MNPs, but may include a prefix that is not properly covered by an MSP.¶

AERO nodes also use the Unique Local Address (ULA) prefix fd00::/8 followed by a pseudo-random 40-bit Global ID to form the prefix {ULA}::/48, then include a 16-bit Subnet ID '*' to form the prefix {ULA*}::/64 [RFC4291]. The AERO node then uses the prefix {ULA*}::/64 to form "MNP-ULAs" or "RND-ULA"s as specified in [I-D.templin-6man-omni] to support OAL addressing. (The prefix {ULA*}::/64 appearing alone and with no suffix represents "default" for that prefix.) AERO Clients also use MNP-based eXtended Local Addresses (MNP-XLAs) and Temporary ULAs (TMP-ULAs) constructed per [I-D.templin-6man-omni], where TMP-ULAs are typically used only in initial control message exchanges until a stable MNP-ULA is assigned (and may sometimes be used for sustained communications within a local routing region).¶

AERO MSPs, MNPs and non-MNP routes are typically based on Global Unicast Addresses (GUAs), but in some cases may be based on private-use addresses. A GUA block is also reserved for OMNI link anycast purposes. See [I-D.templin-6man-omni] for a full specification of LLAs, ULAs and GUAs used by AERO nodes on OMNI links.¶

Finally, AERO Clients and Proxy/Servers configure node identification values as specified in [I-D.templin-6man-omni].¶

3.2.3. AERO Routing System

The AERO routing system comprises a private Border Gateway Protocol (BGP) [RFC4271] service coordinated between Gateways and Proxy/Servers (Relays also engage in the routing system as simplified Proxy/Servers). The service supports carrier packet forwarding at a layer below IP and does not interact with the public Internet BGP routing system, but supports redistribution of information for other links and networks connected by Relays.¶

In a reference deployment, each Proxy/Server is configured as an Autonomous System Border Router (ASBR) for a stub Autonomous System (AS) using a 32-bit AS Number (ASN) [RFC4271] that is unique within the BGP instance, and each Proxy/Server further uses eBGP to peer with one or more Gateways but does not peer with other Proxy/Servers. Each SRT segment in the OMNI link must include one or more Gateways in a "hub" AS, which peer with the Proxy/Servers within that segment as "spoke" ASes. All Gateways within the same segment are members of the same hub AS, and use iBGP to maintain a consistent view of all active routes currently in service. The Gateways of different segments peer with one another using eBGP.¶

Gateways maintain forwarding table entries only for MNP-XLAs corresponding to MNP and non-MNP routes that are currently active, and also maintain black-hole routes for the OMNI link MSPs so that carrier packets destined to non-existent more-specific routes are dropped with a Destination Unreachable message returned. In this way, Proxy/Servers and Relays have only partial topology knowledge (i.e., they only maintain routing information for their directly associated Clients and non-AERO links) and they forward all other carrier packets to Gateways which have full topology knowledge.¶

Each OMNI link segment assigns a unique RND-ULA sub-prefix of {ULA}::/48 known as the "SRT prefix". For example, a first segment could assign {ULA}:1000::/56, a second could assign {ULA}:2000::/56, a third could assign {ULA}:3000::/56, etc. Within each segment, each Proxy/Server configures a RND-ULA within the segment's SRT prefix with a 56-bit random value in the interface identifier as specified in [I-D.templin-6man-omni].¶

The administrative authorities for each segment must therefore coordinate to assure mutually-exclusive RND-ULA prefix assignments, but internal provisioning of RND-ULAs is an independent local consideration for each administrative authority. For each RND-ULA prefix, the Gateway(s) that connect that segment assign the all-zero's address of the prefix as a Subnet Router Anycast address. For example, the Subnet Router Anycast address for {ULA}:1023::/64 is simply {ULA}:1023::/64.¶

RND-ULA prefixes are statically represented in Gateway forwarding tables. Gateways join multiple SRT segments into a unified OMNI link over multiple diverse network administrative domains. They support a virtual bridging service by first establishing forwarding table entries for their RND-ULA prefixes either via standard BGP routing or static routes. For example, if three Gateways ('A', 'B' and 'C') from different segments serviced {ULA}:1000::/60, {ULA}:2000::/56 and {ULA}:3000::/56 respectively, then the forwarding tables in each Gateway appear as follows:¶

A:

{ULA}:1000::/56->local, {ULA}:2000::/56->B, {ULA}:3000::/56->C¶

B:

{ULA}:1000::/56->A, {ULA}:2000::/56->local, {ULA}:3000::/56->C¶

C:

{ULA}:1000::/56->A, {ULA}:2000::/56->B, {ULA}:3000::/56->local¶

These forwarding table entries rarely change, since they correspond to fixed infrastructure elements in their respective segments.¶

MNP (and non-MNP) ULA routes are instead dynamically advertised in the AERO routing system by Proxy/Servers and Relays that provide service for their corresponding MNPs. The routes are advertised as MNP-XLA prefixes, i.e., as fd00::{MNP} (see: [I-D.templin-6man-omni]). For example, if three Proxy/Servers ('D', 'E' and 'F') service the MNPs 2001:db8:1000:2000::/56, 2001:db8:3000:4000::/56 and 2001:db8:5000:6000::/56 then the routing system would include:¶

D:

fd00::2001:db8:1000:2000/120¶

E:

fd00::2001:db8:3000:4000/120¶

F:

fd00::2001:db8:5000:6000/120¶

A full discussion of the BGP-based routing system used by AERO is found in [I-D.ietf-rtgwg-atn-bgp].¶

3.2.4. Segment Routing Topologies (SRTs)

The distinct {ULA}::/48 prefixes in an OMNI link domain identify distinct Segment Routing Topologies (SRTs). Each SRT is a mutually-exclusive OMNI link overlay instance using a distinct set of ULAs, and emulates a bridged campus LAN service for the OMNI link. In some cases (e.g., when redundant topologies are needed for fault tolerance and reliability) it may be beneficial to deploy multiple SRTs that act as independent overlay instances. A communication failure in one instance therefore will not affect communications in other instances.¶

Each SRT is identified by a distinct value in the 40-bit ULA Global ID field and assigns an OMNI IPv6 anycast address used for OMNI interface determination in Safety-Based Multilink (SBM) as discussed in [I-D.templin-6man-omni]. Each OMNI interface further applies Performance-Based Multilink (PBM) internally.¶

The Gateways and Proxy/Servers of each independent SRT engage in BGP peerings to form a spanning tree with the Gateways in non-leaf nodes and the Proxy/Servers in leaf nodes. The spanning tree is configured over both secured and unsecured underlay network paths. The secured spanning tree is used to convey secured control messages between Proxy/Servers and Gateways, while the unsecured spanning tree forwards data messages and/or unsecured control messages.¶

Each SRT segment is identified by a unique RND-ULA prefix used by all Proxy/Servers and Gateways in the segment. Each AERO node must therefore discover an SRT prefix that correspondents can use to determine the correct segment, and must publish the SRT prefix in IPv6 ND messages.¶

Note: The distinct ULA prefixes in an OMNI link domain can be carried either in a common BGP routing protocol instance for all OMNI links or in distinct BGP routing protocol instances for different OMNI links. In some SBM environments, such separation may be necessary to ensure that distinct OMNI links do not include any common infrastructure elements as single points of failure. In other environments, carrying the ULAs of multiple OMNI links within a common routing system may be acceptable.¶

3.2.5. Segment Routing For OMNI Link Selection

Original IPv6 sources can direct IPv6 packets to an AERO node by including a standard IPv6 Segment Routing Header (SRH) [RFC8754] with the OMNI IPv6 anycast address for the selected OMNI link as either the IPv6 destination or as an intermediate hop within the SRH. This allows the original source to determine the specific OMNI link SRT an original IPv6 packet will traverse when there may be multiple alternatives.¶

When an AERO node processes the SRH and forwards the original IPv6 packet to the correct OMNI interface, the OMNI interface writes the next IPv6 address from the SRH into the IPv6 destination address and decrements Segments Left. If decrementing would cause Segments Left to become 0, the OMNI interface deletes the SRH before forwarding. This form of Segment Routing supports Safety-Based Multilink (SBM).¶

3.4.1. AERO Proxy/Server and Relay Behavior

When a Proxy/Server enables an OMNI interface, it assigns a RND-ULA appropriate for the given OMNI link SRT segment. The Proxy/Server also configures secured tunnels and engages in BGP routing protocol sessions with one or more neighboring Gateways.¶

The OMNI interface provides a single interface abstraction to the IP layer, but internally includes an NBMA nexus for sending carrier packets to OMNI interface neighbors over underlay INET interfaces and secured tunnels. The Proxy/Server further configures a service to facilitate IPv6 ND exchanges with AERO Clients and manages per-Client neighbor cache entries and IP forwarding table entries based on control message exchanges.¶

Relays are simply Proxy/Servers that run a dynamic routing protocol to redistribute routes between the OMNI interface and INET/ENET interfaces (see: Section 3.2.3). The Relay provisions MNPs to networks on the INET/ENET interfaces (i.e., the same as a Client would do) and advertises the MSP(s) for the OMNI link over the INET/ENET interfaces. The Relay further provides an attachment point of the OMNI link to a non-MNP-based global topology.¶

3.4.2. AERO Client Behavior

When a Client enables an OMNI interface, it assigns either an MNP-XLA or a TMP-ULA and sends OMNI-encapsulated RS messages over its ANET/INET underlay interfaces to an FHS Proxy/Server, which coordinates with a Hub Proxy/Server that returns an RA message with corresponding parameters. The RS/RA messages may pass through one or more NATs in the path between the Client and FHS Proxy/Server. (Note: if the Client used a TMP-ULA in its initial RS messages, it may discover MNP-ULAs in the corresponding RAs that it receives from FHS Proxy/Servers and begin using these new addresses. If the Client is operating outside the context of AERO infrastructure such as in a Mobile Ad-hoc Network (MANET), however, it may continue using TMP-ULAs for Client-to-Client communications until it encounters an infrastructure element that can delegate MNPs.)¶

A Client can further extend the OMNI link over its (downstream) ENET interfaces where it provides a first-hop router for Hosts and other AERO Clients connected to the ENET. A downstream Client that connects via the ENET serviced by an upstream Client can in turn service further downstream ENETs that connect other Hosts and Clients. This OMNI link extension can be applied recursively over a "chain" of ENET Clients.¶

3.4.3. AERO Host Behavior

When a Host enables an OMNI interface, it assigns an address taken from the ENET underlay interface which may itself be a GUA delegated by the upstream Client. The Host does not assign a link-local address to the OMNI interface, since no autoconfiguration is necessary on that interface. (As an implementation matter, the Host could instead configure the "OMNI interface" as a virtual sublayer of the ENET underlay interface itself.)¶

The Host sends OMNI-encapsulated RS messages over its ENET underlay interface to the upstream Client, which returns encapsulated RAs and provides routing services in the same fashion that Proxy/Servers provides services for Clients. Hosts represent the leaf end systems in recursively-nested chain of concatenated ENETs, i.e., they represent terminating endpoints for the OMNI link.¶

3.4.4. AERO Gateway Behavior

AERO Gateways configure an OMNI interface and assign a RND-ULA and corresponding Subnet Router Anycast address for each OMNI link SRT segment they connect to. Gateways configure secured tunnels with Proxy/Servers in the same SRT segment and other Gateways in the same (or an adjacent) SRT segment. Gateways then engage in a BGP routing protocol session with neighbors over the secured spanning tree (see: Section 3.2.3).¶

3.5.1. OMNI ND Messages

OMNI interfaces prepare IPv6 ND messages the same as for standard IPv6 ND, but also include a new option type termed the OMNI option [I-D.templin-6man-omni]. OMNI interfaces do not use LLAs as IPv6 ND message source and destination addresses, but instead use ULAs. This allows for multiple different OMNI links to be joined into a single link at some future time without requiring a global renumbering event.¶

For each IPv6 ND message, OMNI interfaces include one or more OMNI options (and any other ND message options) then completely populate all option information. If the OMNI interface includes an authentication signature, it sets the IPv6 ND message Checksum field to 0 and calculates the authentication signature over the entire length of the OAL packet or super-packet (beginning with a pseudo-header of the IPv6 header) but does not then proceed to calculate the IPv6 ND message checksum itself. Otherwise, the OMNI interface calculates the standard IPv6 ND message checksum over the OAL packet or super-packet and writes the value in the Checksum field. OMNI interfaces verify authentication and integrity of each IPv6 ND message received according to the specific check(s) included, and process the message further only following verification.¶

OMNI options include per-neighbor information that provides multilink forwarding, link-layer address and traffic selector information for the neighbor's underlay interfaces. This information is stored in the neighbor cache and provides the basis for the forwarding algorithm specified in Section 3.10. The information is cumulative and reflects the union of the OMNI information from the most recent IPv6 ND messages received from the neighbor; it is therefore not required that each IPv6 ND message contain all neighbor information.¶

The OMNI option is distinct from any Source/Target Link-Layer Address Options (S/TLLAOs) that may appear in an IPv6 ND message according to the appropriate IPv6 over specific link layer specification (e.g., [RFC2464]). If both an OMNI option and S/TLLAO appear, the former pertains to encapsulation addresses while the latter pertains to the native L2 address format of the underlay media.¶

OMNI interface IPv6 ND messages may also include other IPv6 ND options. In particular, solicitation messages may include a Nonce option if required for verification of advertisement replies. If an OMNI IPv6 ND solicitation message includes a Nonce option, the advertisement reply must echo the same Nonce. If an OMNI IPv6 ND advertisement message includes a Timestamp option, the recipient should check the Timestamp to determine if the message is current.¶

AERO Clients send RS messages to the link-scoped All-Routers multicast address or a RND-ULA while using unicast or anycast L2 addresses. AERO Proxy/Servers respond by returning unicast RA messages. During the RS/RA exchange, AERO Clients and Proxy/Servers include state synchronization parameters to establish Identification windows and other state.¶

AERO Hosts and Clients on ENET underlay networks send RS messages to the link-scoped All-Routers multicast address, a RND-ULA of a remote Hub Proxy/Server or the MNP-ULA of an upstream Client while using unicast or anycast L2 addresses. The upstream AERO Client responds by returning a unicast RA message.¶

AERO nodes use NS/NA messages for the following purposes:¶

• NS/NA(AR) messages are used for address resolution and optionally to establish sequence number windows. The ROS sends an NS(AR) to the solicited-node multicast address of the target, and an ROR with addressing information for the target returns a unicast NA(AR) that contains current, consistent and authentic target address resolution information. NS/NA(AR) messages must be secured.¶
• NS/NA(NUD) messages are used to establish multilink forwarding state and determine target reachability. The source sends an NS(NUD) to the unicast address of the target while naming a specific underlay interface pair, and the target returns a unicast NA(NUD). NS/NA(NUD) messages that use an in-window sequence number and do not update any other state need not include an authentication signature but instead must include an IPv6 ND message checksum. NS/NA(NUD) messages may also be used to establish window synchronization and/or MFIB state, in which case the messages must be secured.¶
• Unsolicited NA (uNA) messages are used to signal addressing and/or other neighbor state changes (e.g., address changes due to mobility, signal degradation, traffic selector updates, etc.). uNA messages that update state information must be secured.¶
• NS/NA(DAD) messages are not used in AERO, since Duplicate Address Detection is not required.¶

Additionally, nodes may set the OMNI option PNG flag in NA/RA messages to receive a uNA response from the neighbor. The uNA response MUST set the ACK flag (without also setting the SYN or PNG flags) with the Acknowledgement field set to the Identification used in the PNG message.¶

3.5.2. OMNI Neighbor Advertisement Message Flags

As discussed in Section 4.4 of [RFC4861] NA messages include three flag bits R, S and O. OMNI interface NA messages treat the flags as follows:¶

• R: The R ("Router") flag is set to 1 in the NA messages sent by all AERO/OMNI node types. Simple hosts that would set R to 0 do not occur on the OMNI link itself, but may occur on the downstream links of Clients and Relays.¶
• S: The S ("Solicited") flag is set exactly as specified in Section 4.4. of [RFC4861], i.e., it is set to 1 for Solicited NAs and set to 0 for uNAs (both unicast and multicast).¶
• O: The O ("Override") flag is set to 0 for solicited NAs returned by a Proxy/Server ROR and set to 1 for all other solicited and unsolicited NAs. For further study is whether solicited NAs for anycast targets apply for OMNI links. Since MNP-XLAs must be uniquely assigned to Clients to support correct IPv6 ND protocol operation, however, no role is currently seen for assigning the same MNP-XLA to multiple Clients.¶

3.5.3. OMNI Neighbor Window Synchronization

In secured environments (e.g., between secured spanning tree neighbors, between neighbors on the same secured ANET, etc.), OMNI interface neighbors can exchange OAL packets using randomly-initialized and monotonically-increasing Identification values (modulo 2**32) without window synchronization. In environments where spoofing is considered a threat, OMNI interface neighbors instead invoke window synchronization in NS/NA message exchanges to maintain send/receive window state in their respective neighbor cache entries as specified in [I-D.templin-6man-omni].¶

3.10.1. Host Forwarding Algorithm

When an original IP packet enters a Host's OMNI interface from the network layer the Host searches for a NCE that matches the destination. If there is a matching NCE, the Host performs L2 encapsulation, fragments the encapsulated packet if necessary and forwards the packets into the ENET addressed to the L2 address of the neighbor.¶

After sending a packet, the Host may receive a Redirect message from its upstream Client to inform it of another AERO node on the same ENET that would provide a better first hop. The Host authenticates the Redirect message, then updates its neighbor cache accordingly.¶

3.10.2. Client Forwarding Algorithm

When an original IP packet enters a Client's OMNI interface from the network layer the Client searches for a NCE that matches the destination. If there is a matching NCE on an ANET/INET interface (i.e., an upstream interface), the Client selects one or more "reachable" neighbor interfaces in the entry for forwarding purposes. Otherwise, the Client invokes route optimization per Section 3.13 and follows the multilink forwarding procedures outlined there. If there is a matching NCE on an ENET interface (i.e., a downstream interface), the Client instead performs OAL and/or L2 encapsulation and forwards the packet to the downstream Host or Client.¶

When a carrier packet enters a Client's OMNI interface from the link-layer, if the OAL destination matches one of the Client's ULAs the Client (acting as an OAL destination) verifies that the Identification is in-window for this OAL source, then reassembles and decapsulates as necessary and delivers the original IP packet to the network layer. If the OAL destination matches a NCE for a Host or Client on an ENET interface, the Client instead forwards the carrier packet to the Host/Client. If the OAL destination does not match, the Client drops the original IP packet and MAY return a network-layer ICMP Destination Unreachable message subject to rate limiting (see: Section 3.11).¶

When a Client forwards a carrier packet from an ENET Host to a neighbor connected to the same ENET, it also returns a Redirect message to inform the source that it can reach the neighbor directly as an ENET peer.¶

Note: Clients and their FHS Proxy/Server (and other Client) peers can exchange original IP packets over ANET underlay interfaces without invoking the OAL, since the ANET is secured at the link and physical layers. By forwarding original IP packets without invoking the OAL, however, the ANET peers can engage only in classical path MTU discovery since the packets are subject to loss and/or corruption due to the various per-link MTU limitations that may occur within the ANET. Moreover, the original IP packets do not include either the OAL integrity check or per-packet Identification values that can be used for data origin authentication and link-layer retransmissions. The tradeoff therefore involves an assessment of the per-packet encapsulation overhead saved by bypassing the OAL vs. inheritance of classical network "brittleness". (Note however that ANET peers can send small original IP packets without invoking the OAL, while invoking the OAL for larger packets. This presents the beneficial aspects of both small packet efficiency and large packet robustness, with delay variance and reordering as possible side effects.)¶

Note: The forwarding table entries established in peer Clients of a multihop forwarding region are based on MNP-ULAs and/or TMP-ULAs used to seed the multihop routing protocols. When MNP-ULAs are used, the ULA /64 prefix provides topological relevance for the multihop forwarding region, while the 64-bit Interface Identifier encodes the Client MNP. Therefore, Clients can forward atomic fragments with compressed OAL headers that do not include ULA or MFVI information by examining the MNP-based addresses in the actual IP packet header. In other words, each forwarding table entry contains two pieces of forwarding information - the ULA information in the prefix and the MNP information in the interface identifier.¶

3.10.3. Proxy/Server and Relay Forwarding Algorithm

When a Proxy/Server receives an original IP packet from the network layer, it drops the packet if routing indicates that it should be forwarded back to the network layer to avoid looping. Otherwise, the Proxy/Server regards the original IP packet the same as if it had arrived as carrier packets with OAL destination set to its own RND-ULA. When the Proxy/Server receives carrier packets on underlay interfaces with OAL destination set to its own RND-ULA, it performs OAL reassembly if necessary to obtain the original IP packet. The Proxy/Server then supports multilink forwarding procedures as specified in Section 3.13.2 and/or acts as an ROS to initiate route optimization as specified in Section 3.13.¶

When the Proxy/Server receives a carrier packet with OAL destination set to an MNP-ULA that does not match the MSP, it accepts the carrier packet only if data origin authentication succeeds and if there is a network layer routing table entry for a GUA route that matches the MNP-ULA. If there is no route, the Proxy/Server drops the carrier packet; otherwise, it reassembles and decapsulates to obtain the original IP packet then acts as a Relay to present it to the network layer where it will be delivered according to standard IP forwarding.¶

When a Proxy/Server receives a carrier packet from one of its Client neighbors with OAL destination set to another node, it forwards the packets via a matching NCE or via the spanning tree if there is no matching entry. When the Proxy/Server receives a carrier packet with OAL destination set to an MNP-ULA of one of its Client neighbors established through RS/RA exchanges, it accepts the carrier packet only if data origin authentication succeeds. If the NCE state is DEPARTED, the Proxy/Server changes the OAL destination address to the RND-ULA of the new Proxy/Server, then re-encapsulates the carrier packet and forwards it to a Gateway which will eventually deliver it to the new Proxy/Server. If the neighbor cache state for the Client is REACHABLE, the Proxy/Server forwards the carrier packets to the Client which then must reassemble. (Note that the Proxy/Server does not reassemble carrier packets not explicitly addressed to its own RND-ULA, since some of the carrier packets of the same original IP packet could be forwarded through a different Proxy/Server.) In that case, the Client may receive fragments that are smaller than its link MTU but that can still be reassembled.¶

Proxy/Servers process carrier packets with OAL destinations that do not match their RND-ULA in the same manner as for traditional IP forwarding within the OAL, i.e., nodes use IP forwarding to forward packets not explicitly addressed to themselves. (Proxy/Servers include a special case that accepts and reassembles carrier packets destined to an MNP-XLA or MNP-ULA of one of their Clients received over the secured spanning tree.) Proxy/Servers process carrier packets with their RND-ULA as the destination by first examining the packet for a CRH-32 header or an OCH header. In that case, the Proxy/Server examines the next MFVI in the carrier packet to locate the MFV entry in the MFIB for next hop forwarding (i.e., without examining IP addresses). When the Proxy/Server forwards the carrier packet, it changes the destination address according to the MFVI value for the next hop found either in the CRH-32 header or in the node's own MFIB. Proxy/Servers must verify that the L2 addresses of carrier packets not received from the secured spanning tree are "trusted" before forwarding according to an MFV (otherwise, the carrier packet must be dropped).¶

Note: Proxy/Servers may receive carrier packets addressed to their own RND-ULA with CRH-32s that include additional forwarding information. Proxy/Servers use the forwarding information to determine the correct NCE and underlay interface for forwarding to the target Client, then remove the CRH-32 and forward the carrier packet. If necessary, the Proxy/Server reassembles first before re-encapsulating (and possibly also re-fragmenting) then forwards to the target Client.¶

Note: Clients and their FHS Proxy/Server peers can exchange original IP packets over ANET underlay interfaces without invoking the OAL, since the ANET is secured at the link and physical layers. By forwarding original IP packets without invoking the OAL, however, the Client and Proxy/Server can engage only in classical path MTU discovery since the packets are subject to loss and/or corruption due to the various per-link MTU limitations that may occur within the ANET. Moreover, the original IP packets do not include either the OAL integrity check or per-packet Identification values that can be used for data origin authentication and link-layer retransmissions. The tradeoff therefore involves an assessment of the per-packet encapsulation overhead saved by bypassing the OAL vs. inheritance of classical network "brittleness". (Note however that ANET peers can send small original IP packets without invoking the OAL, while invoking the OAL for larger packets. This presents the beneficial aspects of both small packet efficiency and large packet robustness.)¶

Note: When a Proxy/Server receives a (non-OAL) original IP packet from an ANET Client, or a carrier packet with OAL destination set to its own RND-ULA from any Client, the Proxy/Server reassembles if necessary then performs ROS functions on behalf of the Client. The Client may at some later time begin sending carrier packets to the OAL address of the actual target instead of the Proxy/Server, at which point it may begin functioning as an ROS on its own behalf and thereby "override" the Proxy/Server's ROS role.¶

Note; Proxy/Servers drop any original IP packets (received either directly from an ANET Client or following reassembly of carrier packets received from an ANET/INET Client) with a destination that corresponds to the Client's delegated MNP. Similarly, Proxy/Servers drop any carrier packet received with both a source and destination that correspond to the Client's delegated MNP regardless of their OMNI link point of origin. These checks are necessary to prevent Clients from either accidentally or intentionally establishing endless loops that could congest Proxy/Servers and/or ANET/INET links.¶

Note: Proxy/Servers forward secure control plane carrier packets via the SRT secured spanning tree and forward other carrier packets via the unsecured spanning tree. When a Proxy/Server receives a carrier packet from the secured spanning tree, it considers the message as authentic without having to verify upper layer authentication signatures. When a Proxy/Server receives a carrier packet from the unsecured spanning tree, it applies data origin authentication itself and/or forwards the unsecured message toward the destination which must apply data origin authentication on its own behalf.¶

Note: If the Proxy/Server has multiple original IP packets to send to the same neighbor, it can concatenate them in a single OAL super-packet [I-D.templin-6man-omni].¶

3.10.4. Gateway Forwarding Algorithm

Gateways forward spanning tree carrier packets while decrementing the OAL header Hop Count but not the original IP header Hop Count/TTL. Gateways convey carrier packets that encapsulate critical IPv6 ND control messages or routing protocol control messages via the SRT secured spanning tree, and may convey other carrier packets via the secured/unsecured spanning tree or via more direct paths according to MFIB information. When the Gateway receives a carrier packet, it removes the L2 headers and searches for an MFIB entry that matches an MFVI or an IP forwarding table entry that matches the OAL destination address.¶

Gateways process carrier packets with OAL destinations that do not match their RND-ULA or the SRT Subnet Router Anycast address in the same manner as for traditional IP forwarding within the OAL, i.e., nodes use IP forwarding to forward packets not explicitly addressed to themselves. Gateways process carrier packets with their RND-ULA or the SRT Subnet Router Anycast address as the destination by first examining the packet for a full OAL header with a CRH-32 extension or an OCH header. In that case, the Gateway examines the next MFVI in the carrier packet to locate the MFV entry in the MFIB for next hop forwarding (i.e., without examining IP addresses). When the Gateway forwards the carrier packet, it changes the destination address according to the MFVI value for the next hop found either in the CRH-32 header or in the node's own MFIB. If the Gateway has a NCE for the target Client with an entry for the target underlay interface and current L2 addresses, the Gateway instead forwards directly to the target Client while using the final hop MFVI instead of the next hop (see: Section 3.13.4).¶

Gateways forward carrier packets received from a first segment via the secured spanning tree to the next segment also via the secured spanning tree. Gateways forward carrier packets received from a first segment via the unsecured spanning tree to the next segment also via the unsecured spanning tree. Gateways use a single IPv6 routing table that always determines the same next hop for a given OAL destination, where the secured/unsecured spanning tree is determined through the selection of the underlay interface to be used for transmission (i.e., a secured tunnel or an open INET interface).¶

As for Proxy/Servers, Gateways must verify that the L2 addresses of carrier packets not received from the secured spanning tree are "trusted" before forwarding according to an MFV (otherwise, the carrier packet must be dropped).¶

3.12.1. AERO Service Model

Each AERO Proxy/Server on the OMNI link is configured to facilitate Client prefix delegation/registration requests. Each Proxy/Server is provisioned with a database of MNP-to-Client ID mappings for all Clients enrolled in the AERO service, as well as any information necessary to authenticate each Client. The Client database is maintained by a central administrative authority for the OMNI link and securely distributed to all Proxy/Servers, e.g., via the Lightweight Directory Access Protocol (LDAP) [RFC4511], via static configuration, etc. Clients receive the same service regardless of the Proxy/Servers they select.¶

Clients associate each of their ANET/INET underlay interfaces with a FHS Proxy/Server. Each FHS Proxy/Server locally services one or more of the Client's underlay interfaces, and the Client typically selects one among them to serve as the Hub Proxy/Server (the Client may instead select a "third-party" Hub Proxy/Server that does not directly service any of its underlay interfaces). All of the Client's other FHS Proxy/Servers forward proxyed copies of RS/RA messages between the Hub Proxy/Server and Client without assuming the Hub role functions themselves.¶

Each Client associates with a single Hub Proxy/Server at a time, while all other Proxy/Servers are candidates for providing the Hub role for other Clients. An FHS Proxy/Server assumes the Hub role when it receives an RS message with its own RND-ULA or link-scoped All-Routers multicast as the destination. An FHS Proxy/Server assumes the proxy role when it receives an RS message with the RND-ULA of another Proxy/Server as the destination. (An FHS Proxy/Server can also assume the proxy role when it receives an RS message addressed to link-scoped All-Routers multicast if it can determine the RND-ULA of another Proxy/Server to serve as a Hub.)¶

Hosts and Clients on ENET interfaces associate with an upstream Client on the ENET the same as a Client would associate with an ANET Proxy/Server. In particular, the Host/Client sends an RS message via the ENET which directs the message to the upstream Client. The upstream Client returns an RA message. In this way, the downstream nodes see the ENET as an ANET and see the upstream Client as a Proxy/Server for that ANET.¶

AERO Hosts, Clients and Proxy/Servers use IPv6 ND messages to maintain neighbor cache entries. AERO Proxy/Servers configure their OMNI interfaces as advertising NBMA interfaces, and therefore send unicast RA messages with a short Router Lifetime value (e.g., ReachableTime seconds) in response to a Client's RS message. Thereafter, Clients send additional RS messages to keep Proxy/Server state alive.¶

AERO Clients and Hub Proxy/Servers include prefix delegation and/or registration parameters in RS/RA messages. The IPv6 ND messages are exchanged between the Client and Hub Proxy/Server (via any FHS Proxy/Servers acting as proxys) according to the prefix management schedule required by the service. If the Client knows its MNP in advance, it can employ prefix registration by including its MNP-XLA as the source address of an RS message and with an OMNI option with valid prefix registration information for the MNP. If the Hub Proxy/Server accepts the Client's MNP assertion, it injects the MNP into the routing system and establishes the necessary neighbor cache state. If the Client does not have a pre-assigned MNP, it can instead employ prefix delegation by including a TMP-ULA as the source address of an RS message and with an OMNI option with prefix delegation parameters to request an MNP.¶

The following sections outlines Host, Client and Proxy/Server behaviors based on the Router Discovery and Prefix Registration specifications found in Section 15 of [I-D.templin-6man-omni]. These sections observe all of the OMNI specifications, and include additional specifications of the interactions of Client-Proxy/Server RS/RA exchanges with the AERO mobility service.¶

3.12.2. AERO Host and Client Behavior

AERO Hosts and Clients discover the addresses of candidate Proxy/Servers by resolving the Potential Router List (PRL) in a similar manner as described in [RFC5214]. Discovery methods include static configuration (e.g., a flat-file map of Proxy/Server addresses and locations), or through an automated means such as Domain Name System (DNS) name resolution [RFC1035]. Alternatively, the Host/Client can discover Proxy/Server addresses through a layer 2 data link login exchange, or through an RA response to a multicast/anycast RS as described below. In the absence of other information, the Host/Client can resolve the DNS Fully-Qualified Domain Name (FQDN) "linkupnetworks.[domainname]" where "linkupnetworks" is a constant text string and "[domainname]" is a DNS suffix for the OMNI link (e.g., "example.com"). The name resolution returns a set of resource records with Proxy/Server address information.¶

The Host/Client then performs RS/RA exchanges over each of its underlay interfaces to associate with (possibly multiple) FHS Proxy/Serves and a single Hub Proxy/Server as specified in Section 15 of [I-D.templin-6man-omni]. The Host/Client then sends each RS (either directly via Direct interfaces, via a VPN for VPNed interfaces, via an access router for ANET interfaces or via INET encapsulation for INET interfaces) and waits up to RetransTimer milliseconds for an RA message reply (see Section 3.12.3) while retrying up to MAX_RTR_SOLICITATIONS if necessary. If the Host/Client receives no RAs, or if it receives an RA with Router Lifetime set to 0, the Client SHOULD abandon attempts through the first candidate Proxy/Server and try another Proxy/Server.¶

After the Host/Client registers its underlay interfaces, it may wish to change one or more registrations, e.g., if an interface changes address or becomes unavailable, if traffic selectors change, etc. To do so, the Host/Client prepares an RS message to send over any available underlay interface as above. The RS includes an OMNI option with prefix registration/delegation information and with an Interface Attributes sub-option specific to the selected underlay interface. When the Host/Client receives the Hub Proxy/Server's RA response, it has assurance that both the Hub and FHS Proxy/Servers have been updated with the new information.¶

If the Host/Client wishes to discontinue use of a Hub Proxy/Server it issues an RS message over any underlay interface with an OMNI option with a prefix release indication (i.e., by setting the OMNI Neighbor Coordination header Preflen to 0). When the Hub Proxy/Server processes the message, it releases the MNP, sets the NCE state for the Host/Client to DEPARTED and returns an RA reply with Router Lifetime set to 0. After a short delay (e.g., 2 seconds), the Hub Proxy/Server withdraws the MNP from the routing system. (Alternatively, when the Host/Client associates with a new FHS/Hub Proxy/Server it can include an OMNI "Proxy/Server Departure" sub-option in RS messages with the ULAs of the Old FHS/Hub Proxy/Servers.)¶

3.12.3. AERO Proxy/Server Behavior

AERO Proxy/Servers act as both IP routers and IPv6 ND proxys, and support a prefix delegation/registration service for Clients. Proxy/Servers arrange to add their RND-ULAs to the PRL maintained in a static map of Proxy/Server addresses for the link, the DNS resource records for the FQDN "linkupnetworks.[domainname]", etc. before entering service. The PRL should be arranged such that Clients can discover the addresses of Proxy/Servers that are geographically and/or topologically "close" to their underlay network connections.¶

When a FHS/Hub Proxy/Server receives a prospective Client's RS message, it SHOULD return an immediate RA reply with Router Lifetime set to 0 if it is currently too busy or otherwise unable to service the Client; otherwise, it processes the RS as specified in Section 15 of [I-D.templin-6man-omni]. When the Hub Proxy/Server receives the RS, it determines the correct MNPs to provide to the Client by processing the MNP-XLA prefix parameters and/or the DHCPv6 OMNI sub-option. When the Hub Proxy/Server returns the MNPs, it also creates a forwarding table entry for the MNP resulting in a BGP update (see: Section 3.2.3). For IPv6, the Hub Proxy/Server creates an IPv6 forwarding table entry based on a standard IPv6 GUA of ULA prefix no longer than /64. For IPv4, the Hub Proxy/Server creates an IPv6 forwarding table entry based on an IPv4-Compatible IPv6 prefix corresponding to the IPv4 address. The Hub Proxy/Server then returns an RA to the Client with destination set to the source of the RS (if an FHS Proxy/Server on the return path proxys the RA, it changes the destination to the Client's MNP-ULA).¶

After the initial RS/RA exchange, the Hub Proxy/Server maintains a ReachableTime timer for each of the Client's underlay interfaces individually (and for the Client's NCE collectively) set to expire after ReachableTime seconds. If the Client (or an FHS Proxy/Server) issues additional RS messages, the Hub Proxy/Server sends an RA response and resets ReachableTime. If the Hub Proxy/Server receives an IPv6 ND message with a prefix release indication it sets the Client's NCE to the DEPARTED state and withdraws the MNP route from the routing system after a short delay (e.g., 2 seconds). If ReachableTime expires before a new RS is received on an individual underlay interface, the Hub Proxy/Server marks the interface as DOWN. If ReachableTime expires before any new RS is received on any individual underlay interface, the Hub Proxy/Server sets the NCE state to STALE and sets a 10 second timer. If the Hub Proxy/Server has not received a new RS or uNA message with a prefix release indication before the 10 second timer expires, it deletes the NCE and withdraws the MNP-XLA from the routing system.¶

The Hub Proxy/Server processes any IPv6 ND messages pertaining to the Client while forwarding to the Client or responding on the Client's behalf as necessary. The Hub Proxy/Server may also issue unsolicited RA messages, e.g., with reconfigure parameters to cause the Client to renegotiate its prefix delegation/registrations, with Router Lifetime set to 0 if it can no longer service this Client, etc. The Hub Proxy/Server may also receive carrier packets via the secured spanning tree that contain initial data packets sent while route optimization is in progress. The Hub Proxy/Server reassembles, then re-encapsulates/re-fragments and forwards the packets to the target Client via an FHS Proxy/Server if necessary. Finally, If the NCE is in the DEPARTED state, the old Hub Proxy/Server forwards any carrier packets it receives from the secured spanning tree and destined to the Client to the new Hub Proxy/Server, then deletes the entry after DepartTime expires.¶

Note: Clients SHOULD arrange to notify former Hub Proxy/Servers of their departures, but Hub Proxy/Servers are responsible for expiring neighbor cache entries and withdrawing MNP-XLA routes even if no departure notification is received (e.g., if the Client leaves the network unexpectedly). Hub Proxy/Servers SHOULD therefore set Router Lifetime to ReachableTime seconds in solicited RA messages to minimize persistent stale cache information in the absence of Client departure notifications. A short Router Lifetime also ensures that proactive RS/RA messaging between Clients and FHS Proxy/Servers will keep any NAT state alive (see above).¶

Note: All Proxy/Servers on an OMNI link MUST advertise consistent values in the RA Cur Hop Limit, M and O flags, Reachable Time and Retrans Timer fields the same as for any link, since unpredictable behavior could result if different Proxy/Servers on the same link advertised different values.¶

3.13.1. Multilink Address Resolution

When one or more original IP packets from a source node destined to a target node arrives, the ROS checks for a NCE with an MNP-XLA that matches the target destination. If there is a NCE in the REACHABLE state, the ROS invokes the OAL and forwards the resulting carrier packets according to the cached state then returns from processing. Otherwise, if there is no NCE the ROS creates one in the INCOMPLETE state.¶

The ROS next prepares an NS message for Address Resolution (NS(AR)) to send toward an ROR while including the original IP packet(s) as trailing data following the NS(AR) in an OAL super-packet [I-D.templin-6man-omni]. The resulting NS(AR) message must be sent securely, and includes:¶

• the ULA of the ROS as the source address.¶
• the MNP-XLA corresponding to the original IP packet's destination as the Target Address, e.g., for 2001:db8:1:2::10:2000 the Target Address is fd00::2001:db8:1:2.¶
• the Solicited-Node multicast address [RFC4291] formed from the lower 24 bits of the original IP packet's destination as the destination address, e.g., for 2001:db8:1:2::10:2000 the NS(AR) destination address is ff02:0:0:0:0:1:ff10:2000.¶

The NS(AR) message also includes an OMNI option with an authentication sub-option if necessary and with OMNI extension header Preflen set to the prefix length associated with the NS(AR) source. The ROS also includes Interface Attributes and Traffic Selectors for all of the source Client's underlay interfaces, calculates the authentication signature or checksum, then selects an Identification value and submits the NS(AR) message for OAL encapsulation with OAL source set to its own {ADM,MNP}-ULA and OAL destination set to the MNP-XLA corresponding to the target and with window synchronization parameters. The ROS then inserts a fragment header, performs fragmentation and L2 encapsulation, then sends the resulting carrier packets into the SRT secured spanning tree without decrementing the network-layer TTL/Hop Limit field.¶

When the ROS is a Client, it must instead use the RND-ULA of one of its FHS Proxy/Servers as the OAL destination. The ROS Client then fragments, performs L2 encapsulation and forwards the carrier packets to the FHS Proxy/Server. The FHS Proxy/Server then reassembles, verifies the NS(AR) authentication signature or checksum, changes the OAL source to its own RND-ULA, changes the OAL destination to the MNP-XLA corresponding to the target, selects an appropriate Identification, then re-fragments and forwards the resulting carrier packets into the secured spanning tree on behalf of the Client.¶

Note: both the target Client and its Hub Proxy/Server include current and accurate information for the Client's multilink Interface Attributes profile. The Hub Proxy/Server can be trusted to provide an authoritative response on behalf of the Client should the need arise. While the Client has no such trust basis, any attempt by the Client to mount an attack by providing false Interface Attributes information would only result in black-holing of return traffic, i.e., the "attack" could only result in denial of service to the Client itself. Therefore, the Client's asserted Interface Attributes need not be validated by the Hub Proxy/Server.¶

3.13.2. Multilink Route Optimization

Following address resolution, the ROS and ROR can assert multilink paths through underlay interface pairs serviced by the same source/destination ULAs by sending unicast NS/NA messages with Multilink Forwarding Parameters and OMNI Neighbor Coordination window synchronization parameters when necessary. The unicast NS/NA messages establish multilink forwarding state in intermediate nodes in the path between the ROS and ROR.¶

To support multilink route optimization, OMNI interfaces include an additional forwarding table termed the Multilink Forwarding Information Base (MFIB) that supports carrier packet forwarding based on OMNI neighbor underlay interface pairs. The MFIB contains Multilink Forwarding Vectors (MFVs) indexed by 4-octet values known as MFV Indexes (MFVIs).¶

OAL source, intermediate and destination nodes create MFVs/MFVIs when they process an NS message with a Multilink Forwarding Parameters sub-option with Job code '00' (Initialize; Build B) or a solicited NA with Job code '01' (Follow B; Build A) (see: [I-D.templin-6man-omni]). The OAL source of the NS (and OAL destination of the solicited NA) are considered to reside in the "First Hop Segment (FHS)", while the OAL destination of the NS (and OAL source of the solicited NA) are considered to reside in the "Last Hop Segment (LHS)".¶

When an OAL node processes an NS with Job code '00', it creates an MFV, records the NS source and destination ULAs and assigns a "B" MFVI. When the "B" MVFI is referenced, the MVF retains the ULAs in (dst,src) order the opposite of how they appeared in the original NS to support full header reconstruction. (If the NS message included a nested OAL encapsulation, the ULAs of both OAL headers are retained.)¶

When an OAL node processes a solicited NA with Job code '01', it locates the MFV created by the NS and assigns an "A" MFVI. When the "A" MFVI is referenced, the MFV retains the ULAs in (src,dst) order the same as they appeared in the original NS to support full header reconstruction. (If the NS message included a nested OAL encapsulation, the ULAs of both OAL headers are retained.)¶

OAL nodes generate random 32-bit values as candidate A/B MFVIs which must first be tested for local uniqueness. If a candidate MFVI s already in use (or if the value is 0), the OAL node repeats the random generation process until it obtains a unique non-zero value. (Since the number of MFVs in service at each OAL node is likely to be much smaller than 2**32, the process will generate a unique value after a small number of tries; also, an MFVI generated by a first OAL node is never tested for uniqueness on other OAL nodes, since the uniqueness property is node-local only.)¶

OAL nodes maintain A/B MFVIs as follows:¶

• "B1" - a locally-unique MFVI maintained independently by each OAL node on the path from the FHS OAL source to the last OAL intermediate node before the LHS OAL destination. The OAL node generates and assigns a "B1" MFVI to a newly-created MFV when it processes an NS message with Job code '00'. When the OAL node receives future carrier packets that include this value, it can unambiguously locate the correct MFV and determine directionality without examining addresses.¶
• "A1" - a locally unique MFVI maintained independently by each OAL node on the path from the LHS OAL source to the last OAL intermediate node before the FHS OAL destination. The OAL node generates and assigns an "A1" MFVI to the MVF that configures the corresponding "B1" MFVI when it processes a solicited NA message with Job code '01'. When the OAL node receives future carrier packets that include this value, it can unambiguously locate the correct MFV and determine directionality without examining addresses.¶
• "A2" - the A1 MFVI of a remote OAL node discovered by an FHS OAL source or OAL intermediate node when it processes an NA message with Job code '01' that originated from an LHS OAL source. A2 values MUST NOT be tested for uniqueness within the OAL node's local context.¶
• "B2" - the B1 MFVI of a remote OAL node discovered by an LHS OAL source or OAL intermediate node when it processes an NS message with Job code '00' that originated from an FHS OAL source. B2 values MUST NOT be tested for uniqueness within the OAL node's local context.¶

When an FHS OAL source has an original IP packet to send to an LHS OAL destination discovered via multilink address resolution, it first selects a source and target underlay interface pair. The OAL source uses its cached information for the target underlay interface as LHS information then prepares an NS message with an OMNI Multilink Forwarding Parameters sub-option with Job code '00' and with source set to its own RND-ULA or MNP-XLA. If the LHS FMT-Forward and FMT-Mode bits are both clear, the OAL source sets the destination to the RND-ULA of the LHS Proxy/Server; otherwise, it sets the destination to the MNP-XLA of the target Client. The OAL source then sets window synchronization information in the OMNI Neighbor Coordination header and creates a NCE for the selected destination RND-ULA or MNP-XLA in the INCOMPLETE state. The OAL source next creates an MFV based on the NS source and destination ULAs, then generates a "B1" MFVI and assigns it to the MFV while also including it as the first B entry in the MFVI List. The OAL source then populates the NS Multilink Forwarding Parameters based on any FHS/LHS information it knows locally. OAL intermediate nodes on the path to the OAL destination may populate additional FHS/LHS information on a hop-by-hop basis.¶

If the OAL source is the FHS Proxy/Server, it then performs OAL encapsulation/fragmentation while setting the source to its own RND-ULA and setting the destination to the FHS Subnet Router Anycast ULA determined by applying the FHS SRT prefix length to its RND-ULA. The FHS Proxy/Server next examines the LHS FMT code. If FMT-Forward is clear and FMT-Mode is set, the FHS Proxy/Server checks for a NCE for the RND-ULA of the LHS Proxy/Server. If there is no NCE, the FHS Proxy/Server creates one in the INCOMPLETE state. If a new NCE was created (or if the existing NCE requires fresh window synchronization), the FHS Proxy/Server then writes window synchronization parameters into the OMNI Multilink Forwarding Parameters Tunnel Window Synchronization fields. The FHS Proxy/Server then selects an appropriate Identification value and L2 headers and forwards the resulting carrier packets into the secured spanning tree which will deliver them to a Gateway interface that assigns the FHS Subnet Router Anycast ULA.¶

If the OAL source is the FHS Client, it instead includes an authentication signature if necessary, performs OAL encapsulation, sets the source to its own MNP-ULA, sets the destination to the RND-ULA of the FHS Proxy/Server and selects an appropriate Identification value for the FHS Proxy/Server. If FHS FMT-Forward is set and LHS FMT-Forward is clear, the FHS Client creates/updates a NCE for the RND-ULA of the LHS Proxy/Server as above and includes Tunnel Window Synchronization parameters. The FHS Client then fragments and encapsulates in appropriate L2 headers then forwards the carrier packets to the FHS Proxy/Server. When the FHS Proxy/Server receives the carrier packets, it verifies the Identification, reassembles/decapsulates to obtain the NS then verifies the authentication signature or checksum. The FHS Proxy/Server then creates an MFV (i.e., the same as the FHS Client had done) while assigning the current B entry in the MFVI List (i.e., the one included by the FHS Client) as the "B2" MFVI for this MVF. The FHS Proxy/Server next generates a new unique "B1" MFVI, then both assigns it to the MFV and writes it as the next B entry in the OMNI Multilink Forwarding Parameters MFVI List (while also writing any FHS Client and Proxy/Server addressing information). The FHS Proxy/Server then checks FHS/LHS FMT-Forward/Mode to determine whether to create a NCE for the LHS Proxy/Server RND-ULA and include Tunnel Window Synchronization parameters the same as above. The FHS Proxy/Server then calculates the checksum, re-fragments while setting the OAL source address to its own RND-ULA and destination address to the FHS Subnet Router Anycast ULA, and includes an Identification appropriate for the secured spanning tree. The FHS Proxy/Server finally includes appropriate L2 headers and forwards the carrier packets into the secured spanning tree the same as above.¶

Gateways in the spanning tree forward carrier packets not explicitly addressed to themselves, while forwarding those that arrived via the secured spanning tree to the next hop also via the secured spanning tree and forwarding all others via the unsecured spanning tree. When an FHS Gateway receives a carrier packet over the secured spanning tree addressed to its RND-ULA or the FHS Subnet Router Anycast ULA, it instead reassembles/decapsulates to obtain the NS then verifies the checksum. The FHS Gateway next creates an MFV (i.e., the same as the FHS Proxy/Server had done) while assigning the current B entry in the MFVI List as the MFV "B2" index. The FHS Gateway also caches the NS Multilink Forwarding Parameters FHS information in the MFV, and also caches the first B entry in the MFVI List as "FHS-Client" when FHS FMT-Forward/Mode are both set to enable future direct forwarding to this FHS Client. The FHS Gateway then generates a "B1" MFVI for the MFV and also writes it as the next B entry in the NS's MFVI List.¶

The FHS Gateway then examines the SRT prefixes corresponding to both FHS and LHS. If the FHS Gateway has a local interface connection to both the FHS and LHS (whether they are the same or different segments), the FHS/LHS Gateway caches the NS LHS information, writes its RND-ULA suffix and LHS INADDR into the NS OMNI Multilink Forwarding Parameters LHS fields, then sets its own RND-ULA as the source and the RND-ULA of the LHS Proxy/Server as the destination while selecting an appropriate identification. If the FHS and LHS prefixes are different, the FHS Gateway instead sets the LHS Subnet Router Anycast ULA as the destination. The FHS Gateway then recalculates the NS checksum, selects an appropriate Identification and L2 headers as above then forwards the carrier packets into the secured spanning tree.¶

When the FHS and LHS Gateways are different, the LHS Gateway will receive carrier packets over the secured spanning tree from the FHS Gateway. The LHS Gateway reassembles/decapsulates to obtain the NS then verifies the checksum and creates an MFV (i.e., the same as the FHS Gateway had done) while assigning the current B entry in the MFVI List as the MFV "B2" index. The LHS Gateway also caches the RND-ULA of the FHS Gateway found in the Multilink Forwarding Parameters as the spanning tree address for "B2", caches the NS Multilink Forwarding Parameters LHS information then generates a "B1" MFVI for the MFV while also writing it as the next B entry in the MFVI List. The LHS Gateway also writes its own RND-ULA suffix and LHS INADDR into the OMNI Multilink Forwarding Parameters. The LHS Gateway then sets the its own RND-ULA as the source and the RND-ULA of the LHS Proxy/Server as the OAL destination, recalculates the checksum, selects an appropriate Identification, then fragments while including appropriate L2 headers and forwards the carrier packets into the secured spanning tree.¶

When the LHS Proxy/Server receives the carrier packets from the secured spanning tree, it reassembles/decapsulates to obtain the NS, verifies the checksum then verifies that the LHS information supplied by the FHS source is consistent with its own cached information. If the information is consistent, the LHS Proxy/Server then creates an MFV and assigns the current B entry in the MFVI List as the "B2" MFVI the same as for the prior hop. If the NS destination is the MNP-XLA of the target Client, the LHS Proxy/Server also generates a "B1" MFVI and assigns it both to the MFVI and as the next B entry in the MFVI List. The LHS Proxy/Server then examines FHS FMT; if FMT-Forward is clear and FMT-Mode is set, the LHS Proxy/Server creates a NCE for the RND-ULA of the FHS Proxy/Server (if necessary) and sets the state to STALE, then caches any Tunnel Window Synchronization parameters.¶

If the NS destination is its own RND-ULA, the LHS Proxy/Server next prepares to return a solicited NA with Job code '01'. If the NS source was the MNP-XLA of the FHS Client, the LHS Proxy/Server first creates or updates an NCE for the MNP-XLA with state set to STALE. The LHS Proxy/Server next caches the NS OMNI Neighbor Coordination header window synchronization parameters and Multilink Forwarding Parameters information (including the MFVI List) in the NCE corresponding to the ULA source. When the LHS Proxy/Server forwards future carrier packets based on the NCE, it can populate reverse-path forwarding information in a CRH-32 routing header to enable forwarding based on the cached MFVI List B entries instead of ULA addresses.¶

The LHS Proxy/Server then creates an NA with Job code '01' while copying the NS OMNI Multilink Forwarding Parameters FHS/LHS information into the corresponding fields in the NA. The LHS Proxy/Server then generates an "A1" MFVI and both assigns it to the MFV and includes it as the first A entry in NA's MFVI List (see: [I-D.templin-6man-omni] for details on MFVI List A/B processing). The LHS Proxy/Server then includes end-to-end window synchronization parameters in the OMNI Neighbor Coordination header (if necessary) and also tunnel window synchronization parameters in the Multilink Forwarding Parameters (if necessary). The LHS Proxy/Server then encapsulates the NA, calculates the checksum, sets the source to its own RND-ULA, sets the destination to the RND-ULA of the LHS Gateway, selects an appropriate Identification value and L2 headers then forwards the carrier packets into the secured spanning tree.¶

If the NS destination was the MNP-XLA of the LHS Client, the LHS Proxy/Server instead includes an authentication signature in the NS if necessary (otherwise recalculates the checksum), then changes the OAL source to its own RND-ULA and changes the destination to the MNP-ULA of the LHS Client. The LHS Proxy/Server then selects an appropriate Identification value, fragments if necessary, includes appropriate L2 headers and forwards the carrier packets to the LHS Client. When the LHS Client receives the carrier packets, it verifies the Identification and reassembles/decapsulates to obtain the NS then verifies the authentication signature or checksum. The LHS Client then creates a NCE for the NS ULA source address in the STALE state. If LHS FMT-Forward is set, FHS FMT-Forward is clear and the NS source was an MNP-XLA, the Client also creates a NCE for the RND-ULA of the FHS Proxy/Server in the STALE state and caches any Tunnel Window Synchronization parameters. The Client then caches the NS OMNI Neighbor Coordination header window synchronization parameters and Multilink Forwarding Parameters in the NCE corresponding to the NS ULA source, then creates an MFV and assigns both the current MFVI List B entry as "B2" and a locally generated "A1" MFVI the same as for previous hops (the LHS Client also includes the "A1" value in the solicited NA - see above and below). The LHS Client also caches the previous MFVI List B entry as "LHS-Gateway" since it can include this value when it sends future carrier packets directly to the Gateway (following appropriate neighbor coordination).¶

The LHS Client then prepares an NA using exactly the same procedures as for the LHS Proxy/Server above, except that it uses its MNP-XLA as the source and the RND-ULA or MNP-XLA of the FHS correspondent as the destination. The LHS Client also includes an authentication signature if necessary (otherwise calculates the checksum), then encapsulates the NA with OAL source set to its own MNP-ULA and destination set to the RND-ULA of the LHS Proxy/Server, includes an appropriate Identification and L2 headers and forwards the carrier packets to the LHS Proxy/Server. When the LHS Proxy/Server receives the carrier packets, it verifies the Identifications, reassembles/decapsulates to obtain the NA, verifies the authentication signature or checksum, then uses the current MVFI List B entry to locate the MFV. The LHS Proxy/Server then writes the current MFVI List A entry as the "A2" value for the MVF, generates an "A1" MFVI and both assigns it to the MFV and writes it as the next MFVI List A entry. The LHS Proxy/Server then examines the FHS/LHS FMT codes to determine if it needs to include Tunnel Window Synchronization parameters. The LHS Proxy/Server then recalculates the checksum, re-fragments the NA while setting the OAL source to its own RND-ULA and destination to the RND-ULA of the LHS Gateway, includes an appropriate Identification and L2 headers and forwards the carrier packets into the secured spanning tree.¶

When the LHS Gateway receives the carrier packets, it reassembles/decapsulates to obtain the NA while verifying the checksum then uses the current MFVI List B entry to locate the MFV. The LHS Gateway then writes the current MFVI List A entry as the MFV "A2" index and generates a new "A1" value which it both assigns the MFV and writes as the next MFVI List A entry. (The LHS Gateway also caches the first A entry in the MFVI List as "LHS-Client" when LHS FMT-Forward/Mode are both set to enable future direct forwarding to this LHS Client.) If the LHS Gateway is connected directly to both the FHS and LHS segments (whether the segments are the same or different), the FHS/LHS Gateway will have already cached the FHS/LHS information based on the original NS. The FHS/LHS Gateway recalculates the checksum then re-fragments the NA while setting the OAL source to its own RND-ULA and destination to the RND-ULA of the FHS Proxy/Server. If the FHS and LHS prefixes are different, the FHS Gateway instead re-fragments while setting the destination to the RND-ULA of the FHS Gateway. The LHS Gateway selects an appropriate Identification and L2 headers then forwards the carrier packets into the secured spanning tree.¶

When the FHS and LHS Gateways are different, the FHS Gateway will receive the carrier packets from the LHS Gateway over the secured spanning tree. The FHS Gateway reassembles/decapsulates to obtain the NA while verifying the checksum, then locates the MFV based on the current MFVI List B entry. The FHS Gateway then assigns the current MFVI List A entry as the MFV "A2" index and caches the RND-ULA of the LHS Gateway as the spanning tree address for "A2". The FHS Gateway then generates an "A1" MVFI and both assigns it to the MVF and writes it as the next MFVI List A entry while also writing its RND-ULA and INADDR in the NA FHS Gateway fields. The FHS Gateway then recalculates the checksum, re-encapsulates/re-fragments with its own RND-ULA as the source, with the RND-ULA of the FHS Proxy/Server as the destination, then selects an appropriate Identification value and L2 headers and forwards the carrier packets into the secured spanning tree.¶

When the FHS Proxy/Server receives the carrier packets from the secured spanning tree, it reassembles/decapsulates to obtain the NA while verifying the checksum then locates the MFV based on the current MFVI List B entry. The FHS Proxy/Server then assigns the current MFVI List A entry as the "A2" MFVI the same as for the prior hop. If the NA destination is its own RND-ULA, the FHS Proxy/Server then caches the NA Multilink Forwarding Parameters with the MFV and examines LHS FMT. If FMT-Forward is clear, the FHS Proxy/Server locates the NCE for the RND-ULA of the LHS Proxy/Server and sets the state to REACHABLE then caches any Tunnel Window Synchronization parameters. If the NA source is the MNP-XLA of the LHS Client, the FHS Proxy/Server then locates the LHS Client NCE and sets the state to REACHABLE then caches the OMNI Neighbor Coordination header window synchronization parameters and prepares to return an NA acknowledgement, if necessary.¶

If the NA destination is the MNP-XLA of the FHS Client, the FHS Proxy/Server also searches for and updates the NCE for the RND-ULA of the LHS Proxy/Server if necessary the same as above. The FHS Proxy/Server then generates an "A1" MFVI and assigns it both to the MFVI and as the next MFVI List A entry, then includes an authentication signature or checksum in the NA message. The FHS Proxy/Server then sets the OAL source to its own RND-ULA and sets the destination to the MNP-ULA of the FHS Client, then selects an appropriate Identification value and L2headers and forwards the carrier packets to the FHS Client.¶

When the FHS Client receives the carrier packets, it verifies the Identification, reassembles/decapsulates to obtain the NA, verifies the authentication signature or checksum, then locates the MFV based on the current MFVI List B entry. The FHS Client then assigns the current MFVI List A entry as the "A2" MFVI the same as for the prior hop. The FHS Client then caches the NA Multilink Forwarding Parameters (including the MFVI List) with the MFV and examines LHS FMT. If FMT-Forward is clear, the FHS Client locates the NCE for the RND-ULA of the LHS Proxy/Server and sets the state to REACHABLE then caches any Tunnel Window Synchronization parameters. If the NA source is the MNP-XLA of the LHS Client, the FHS Proxy/Server then locates the LHS Client NCE and sets the state to REACHABLE then caches the OMNI Neighbor Coordination header window synchronization parameters and prepares to return an NA acknowledgement, if necessary. The FHS Client also caches the previous MFVI List A entry as "FHS-Gateway" since it can include this value when it sends future carrier packets directly to the Gateway (following appropriate neighbor coordination).¶

If either the FHS Client or FHS Proxy/Server needs to return an acknowledgement to complete window synchronization, it prepares a uNA message with an OMNI Multilink Forwarding Parameters sub-option with Job code set to '10' (Follow A; Record B) (note that this step is unnecessary when Rapid Commit route optimization is used per Section 3.13.3). The FHS node sets the source to its own RND-ULA or MNP-XLA, sets the destination to the RND-ULA or MNP-XLA of the LHS node then includes Tunnel Window Synchronization parameters if necessary. The FHS node next sets the MFVI List to the cached list of A entries received in the Job code '01' NA, but need not set any other FHS/LHS information. The FHS node then encapsulates the uNA message in an OAL header with its own {ADM,MNP}-ULA as the source. If the FHS node is the Client, it next sets the RND-ULA of the FHS Proxy/Server as the OAL destination, includes an authentication signature or checksum, selects an appropriate Identification value and L2 headers and forwards the carrier packets to the FHS Proxy/Server. The FHS Proxy/Server then verifies the Identification, reassembles/decapsulates, verifies the authentication signature or checksum, then uses the current MFVI List A entry to locate the MFV. The FHS Proxy/Server then writes its "B1" MFVI as the next MFVI List B entry and determines whether it needs to include Tunnel Window Synchronization parameters the same as it had done when it forwarded the original NS.¶

The FHS Proxy/Server recalculates the uNA checksum then re-fragments while setting its own RND-ULA as the source and the RND-ULA of the FHS Gateway as the destination, then selects an appropriate Identification and L2 headers and forwards the carrier packets into the secured spanning tree. When the FHS Gateway receives the carrier packets, it reassembles/decapsulates to obtain the uNA while verifying the checksum then uses the current MFVI List A entry to locate the MFV. The FHS Gateway then writes its "B1" MFVI as the next MFVI List B entry, then re-fragments while setting the OAL source and destination. If the FHS Gateway is also the LHS Gateway, it sets the RND-ULA of the LHS Proxy/Server as the destination; otherwise it sets the RND-ULA of the LHS Gateway. The FHS Gateway recalculates the checksum then selects an appropriate Identification and L2 headers, re-fragments/forwards the carrier packets into the secured spanning tree. If an LHS Gateway receives the carrier packets, it processes them exactly the same as the FHS Gateway had done while setting the carrier packet destination to the RND-ULA of the LHS Proxy/Server.¶

When the LHS Proxy/Server receives the carrier packets, it reassembles/decapsulates to obtain the uNA message while verifying the checksum. The LHS Proxy/Server then locates the MFV based on the current MFVI List A entry then determines whether it is a tunnel ingress the same as for the original NS. If it is a tunnel ingress, the LHS Proxy/Server updates the NCE for the tunnel far-end based on the Tunnel Window Synchronization parameters. If the uNA destination is its own RND-ULA, the LHS Proxy/Server next updates the NCE for the source ULA based on the OMNI Neighbor Coordination header window synchronization parameters and MAY compare the MVFI List to the version it had cached in the MFV based on the original NS.¶

If the uNA destination is the MNP-XLA of the LHS Client, the LHS Proxy/Server instead writes its "B1" MFV as the next MFVI List B entry, includes an authentication signature or checksum, writes its own RND-ULA as the OAL source and the MNP-ULA of the Client as the OAL destination then selects an appropriate Identification and L2 headers and forwards the resulting carrier packets to the LHS Client. When the LHS Client receives the carrier packets, it verifies the Identification, reassembles/decapsulates to obtain the uNA, verifies the authentication signature or checksum then processes the message exactly the same as for the LHS Proxy/Server case above.¶

Following the NS/NA exchange with Multilink Forwarding Parameters, OAL end systems and tunnel endpoints can begin exchanging ordinary carrier packets with Identification values within their respective send/receive windows without requiring security signatures and/or secured spanning tree traversal. Either peer can refresh window synchronization parameters and/or send other carrier packets requiring security at any time using the same secured procedures described above. OAL end systems and intermediate nodes can also use their own A1/B1 MFVIs when they receive carrier packets to unambiguously locate the correct MFV and determine directionality and can use any discovered A2/B2 MFVIs to forward carrier packets to other OAL nodes that configure the corresponding A1/B1 MFVIs. When an OAL node uses an MFVI included in a carrier packet to locate an MFV, it need not also examine the carrier packet addresses.¶

OAL sources can also begin including CRH-32s in carrier packets with a list of A/B MFVIs that OAL intermediate nodes can use for shortest-path carrier packet forwarding based on MFVIs instead of spanning tree addresses. OAL sources and intermediate nodes can also begin forwarding carrier packets with OAL compressed headers termed "OCH" (see: [I-D.templin-6man-omni]) that include only a single A/B MFVI meaningful to the next hop, since all nodes in the path up to (and sometimes including) the OAL destination have already established MFV forwarding information. Note that when an FHS OAL source receives a solicited NA with Job code '01', the message will contain an MFVI List with A entries populated in the reverse order needed for populating a CRH-32 routing header. The FHS OAL source must therefore write the MFVI List A entries last-to-first when it populates a CRH-32, or must select the correct A entry to include in an OCH header based on the intended OAL intermediate node or destination.¶

When a Gateway receives unsecured carrier packets destined to a local segment Client that has asserted direct reachability, the Gateway performs direct carrier packet forwarding while bypassing the local Proxy/Server based on the Client's advertised MFVIs and discovered NATed INADDR information (see: Section 3.13.4). If the Client cannot be reached directly (or if NAT traversal has not yet converged), the Gateway instead forwards carrier packets directly to the local Proxy/Server.¶

When a Proxy/Server receives carrier packets destined to a local Client or forwards carrier packets received from a local Client, it first locates the correct MFV. If the carrier packets include a secured IPv6 ND message, the Proxy/Server uses the Client's NCE established through RS/RA exchanges to re-encapsulate/re-fragment while forwarding outbound secured carrier packets via the secured spanning tree and forwarding inbound secured carrier packets while including an authentication signature or checksum. For ordinary carrier packets, the Proxy/Server uses the same MFV if directed by MFVI and/or OAL addressing. Otherwise it locates an MFV established through an NS/NA exchange between the Client and the remote peer, and forwards the carrier packets without first reassembling/decapsulating.¶

When a Proxy/Server or Client configured as a tunnel ingress receives a carrier packet with a full OAL header with an MNP-ULA source and CRH-32 routing header, or an OCH header with an MFVI that matches an MFV, the ingress encapsulates the carrier packet in a new full OAL header or an OCH header containing the next hop MVFI and an Identification value appropriate for the end-to-end window and the outer header containing an Identification value appropriate for the tunnel endpoints. When a Proxy/Server or Client configured as a tunnel egress receives an encapsulated carrier packet, it verifies the Identification in the outer header, then discards the outer header and forwards the inner carrier packet to the final destination.¶

When a Proxy/Server with FMT-Forward/Mode set to 0/1 for a source Client receives carrier packets from the source Client, it first reassembles to obtain the original OAL packet then re-fragments if necessary to cause the Client's packets to match the MPS on the path from the Proxy/Server as a tunnel ingress to the tunnel egress. The Proxy/Server then performs OAL-in-OAL encapsulation and forwards the resulting carrier packets to the tunnel egress. When a Proxy/Server with FMT-Forward/Mode set to 0/1 for a target Client receives carrier packets from a tunnel ingress, it first decapsulates to obtain the original fragments then reassembles to obtain the original OAL packet. The Proxy/Server then re-fragments if necessary to cause the fragments to match the target Client's underlay interface (Path) MTU and forwards the resulting carrier packets to the target Client.¶

When a source Client forwards carrier packets it can employ header compression according to the MFVIs established through an NS/NA exchange with a remote or local peer. When the source Client forwards to a remote peer, it can forward carrier packets to a local SRT Gateway (following the establishment of INADDR information) while bypassing the Proxy/Server (see: Section 3.13.4). When a target Client receives carrier packets that match a local MFV, the Client first verifies the Identification then decompresses the headers if necessary, reassembles if necessary to obtain the OAL packet then decapsulates and delivers the IP packet to upper layers.¶

When synchronized peer Clients in the same SRT segment with FMT-Forward and FMT-Mode set discover each other's NATed INADDR addresses, they can exchange carrier packets directly with header compression using MFVIs discovered as above (see: Section 3.13.5). The FHS Client will have cached the A MFVI for the LHS Client, which will have cached the B MVFI for the FHS Client.¶

After window synchronization state has been established, the ROS and ROR can begin forwarding carrier packets while performing additional NS/NA exchanges as above to update window state, register new interface pairs for optimized multilink forwarding and/or confirm reachability. The ROS sends carrier packets to the FHS Gateway discovered through the NS/NA exchange. The FHS Gateway then forwards the carrier packets over the unsecured spanning tree to the LHS Gateway, which forwards them via LHS encapsulation to the LHS Proxy/Server or directly to the target Client itself. The target Client in turn sends packets to the ROS in the reverse direction while forwarding through the Gateways to minimize Proxy/Server load whenever possible.¶

While the ROS continues to actively forward packets to the target Client, it is responsible for updating window synchronization state and per-interface reachability before expiration. Window synchronization state is shared by all underlay interfaces in the ROS' NCE that use the same destination ULA so that a single NS/NA exchange applies for all interfaces regardless of the specific interface used to conduct the exchange. However, the window synchronization exchange only confirms target Client reachability over the specific underlay interface pair. Reachability for other underlay interfaces that share the same window synchronization state must be determined individually using additional NS/NA messages.¶

3.13.3. Rapid Commit Route Optimization

When the ROR receives an NS(AR) with a set of Interface Attributes for the source Client, it can perform "rapid commit" by immediately invoking multilink route optimization as above instead of returning an NA(AR). In order to perform rapid commit, the ROR prepares a unicast NS message with an OMNI option with window synchronization information responsive to the NS(AR), with a Multilink Forwarding Parameters sub-option selected for a specific underlay interface pair and with Interface Attributes for all of the ROR's other underlay interfaces. The ROR can also include ordinary IP packets as OAL super-packet extensions to the NS message if it has immediate data to send to the ROS. The ROR then returns the NS to the ROS the same as for the NA(AR) case.¶

When the NS message traverses the return path to the ROR, all intermediate nodes in the path establish state exactly the same as for an ordinary NS/NA multilink route optimization exchange. When the NS message arrives at the ROS, the window synchronization parameters confirm that the NS is taking the place of the NA(AR), thereby eliminating an extraneous message transmission and associated delay. The ROS then completes the route optimization by returning a responsive NA.¶

Note: The ROS must accept unicast NS messages with an ACK matching the SYN included in the NS(AR) as an equivalent message replacement for the NA(AR). Address resolution and multilink forwarding coordination can therefore be coordinated in a single three-way handshake connection with minimal messaging and delay (i.e., as opposed to a four-message exchange).¶

3.13.4. Client/Gateway Route Optimization

Following multilink route optimization for specific underlay interface pairs, ROS/ROR Clients located on open INETs can invoke Client/Gateway route optimization to improve performance and reduce load and congestion on their respective FHS/LHS Proxy/Servers. To initiate Client/Gateway route optimization, the Client prepares an NS message with its own MNP-XLA address as the source and the RND-ULA of its Gateway as the destination while creating a NCE for the Gateway if necessary. The NS message must be no larger than the minimum MPS and encapsulated as an atomic fragment.¶

The Client then includes an Interface Attributes sub-option for its underlay interface as well as an authentication signature but does not include window synchronization parameters. The Client then performs OAL encapsulation with its own MNP-ULA as the source and the RND-ULA of the Gateway as the destination while including a randomly-chosen Identification value, then performs L2 encapsulation on the atomic fragment and sends the resulting carrier packet directly to the Gateway.¶

When the Gateway receives the carrier packet, it verifies the authentication signature then creates a NCE for the Client. The Gateway then caches the L2 encapsulation addresses (which may have been altered by one or more NATs on the path) as well as the Interface Attributes for this Client omIndex, and marks this Client underlay interface as "trusted". The Gateway then prepares an NA reply with its own RND-ULA as the source and the MNP-XLA of the Client as the destination where the NA again must be no larger than the minimum MPS.¶

The Gateway then echoes the Client's Interface Attributes, includes an Origin Indication with the Client's observed L2 addresses and includes an authentication signature. The Gateway then performs OAL encapsulation with its own RND-ULA as the source and the MNP-ULA of the Client as the destination while using the same Identification value that appeared in the NS, then performs L2 encapsulation on the atomic fragment and sends the resulting carrier packet directly to the Client.¶

When the Client receives the NA reply, it caches the carrier packet L2 source address information as the Gateway target address via this underlay interface while marking the interface as "trusted". The Client also caches the Origin Indication L2 address information as its own (external) source address for this underlay interface.¶

After the Client and Gateway have established NCEs as well as "trusted" status for a particular underlay interface pair, each node can begin forwarding ordinary carrier packets intended for this multilink route optimization directly to one another while omitting the Proxy/Server from the forwarding path while the status is "trusted". The NS/NA messaging will have established the correct state in any NATs in the path so that NAT traversal is naturally supported. The Client and Gateway must maintain a timer that watches for activity on the path; if no carrier packets and/or NS/NA messages are sent or received over the path before NAT state is likely to have expired, the underlay interface pair status becomes "untrusted".¶

Thereafter, when the Client forwards a carrier packet with an MFVI toward the Gateway as the next hop, the Client uses the MFVI for the Gateway (discovered during multilink route optimization) instead of the MFVI for its Proxy/Server; the Gateway will accept the packet from the Client if and only if the underlay interface status is trusted and if the MFVI is correct for the next hop toward the final destination. (The same is true in the reverse direction when the Gateway sends carrier packets directly to the Client.)¶

Note that the Client and Gateway each maintain a single NCE, but that the NCE may aggregate multiple underlay interface pairs. Each underlay interface pair may use differing source and target L2 addresses according to NAT mappings, and the "trusted/untrusted" status of each pair must be tested independently. When no "trusted" pairs remain, the NCE is deleted.¶

Note that the above method requires Gateways to participate in NS/NA message authentication signature application and verification. In an alternate approach, the Client could instead exchange NS/NA messages with authentication signatures via its Proxy/Server but addressed to the RND-ULA of the Gateway, and the Proxy/Server and Gateway could relay the messages over the secured spanning tree. However, this would still require the Client to send additional messages toward the L2 address of the Gateway to populate NAT state; hence the savings in complexity for Gateways would result in increased message overhead for Clients.¶

3.13.5. Client/Client Route Optimization

When the ROS/ROR Clients are both located on the same SRT segment, Client-to-Client route optimization is possible following the establishment of any necessary state in NATs in the path. Both Clients will have already established state via their respective shared segment Proxy/Servers (and possibly also the shared segment Gateway) and can begin forwarding packets directly via NAT traversal while avoiding any Proxy/Server and/or Gateway hops.¶

When the ROR/ROS Clients on the same SRT segment perform the initial NS/NA exchange to establish Multilink Forwarding state, they also include an Origin Indication (i.e., in addition to Multilink Forwarding Parameters) with the mapped addresses discovered during the RS/RA exchanges with their respective Proxy/Servers. After the MFV paths have been established, both Clients can begin sending packets via strict MFV paths while establishing a direct path for Client-to-Client route optimization.¶

To establish the direct path, either Client (acting as the source) transmits a bubble to the mapped L2 address for the target Client which primes its local chain of NATs for reception of future packets from that L2 address (see: [RFC4380] and [I-D.templin-6man-omni]). The source Client then prepares an NS message with its own MNP-XLA as the source, with the MNP-XLA of the target as the destination and with an OMNI option with an Interface Attributes sub-option. The source Client then encapsulates the NS in an OAL header with its own MNP-ULA as the source, with the MNP-ULA of the target Client as the destination and with an in-window Identification for the target. The source Client then fragments and encapsulates in L2 headers addressed to its FHS Proxy/Server then forwards the resulting carrier packets to the Proxy/Server.¶

When the FHS Proxy/Server receives the carrier packets, it re-encapsulates and forwards them as unsecured carrier packets according to MFV state where they will eventually arrive at the target Client which can verify that the identifications are within the acceptable window and reassemble if necessary. Following reassembly, the target Client prepares an NA message with its own MNP-XLA as the source, with the MNP-XLA of the source Client as the destination and with an OMNI option with an Interface Attributes sub-option. The target Client then encapsulates the NA in an OAL header with its own MNP-ULA as the source, with the MNP-ULA of the source Client as the destination and with an in-window Identification for the source Client. The target Client then fragments and encapsulates in L2 headers addressed to the source Client's Origin addresses then forwards the resulting carrier packets directly to the source Client.¶

Following the initial NS/NA exchange, both Clients mark their respective (source, target) underlay interface pairs as "trusted" for no more than ReachableTime seconds. While the Clients continue to exchange carrier packets via the direct path avoiding all Proxy/Servers and Gateways, they should perform additional NS/NA exchanges via their local Proxy/Servers to refresh NCE state as well as send additional bubbles to the peer's Origin address information if necessary to refresh NAT state.¶

Note that these procedures are suitable for a widely-deployed but basic class of NATs. Procedures for advanced NAT classes are outlined in [RFC6081], which provides mechanisms that can be employed equally for AERO using the corresponding sub-options specified by OMNI.¶

Note also that each communicating pair of Clients may need to maintain NAT state for peer to peer communications via multiple underlay interface pairs. It is therefore important that Origin Indications are maintained with the correct peer interface and that the NCE may cache information for multiple peer interfaces.¶

Note that the source and target Client exchange Origin information during the secured NS/NA multilink route optimization exchange. This allows for subsequent NS/NA exchanges to proceed using only the Identification value as a data origin confirmation. However, Client-to-Client peerings that require stronger security may also include authentication signatures for mutual authentication.¶

3.13.6. Client-to-Client OMNI Link Extension

Clients may be recursively nested within the ENETs of other Clients. When a Client is the downstream-attached ENET neighbor of an upstream Client, it still supports the route optimization functions discussed above by maintaining an MFIB and assigning MFVI values. When the Client processes an IPv6 ND NS/NA message that includes a Multilink Forwarding Parameters sub-option, it writes its MFVI information as the first/last MFVI list entry the same as for the single Client case discussed above.¶

The Client then forwards the NS/NA message to the next Client in the extended OMNI link toward the FHS/LHS Proxy/Server, which records the MVFI value then overwrites the MFVI list entry with its own MFVI value. This process iteratively continues until the Client that will forward the NS/NA message to the FHS/LHS Proxy/Server is reached, at which point the NS/NA MFVI list entries are populated by the intermediate nodes on the path to the LHS/FHS the same as discussed above.¶

In this way, each Client in the extended OMNI link discovers the A/B MVFIs of the next/previous Client without intruding into the Multilink Forwarding Parameters MFVI list. Therefore the list can remain fixed at 5 entries even though the Client-to-Client OMNI link extension can be arbitrarily long. Therefore, route optimization is not possible between consecutive Client members of the extended OMNI link but becomes possible at the Internetworking border that separates the FHS and LHS elements.¶

3.13.7. Intra-ANET/ENET Route Optimization for AERO Peers

When a Client forwards a packet from a Host or another Client connected to one of its downstream ENETs to a peer within the same downstream ENET, the Client returns an IPv6 ND Redirect message to inform the source that that target can be reached directly. The contents of the Redirect message are the same as specified in [RFC4861].¶

In the same fashion, when a Proxy/Server forwards a packet from a Host or Client connected to one of its downstream ANETs to a peer within the same downstream ANET, the Proxy/Server returns an IPv6 ND Redirect message.¶

All other route optimization functions are conducted per the NS/NA messaging discussed in the previous sections.¶

3.15.1. Mobility Update Messaging

RORs and ROSs accommodate Client mobility and/or multilink change events by sending secured uNA messages to each active neighbor. When an ROR/ROS sends a uNA message, it sets the IPv6 source address to the its own RND-ULA or MNP-XLA, sets the destination address to the neighbor's RND-ULA or MNP-XLA and sets the Target Address to the Client's MNP-XLA. The ROR/ROS also includes an OMNI option with OMNI Neighbor Coordination header Preflen set to the prefix length associated with the Client's MNP-XLA, includes Interface Attributes and Traffic Selectors for the Client's underlay interfaces and includes an authentication signature if necessary. The ROR then sets the uNA R flag to 1, S flag to 0 and O flag to 1, then encapsulates the message in an OAL header with source set to its own ULA and destination set to its FHS Proxy/Server's RND-ULA. When the FHS Proxy/Server receives the uNA, it reassembles, verifies the authentication signature, then changes the destination to the ULA corresponding to the uNA destination and forwards the uNA into the secured spanning tree.¶

As discussed in Section 7.2.6 of [RFC4861], the transmission and reception of uNA messages is unreliable but provides a useful optimization. In well-connected Internetworks with robust data links uNA messages will be delivered with high probability, but in any case the ROR/ROS can optionally send up to MAX_NEIGHBOR_ADVERTISEMENT uNAs to each neighbor to increase the likelihood that at least one will be received. Alternatively, the ROR/ROS can set the PNG flag in the uNA OMNI option header to request a uNA acknowledgement as specified in [I-D.templin-6man-omni].¶

When the ROR/ROS Proxy/Server receives a uNA message prepared as above, if the uNA destination was its own RND-ULA the Proxy/Server uses the included OMNI option information to update its NCE for the target but does not reset ReachableTime since the receipt of a uNA message does not provide confirmation that any forward paths to the target Client are working. If the destination was the MNP-XLA of the ROR/ROS Client, the Proxy/Server instead changes the OAL source to its own RND-ULA, includes an authentication signature if necessary, and includes an in-window Identification for this Client. Finally, if the uNA message PNG flag was set, the node that processes the uNA returns a uNA acknowledgement as specified in [I-D.templin-6man-omni].¶

3.15.2. Announcing Link-Layer Information Changes

When a Client needs to change its underlay Interface Attributes and/or Traffic Selectors (e.g., due to a mobility event), the Client sends an RS message to its Hub Proxy/Server via a first-hop FHS Proxy/Server, if necessary. The RS includes an OMNI option with an Interface Attributes sub-option with the omIndex and with new link quality and any other information.¶

Note that the first FHS Proxy/Server may change due to the underlay interface change. If the Client supplies the address of the former FHS Proxy/Server, the new FHS Proxy/Server can send a departure indication (see below); otherwise, any stale state in the former FHS Proxy/Server will simply expire after ReachableTime expires with no effect on the Hub Proxy/Server.¶

Up to MAX_RTR_SOLICITATIONS RS messages MAY be sent in parallel with sending carrier packets containing user data in case one or more RAs are lost. If all RAs are lost, the Client SHOULD re-associate with a new Proxy/Server.¶

After performing the RS/RA exchange, the Client sends uNA messages to all neighbors the same as described in the previous section.¶

3.15.3. Bringing New Links Into Service

When a Client needs to bring new underlay interfaces into service (e.g., when it activates a new data link), it sends an RS message to the Hub Proxy/Server via a FHS Proxy/Server for the underlay interface (if necessary) with an OMNI option that includes an Interface Attributes sub-option with appropriate link quality values and with link-layer address information for the new link. The Client then again sends uNA messages to all neighbors the same as described above.¶

3.15.4. Deactivating Existing Links

When a Client needs to deactivate an existing underlay interface, it sends a uNA message toward the Hub Proxy/Server via an FHS Proxy/Server with an OMNI option with appropriate Interface Attributes values for the deactivated link - in particular, the link quality value 0 assures that neighbors will cease to use the link.¶

If the Client needs to send uNA messages over an underlay interface other than the one being deactivated, it MUST include Interface Attributes with appropriate link quality values for any underlay interfaces being deactivated. The Client then again sends uNA messages to all neighbors the same as described above.¶

Note that when a Client deactivates an underlay interface, neighbors that receive the ensuing uNA messages need not purge all references for the underlay interface from their neighbor cache entries. The Client may reactivate or reuse the underlay interface and/or its omIndex at a later point in time, when it will send new RS messages to an FHS Proxy/Server with fresh interface parameters to update any neighbors.¶

3.15.5. Moving Between Proxy/Servers

The Client performs the procedures specified in Section 3.12.2 when it first associates with a new Hub Proxy/Server or renews its association with an existing Hub Proxy/Server.¶

When a Client associates with a new Hub Proxy/Server, it sends RS messages to register its underlay interfaces with the new Hub while including the old Hub's RND-ULA in the "Old Hub Proxy/Server ULA" field of a Proxy/Server Departure OMNI sub-option. When the new Hub Proxy/Server returns the RA message via the FHS Proxy/Server (acting as a Proxy), the FHS Proxy/Server sends a uNA to the old Hub Proxy/Server (i.e., if the ULA is non-zero and different from its own). The uNA has the MNP-XLA of the Client as the source and the RND-ULA of the old hub as the destination and with OMNI Neighbor Coordination header Preflen set to 0. The FHS Proxy/Server encapsulates the uNA in an OAL header with the RND-ULA of the new Hub as the source and the RND-ULA of the old Hub as the destination, the fragments and sends the carrier packets via the secured spanning tree.¶

When the old Hub Proxy/Server receives the uNA, it changes the Client's NCE state to DEPARTED, resets DepartTime and caches the new Hub Proxy/Server RND-ULA. After a short delay (e.g., 2 seconds) the old Hub Proxy/Server withdraws the Client's MNP from the routing system. While in the DEPARTED state, the old Hub Proxy/Server forwards any carrier packets received via the secured spanning tree destined to the Client's MNP-ULA to the new Hub Proxy/Server's RND-ULA. After DepartTime expires, the old Hub Proxy/Server deletes the Client's NCE.¶

Mobility events may also cause a Client to change to a new FHS Proxy/Server over a specific underlay interface at any time such that a Client RS/RA exchange over the underlay interface will engage the new FHS Proxy/Server instead of the old. The Client can arrange to inform the old FHS Proxy/Server of the departure by including a Proxy/Server Departure sub-option with an RND-ULA for the "Old FHS Proxy/Server ULA", and the new FHS Proxy/Server will issue a uNA using the same procedures as outlined for the Hub above while using its own RND-ULA as the source address. This can often result in successful delivery of packets that would otherwise be lost due to the mobility event.¶

Clients SHOULD NOT move rapidly between Hub Proxy/Servers in order to avoid causing excessive oscillations in the AERO routing system. Examples of when a Client might wish to change to a different Hub Proxy/Server include a Hub Proxy/Server that has gone unreachable, topological movements of significant distance, movement to a new geographic region, movement to a new OMNI link segment, etc.¶

3.16.1. Source-Specific Multicast (SSM)

When an ROS "X" (i.e., either a Client or Proxy/Server) acting as PIM router receives a Join/Prune message from a node on its downstream interfaces containing one or more ((S)ource, (G)roup) pairs, it updates its Multicast Routing Information Base (MRIB) accordingly. For each S belonging to a prefix reachable via X's non-OMNI interfaces, X then forwards the (S, G) Join/Prune to any PIM routers on those interfaces per [RFC7761].¶

For each S belonging to a prefix reachable via X's OMNI interface, X sends an NS(AR) message (see: Section 3.13) using its own RND-ULA or MNP-XLA as the source address, the solicited node multicast address corresponding to S as the destination and the MNP-XLA of S as the target address. X then encapsulates the NS(AR) in an OAL header with source address set to its own ULA and destination address set to the ULA for S, then forwards the message into the secured spanning tree which delivers it to ROR "Y" that services S. The resulting NA(AR) will return an OMNI option with Interface Attributes for any underlay interfaces that are currently servicing S.¶

When X processes the NA(AR) it selects one or more underlay interfaces for S and performs an NS/NA multilink route optimization exchange over the secured spanning tree while including a PIM Join/Prune message for each multicast group of interest in the OMNI option. If S is located behind any Proxys "Z"*, each Z* then updates its MRIB accordingly and maintains the MNP-XLA of X as the next hop in the reverse path. Since Gateways forward messages not addressed to themselves without examining them, this means that the (reverse) multicast tree path is simply from each Z* (and/or S) to X with no other multicast-aware routers in the path.¶

Following the initial combined Join/Prune and NS/NA messaging, X maintains a NCE for each S the same as if X was sending unicast data traffic to S. In particular, X performs additional NS/NA exchanges to keep the NCE alive for up to t_periodic seconds [RFC7761]. If no new Joins are received within t_periodic seconds, X allows the NCE to expire. Finally, if X receives any additional Join/Prune messages for (S,G) it forwards the messages over the secured spanning tree.¶

Client C that holds an MNP for source S may later depart from a first Proxy/Server Z1 and/or connect via a new Proxy/Server Z2. In that case, Y sends a uNA message to X the same as specified for unicast mobility in Section 3.15. When X receives the uNA message, it updates its NCE for the MNP-XLA for source S and sends new Join messages in NS/NA exchanges addressed to the new target Client underlay interface connection for S. There is no requirement to send any Prune messages to old Proxy/Server Z1 since source S will no longer source any multicast data traffic via Z1. Instead, the multicast state for (S,G) in Proxy/Server Z1 will soon expire since no new Joins will arrive.¶

3.16.2. Any-Source Multicast (ASM)

When an ROS X acting as a PIM router receives Join/Prune messages from a node on its downstream interfaces containing one or more (*,G) pairs, it updates its Multicast Routing Information Base (MRIB) accordingly. X first performs an NS/NA(AR) exchange to receive route optimization information for Rendezvous Point (RP) R for each G. X then includes a copy of each Join/Prune message in the OMNI option of an NS message with its own RND-ULA or MNP-XLA as the source address and the RND-ULA or MNP-XLA for R as the destination address, then encapsulates the NS message in an OAL header with its own ULA as the source and the RND-ULA of R's Proxy/Server as the destination then sends the message into the secured spanning tree.¶

For each source S that sends multicast traffic to group G via R, Client S* that aggregates S (or its Proxy/Server) encapsulates the original IP packets in PIM Register messages, includes the PIM Register messages in the OMNI options of uNA messages, performs OAL encapsulation and fragmentation then forwards the resulting carrier packets with Identification values within the receive window for Client R* that aggregates R. Client R* may then elect to send a PIM Join to S* in the OMNI option of a uNA over the secured spanning tree. This will result in an (S,G) tree rooted at S* with R as the next hop so that R will begin to receive two copies of the original IP packet; one native copy from the (S, G) tree and a second copy from the pre-existing (*, G) tree that still uses uNA PIM Register encapsulation. R can then issue a uNA PIM Register-stop message over the secured spanning tree to suppress the Register-encapsulated stream. At some later time, if Client S* moves to a new Proxy/Server, it resumes sending original IP packets via uNA PIM Register encapsulation via the new Proxy/Server.¶

At the same time, as multicast listeners discover individual S's for a given G, they can initiate an (S,G) Join for each S under the same procedures discussed in Section 3.16.1. Once the (S,G) tree is established, the listeners can send (S, G) Prune messages to R so that multicast original IP packets for group G sourced by S will only be delivered via the (S, G) tree and not from the (*, G) tree rooted at R. All mobility considerations discussed for SSM apply.¶

3.16.3. Bi-Directional PIM (BIDIR-PIM)

Bi-Directional PIM (BIDIR-PIM) [RFC5015] provides an alternate approach to ASM that treats the Rendezvous Point (RP) as a Designated Forwarder (DF). Further considerations for BIDIR-PIM are out of scope.¶