Logical Interface Overview Date: [2014-03-20] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital+1 514 904 Notice:

Slides:



Advertisements
Similar presentations
Omniran Network Detection and Selection Date: Authors: NameAffiliationPhone Max RiegelNSN
Advertisements

Omniran GPP Trusted WLAN Access to EPC Use Case Analysis Date: Authors: NameAffiliationPhone Max RiegelNSN
Netext issues Julien Laganier, IETF-80. Logical Interface (I) #1: Replication of ND multicast messages across physical interfaces – What is in the source.
SDN-based OmniRAN Use Cases Date: [ ] Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34 Juan Carlos ZúñigaInterDigital+1.
IETF 80: NETEXT Working Group – Logical Interface Support for IP Hosts 1 Logical Interface Support for IP Hosts Sri Gundavelli Telemaco Melia Carlos Jesus.
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran OmniRAN Proximity Service use case Date: [ ] Authors: NameAffiliationPhone Hyunho ParkETRI
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio
OmniRAN ecsg SDN-based Control Plane and Data Plane Separation in OmniRAN Network Reference Model Date: Authors: NameAffiliationPhone .
Omniran OmniRAN Wi-Fi Hotspot Roaming Use Case Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran PtP Links across IEEE 802 Bridged Infrastructure Date: Authors: NameAffiliationPhone Max
NETEXT WG, th IETF, Anaheimdraft-bernardos-netext-ll-statement-01 Applicability Statement on Link Layer implementation/Logical Interface over.
OmniRAN SoA and Gap Analysis Date: [ ] Authors: NameAffiliationPhone Antonio de la Juan Carlos
Proposal for an IEEE 802 EC OmniRAN Study Group Document Number: IEEE Shet Date Submitted: Source: Roger Marks (Consensii.
OmniRAN Specification – Structuring the effort Document Number: Omniran Date Submitted: Source: Max Riegel
Discussion on NRM Control Reference Points Information and Parameters Date: Authors: NameAffiliationPhone Antonio de la Oliva University.
Privecsg ‹#› IEEE 802 Privacy concerns about 802c PAR Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZunigaInterDigital.
OmniRAN SDN-based OmniRAN Use Cases Summary Date: Authors: NameAffiliationPhone Antonio de la OlivaUC3M+34
An SDN-based approach for OmniRAN Reference Point mapping Date: [ ] Authors: NameAffiliationPhone Antonio de la
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran CF00 1 OmniRAN R3 Considerations Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 P802.1CF NRM Mapping to real networks Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
Omniran CF CF Network Reference Model Introduction Date: Authors: NameAffiliationPhone Max RiegelNokia Networks+49.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Analysis on Identifiers Date Submitted: January 9, 2006 Presented.
WiFi Privacy network experiment at IEEE 802 Berlin Plenary and IETF92 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho Title: IETF NETEXT Overview and Relationship with c Date Submitted: March 16, 2010.
Omniran Thoughts about the tenets in IEEE 802.1CF Date: Authors: NameAffiliationPhone Max RiegelNSN
Privecsg Tracking of Link Layer Identifiers Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
WiFi Privacy network experiment at IETF91 Date: [ ] Authors: NameAffiliationPhone Carlos Jesús Fabio
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 VLANs in relation to P802.1CF NRM Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
1 privecsg Privacy EC SG Update to NGP SG Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran CF00 1 CF ToC Refinements Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 Content and outline considerations for Annex: Applicability to non-IEEE 802 PHY layer technologies Date: Authors:
OmniRAN IEEE 802 OmniRAN Recommended Practice ToC Proposal Date: Authors: NameAffiliationPhone Yonggang
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: November 14, 2013 Presented at IEEE session.
Privecsg Overview of Privacy in Date: Authors: NameAffiliationPhone Phillip BarberBroadband Mobile Tech
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: September 16, 2010 Presented at IEEE session.
Omniran CF00 1 P802.1CF NRM Backhaul Considerations Date: Authors: NameAffiliationPhone Max RiegelNokia Networks
OmniRAN IEEE 802 OmniRAN Architecture Proposal Date: Authors: NameAffiliationPhone Yonggang Bo.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IETF Liaison Report Date Submitted: May 14, 2009 Presented at IEEE session.
3GPP SA2 SaMOG Status Document Number: Omniran Date Submitted: Source: Antonio de la Oliva UC3M *
IETF 80: NETEXT Working Group – Logical Interface Support for IP Hosts 1 Logical Interface Support for IP Hosts Telemaco Melia, Sri Gundavelli, Carlos.
NETEXT WG, th IETF, Beijing Logical Interface Support for multi-mode IP Hosts draft-ietf-netext-logical-interface-support-01 Sri Gundavelli.
Omniran IEEE 802 Scope of OmniRAN Date: Authors: NameAffiliationPhone Max RiegelNSN
Omniran CF00 1 Key Concepts of Association and Disassociation Date: Authors: NameAffiliationPhone Max RiegelNokia
Privecsg Privacy Recommendation PAR Proposal Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital
Omniran Backhaul representation in OmniRAN SDN model Date: Authors: NameAffiliationPhone Max RiegelNSN
draft-jeyatharan-netext-pmip-partial-handoff-02
Date: < yyyy-mm-dd >
An SDN-based approach for OmniRAN
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
IEEE MEDIA INDEPENDENT HANDOVER DCN: srho
SDN Functional Decomposition
P802.1CF operational models
[place document title here]
IEEE 802 Scope of OmniRAN Abstract
Privacy Recommendation PAR Proposal
Broadcast Handovers Tutorial Overview
An SDN-based approach for OmniRAN Reference Point mapping
January 2013 Summary Report for OmniRAN EC SG
[place document title here]
802.1CF ToC Refinements Abstract
OmniRAN SDN Use Case ToC
SDN-based OmniRAN Use Cases Summary
OmniRAN SDN Use Case ToC
Logical Interface Support for IP Hosts
Presentation transcript:

Logical Interface Overview Date: [ ] Authors: NameAffiliationPhone Juan Carlos ZúñigaInterDigital Notice: This document does not represent the agreed view of the OmniRAN EC SG. It represents only the views of the participants listed in the ‘Authors:’ field above. It is offered as a basis for discussion. It is not binding on the contributor, who reserve the right to add, amend or withdraw material contained herein. Copyright policy: The contributor is familiar with the IEEE-SA Copyright Policy. Patent policy: The contributor is familiar with the IEEE-SA Patent Policy and Procedures: and. Abstract This presentation provides a an overview of the Logical Interface definition and discussions that have taken place at the NETEXT working group in the IETF. These discussions could be relevant to the latest developments in OmniRAN and are presented for informational background purposes.

Logical Interface Overview Juan Carlos Zúñiga (InterDigital Labs)

Logical Interface in IETF/NETEXT The IETF NETEXT WG has discussed the concept of a logical interface to support multi- technology handovers and IP Flow mobility These definitions are relevant to the latest discussions in OmniRAN, especially with respect to handling multiple technologies logical-interface-support logical-interface-support

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

Logical Interface Properties 1.The logical interface has a relation to a set of physical interfaces (sub-interfaces) on the host that it is abstracting. These sub-interfaces can be attached or detached from the Logical Interface at any time. The sub-interfaces attached to a Logical interface are not visible to the IP and upper layers. 2.The logical interface may be attached to multiple access technologies. 3.The Transmit/Receive functions of the logical interface are mapped to the Transmit/Receive services exposed by the sub- interfaces. This mapping is dynamic and any change is not visible to the upper layers of the IP stack. 4.The logical interface maintains IP flow information for each of its sub-interfaces. A conceptual data structure is maintained for this purpose. The host may populate this information based on tracking each of the sub-interface for the active flows.

Some previous discussions/definitions 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, like ) The Logical Interface has the path awareness of an IPv4/IPv6 link through a sub-interface. 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) The Logical interface should transmit uplink packets on the same physical interface on which the downlink packet was received for the particular prefix/flow. This relationship should follow the policies configured by the network and can be dynamically reconfigured.

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 Some previous discussions/definitions (cont.)

The sub-interfaces of a logical interface can be bound to point-to- point links over any access technology. Shared media (e.g., IEEE ) are supported as long as they provide a point-to-point link [rfc4861] as required by the Proxy Mobile IPv6 specification [RFC-5213]. 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 media can provide a point-to-point link Ex:, 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. The logical interface appears as a shared-link to the applications, and adapts to the link model of the sub-interface for packet communication. Some previous discussions/definitions (cont.)