AERO/OMNI Base Specification Amendments (Volume 1)

Amendments to the AERO/OMNI specifications appear in the following sections in the chronological order in which they were identified, formalized and reported. As new amendments are reported and/or discovered, they will be added below in the order they are received which may not necessarily align with specification chapter orders and/or resolution priority.

The AERO/OMNI base specifications include comprehensive instructions for Clients to request and receive Mobile Network Prefix (MNP) Prefix Delegations (PD) from the mobility service. The specifications suggest that the Client should apply these MNP PDs on downstream-attached (or, "tethered") End User Network (EUN) interfaces but do not discuss specific MNP administrative procedures. Per this amendment, when a Client receives an MNP PD it should provision the MNP over EUNs in a manner consistent with and . More specifically, the Client assigns /64 portions of the MNP to its EUN interfaces and optionally also sub-delegates other portions of the MNP to requesting EUN nodes. (The Client can also use virtual interfaces such as a loopback as EUN interfaces.) The Client should then assign an IPv6 address taken from each EUN /64 prefix to the corresponding EUN interface using standard IPv6 address (auto)configuration procedures. The Client then associates the IPv6 Subnet Router Anycast (SRA) address corresponding to the MNP with the OMNI interface but does not assign it to the interface. For example, if the Client receives the MNP PD 2001:db8:1::/48, it should accept packets with the SRA address 2001:db8:1:: as the destination and respond with packets that use one of the Client's EUN addresses as the source. After the Client configures the SRA address and assigns EUN addresses it can operate as an IPv6 host over the OMNI interface according to the weak end system model while also serving as an IPv6 router for its EUNs. The Client then engages IPv6 host and router operations the same as per and except that the Client engages the OMNI interface as a combined host/router interface. When the Client acts as an IPv6 host over the OMNI interface, it can send Router Solicitations (RSs) to elicit Router Advertisements (RAs) from OMNI link Proxy/Servers. The Client can then use its EUN addresses for packets exchanged between its local applications and correspondents reached via OMNI link neighbors. (When the Client has no EUN addresses, it can instead use its OMNI interface Multilink Local Address (MLA) with the understanding that the packets may be routable only within the OMNI link limited domain.) When the Client acts as an IPv6 router over the OMNI interface, it forwards IPv6 packets between EUN peers and correspondents reached via OMNI link neighbors but never sends RA messages over the OMNI interface. This may require the Client to enable "IPv6 forwarding" on the OMNI interface but without representing itself as an IPv6 router in OMNI link IPv6 Neighbor Discovery (IPv6 ND) messages. The Client instead sends RAs over its EUN interfaces that include EUN portions of the MNP in Prefix Information Options (PIOs) and also represents itself as an IPv6 router in other EUN interface IPv6 ND messages. Note that the Client could also optionally assign each EUN address it configures to the OMNI interface. This would give the outward appearance of support for the strong end system model, albeit with added complexity for coordinating the same IP unicast address assigned to multiple Client interfaces. Further details on administrative options are beyond the scope of this amendment.