1 / 5

n etext issues

n etext issues. Julien Laganier, IETF-80. Logical Interface (I). #1: Replication of ND multicast messages across physical interfaces What is in the source link layer address? How are multiple answers dealt with? #3: Link layer ID

salome
Download Presentation

n etext issues

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. netext issues Julien Laganier, IETF-80

  2. Logical Interface (I) • #1: Replication of ND multicast messages across physical interfaces • What is in the source link layer address? • How are multiple answers dealt with? • #3: Link layer ID • If an underlying link layer does not let you use an arbitrary link layer identifier, what is the linklayer identifier exposed by the logical interface to the IP layer? • #5: Multicast Traffic • IP stack wants to send a packet to a multicast address M;  How is it transmitted?

  3. Logical Interface (II) • #4: shall document only Point-to-Point Link model • As per the original PMIPv6 specification [RFC5213] the physicalinterface underneath the logical interface has to be bound topoint-to-point link [RFC4861]. Access technologies that provides a shared media (e.g., IEEE 802.11) can be supported as long as they provide a point-to-point link [rfc4861]. The details of how a shared media provides a point to point link are link layer specific and/or operational matters that are out of scope of this document. For example IEEE 802.11 media can provide a point-to-point link via the appropriate use of IEEE 802.1Q VLAN header where a distinct VLAN is configured between the MAG and each of the mobile node.

  4. Logical Interface (III) • #6 MTU • what is the logical interface MTU? • PMTUD and transport impact of handoffs b/w IFs w/ != MTUs • #7 Uplink/Downlink matching • “ Logical interface should transmit uplink packets on the same physical interface on which the downlink packet was received for the particular prefix/flow” How does the logical interface associates an uplink packet to a downlink packet?

  5. PMIPv6 Model • RFC 5213: unmutable prefix set assigned to MN at attach • Attach triggered by L2 triggers • Required for secure triggering • L2 can signal intent to do inter-access handoff • Absence of L2 signal defaults to new session creation for new interface  avoids breaking unmodified host that doesn’t support inter-access handoff • No reason to depart from that for flow mobility • Attach physical interface to PMIPv6 session via L2 triggers • L2 can signal intent to do simultaneous access for flow mobility • Absence of L2 signal defaults to new session creation for new interface  avoids breaking host that doesn’t support simultaneous access • LMA deciding to move a flow doesn’t require new prefix assignment  just move the flow

More Related