DCN / 21-10-0141-00-srho
Title / Minutes of May 2010 802.21c TG Meeting
Date submitted / June 13, 2010
Source(s) / Hongseok Jeon (ETRI) / ContactInfo /
Abstract / IEEE 802.21c meeting minutes
Purpose / To record the minutes of the IEEE 802.21c Task Group meeting IEEE 802.21 session #38 in Bangalore, India
Release / 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.
Patent Policy and Procedures / The contributor is familiar with the IEEE-SA Patent Policy and Procedures:
> and <>.
Further information is located at <
and <>.
IEEE 802.21 Media Independent Handover Services
Meeting Minutes of the IEEE P802.21cSingle Radio Handover Task Group
Chair: Junghoon Jee
Vice Chair: Anthony Chan
Minutes taker: Hongseok Jeon
1.Session 1 (May12, 2010, 05:00 pm -07:00 pm, Local Time)
The Chair presented meeting protocol and the IEEE patent policy. The chair requested information on essential patents, patent claims, and pending patent applications and called for letters of assurance. No response was made to the call.
The chair presented 802.21c progress so far. (Refer to 21-10/0092r0)
The chair presented the agenda items for this Bangalore 21c meeting.
The chair updated the march meeting minutes (21-10/0094r1) because the document has an wrong DCN. The chair requested approval ofthe updated minutes (21-10/0094r2). There was no objection from the task group, so the minutes are approved.
1.1 Presentation: No DCN, WMF IWK Update, by Junghoon Jee
The presenter verbally summarized progress on WMF IWK.
- Question (Q): WMF IWK was discussed so far. What would be the next step now?
- Presenter (P): WMF NWG sent two liaison letters to 21c in order to show their interest in creating 21c TG and their will to cooperate with 21c TG. Also they shared the IWK document with 21c. Actually, it is hard to clearly decide next step now. We have to maintain good relationship with WiMAX as well as 802.16. We need to create some values from ourselves regarding some pre-registration functions and we need to call related contributions and discuss about how for 802.21c to help WiMAX and 802.16 WG. Probably, we need an initial document and then push it to WiMAX and 802.16WG. We need to show them some added values.
1.2 Presentation: 21-10/0061/r2, IETF NETEXT Overview and Relationship with 802.21c, By Juan Carlos Zuniga
The presenter briefly explained Proxy Mobile IP architecture and related issues and introduced “hiding access technology change from IP layer” as one of working items in NETEXT WG.
- Q: How does the logical interface help PMIP?
- P: Main thing is there is a role of no change of IP stack. So we have to handle mobility without change of mobility stack.
- Comment (C): We only specify part related to IETF. Maybe it can be a little part.
- Q: Each physical interface has different MAC address. So, they have different IPv6 address.
- P: The logical interface can convert the MAC address of incoming packets.
- Q: Multiple flows are possible?
- C: Logical interface plays an only role of giving single identification.
- Q: I don’t know how for the traffic to be distributed with multiple interfaces.
- P: LMA handle flow mobility. So, logical interface information from client should be delivered to LMA. (Such as information on link down interface) So, we need a communication b/w client and LMA.802.21 is good candidate technology for that.
- Q: Is there a new protocol to deliver information b/w client and LMA?
- P: 802.21c will be the protocol.
- Q: NETEXT socialize with 3GPP. However, 3GPP use DSMIP for flow mobility. Is there any requirement?
- P: 3GPP considers MIP and PMIP for flow mobility.
1.3 Presentation: No DCN, SRHO Functional Requirement Discussion, By Junghoon Jee
The presenter reviewed current SRHO functional requirement (21-10/0017/r1). The presenter said that current SRHO functional requirements were focused on WiMAX Forum too much and so we have to extend to more general manner.
- Q: Are you thinking to add or delete requirements?
- C: Just adding requirement is a good approach.
- Q: We have too many requirements, which causes many contributions.
- A: We have already draft outline. We can incorporate those multiple contributions.
Chair asked if it is possible to announce a technical editor without agreement of WG members. He got a verbal acceptance.
Chair arranged conference call times as follows:
May 19th 22:00 ET
June 2nd 09:00 ET
June 16th 22:00 ET
June 30th 22:00 ET
July 7th 09:00 ET
Chair called the session to adjourn at 6:46pm.
1