IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-10-0061-01-srho Title: IETF NETEXT Overview and Relationship with 802.21c Date Submitted: March 16, 2010 Presented at IEEE 802.21 session #37 in Orlando, FL Authors or Source(s): Juan Carlos Zuniga (InterDigital) Antonio de la Oliva, Carlos Bernardos (UC3M) Telemaco Melia (Alcatel-Lucent) Abstract: Overview of IETF activities in the NETEXT group and the relationship with current 802.21c activities 1 21-10-0061-01-srho
14
Embed
IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-10-0061-01-srho Title: IETF NETEXT Overview and Relationship with 802.21c Date Submitted: March 16, 2010.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
IEEE 802.21 MEDIA INDEPENDENT HANDOVER
DCN: 21-10-0061-01-srho
Title: IETF NETEXT Overview and Relationship with 802.21c
Date Submitted: March 16, 2010
Presented at IEEE 802.21 session #37 in Orlando, FL
Authors or Source(s):
Juan Carlos Zuniga (InterDigital)
Antonio de la Oliva, Carlos Bernardos (UC3M)
Telemaco Melia (Alcatel-Lucent)
Abstract: Overview of IETF activities in the NETEXT group and the relationship with current 802.21c activities
121-10-0061-01-srho
2
IEEE 802.21 presentation release statementsThis document has been prepared to assist the IEEE 802.21 Working Group. It is offered as a basis
for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.21.
The contributor is familiar with IEEE patent policy, as stated in Section 6 of the IEEE-SA Standards Board bylaws <http://standards.ieee.org/guides/bylaws/sect6-7.html#6> and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/faq.pdf>
21-10-0061-01-srho
IETF NETEXT Overview and Relationship with 802.21c
21-10-0061-01-srho
Proxy Mobile IP
• Proxy Mobile IP standardized in NETLMM– Provides roaming within a
PMIP domain without changing IP address
– It provides also a limited multi-homing support to multi-mode devices
• Initial assumption• Changes in the IP stack are
undesirable
• How do we provide more advance features while using PMIP, without changing the IP stack?– Inter-access handover– Flow mobility
21-10-0061-01-srho
NETEXT
• Working on PMIP extensions:• Localized routing• Bulk refresh• LMA redirection• Radius Extensions • Hiding access technology changes from IP
21-10-0061-01-srho
Hiding L2 changes to the IP stack• Layer 2 techniques hiding the actual physical interface
being used by the IP layer– Link layer support– Logical interface– Layer 2.5
• Assumption: an IP layer interface is able to simultaneously and/or sequentially attach to different MAGs
• Main issues:• MIH_Link_UP is not reaching the new MAG
• It requires registration and subscription but it cannot be done when the MN arrives to the new PoA
• It requires the nMAG to talk with the pMAG in order the nMAG to subscribe to MIH_Link_Up before it moves
21-10-0061-01-srho
PMIP+IEEE 802.21 (Future 802.21c?)
• PoS at LMA?
• Maybe it is easier to manage all the mobility of the user in one central point, the same for IP and .21– One PoS located in the LMA– Just one subscription is required for all interfaces and maybe
flows
• Issues: Communication not allowed on nMAG– Use MIH_Link_Going_Down instead of MIH_Link_Up?– Preauthentication?– Change the way MIH_Link_Up can be sent?