1 / 9

79th IETF, Beijing

Logical Interface Support for multi-mode IP Hosts draft-ietf-netext-logical-interface-support-01. Sri Gundavelli (ED) Telemaco Melia (ED). 79th IETF, Beijing. Session to IP address binding. TCP/UDP. IP. IP to logical interface binding. Logical interface.

jeff
Download Presentation

79th IETF, Beijing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Logical Interface Support for multi-mode IP Hosts draft-ietf-netext-logical-interface-support-01 Sri Gundavelli (ED) Telemaco Melia (ED) 79th IETF, Beijing

  2. Session to IP address binding TCP/UDP IP IP to logical interface binding Logical interface logicaltophysical interface binding L2(IF#1) L2(IF#2) L2(IF#n) … L1 L1 L1 Logical Interface Setup

  3. Logical Interface Properties • P1: The Logical Interface may or may not use the same link layer identifier as the physical interfaces (i.e. some technologies might not allow changing the link layer ID) • P2: Logical interface has a relation to a set of physical interfaces (sub-interfaces) on the host. Sub-interfaces can be attached/detached to the Logical Interface at any time (i.e. upon L2 hints) • P3: The Logical Interface has the path awareness of an IPv4/IPv6 link through a sub-interface. • P4: The logical Interface may manage heterogeneous links. As such, different MTUs may be announced on different links. The Logical Interface should be able to configure a common value (e.g., the minimum value observed by any link) • P5: Send/Receive operations of a Logical interface are managed dynamically and are tied to the sub-interfaces (i.e. dynamic mapping not be visible to the applications) • P6: The Logical interface should transmit uplink packets on the same physical interface on which the downlink packet was received for the particular prefix/flow.

  4. Virtual Link Layer ID • The logical interface has a virtual link-layer identifier (VLL-ID), used to: • Used for the neighbor discovery operation • Used to configure the IP address for this logical interface when the SLAAC is applied • Stored in the BCE at the Local Mobility Anchor via the Link-layer Identifier Option of the PBU • Used as the source link-layer address for sending packets from this logical interface • Physical interface SHOULD be able to send packets with the VLL-ID as the source link-layer address and SHOULD be able to receive packets with the VLL-ID as the destination link-layer address

  5. Link Scoped Unicast Traffic • Link-local unicast traffic generated by the LIF is sent through all PIFs associated to the LIF. • Because of the properties of the PMIPv6 domain this mode of operation of the LIF does not add any issue from the point of view of ND.

  6. Link Scoped Multicast Traffic • Link-local multicast traffic generated by the LIF is sent through all PIFs associated to the LIF. • As a result of the reception of certain types of link-local multicast traffic, the LIF might need to generate and send a (unicast) response. In this case, there are two possible approaches that can be followed: • Send unicast responses via all PIFs associated to the LIF • Keep state at the LIF so replies can be sent via the proper interface only.

  7. Link scoped traffic management • --------- --------- | MAG 1 | | MAG 2 | --------- --------- | mag-IPv6-ll-addr | mag-IPv6-ll-addr| mag-l2-addr | mag-ll-addr | | | | | | | | RA(pref1) | | RA(pref2) | V | V | --------------- | | RS | LIF | RS | | <--- --------------- ----> | ( pref1 and pref2 )|--------------+ PIF1 | PIF2 +--------------| ( may be the same ) --------------- Neighbor cache (interface LIF): IPv6 address link-layer address============== ==================== mag-IPv6-ll-addr mag-ll-addr

  8. MTU considerations • The LIF SHOULD be configured with the maximum MTU value that is supported by all interfaces (see P4).

  9. LIF Conceptual Data Structures • LIF TABLE FLOW table +===============================+ +===============================+ | PIF_ID | FLOW RoutingPolicies | | FLOW ID | PIF_ID | | | Home Network Prefix | +-------------------------------+ | | Link Layer Address | | FLOW_ID | PIF_ID | | | Status | +===============================+ +-------------------------------| | PIF_ID | FLOW RoutingPolicies | | | Home Network Prefix | | | Link Layer Address | | | Status | +-------------------------------+ | .... | .... | +===============================+

More Related