FMIPv6 over IEEE 802.16 (draft-ietf-mipshop-fh80216e-02.txt)

1. FMIPv6 over IEEE 802.16 (draft-ietf-mipshop-fh80216e-02.txt) HeeJin Jang, Youn-Hee Han, Soohong Daniel Park SAMSUNG Junghoon Jee, Jaesun Cha ETRI - IETF 62 -

2. Contents • Status Report • Feedbacks from 16ng WG • Next Steps

3. Status Report • Feedbacks from 16ng WG experts • Jinhyeock Choi (WiMAX & 16ng Expert) • Yoshihiro Ohba (IEEE 802.21 Liaison ) • Jonne Soienen (NETLMM WG chair) • The latest version (draft-ietf-mipshop-fh80216e-02.txt) has been updated based on the 1st two reviewer’s comments, but Jonne’s comments has not been reflected yet. • Most of comments were editorial things except the following comments.

4. Comments & Resolutions • Incorrect statements in Section 3 (Deployment Architecture) • There can be as many subnets as the # of MNs according to per-MN-prefix link model which is not described • The draft was fine without the section, so the section was removed. • Use the latest IEEE 802.21 message • Use a ‘Link_Detected’ primitive instead of a New_BS_Found • Use a ‘Handover_commit’ primitive instead of a Link_Switch

5. Comments & Resolutions • Why not use a Link_Handover_Imminent primitive of 802.21 instead of a Link_Going_Down ? • According to 802.21 document, a Link_Going_Down is more appropriate than a Link_Handover_Imminent for handover preparation. • “A Link_Going_Down provides …the time interval required to anticipate in advance and make adequate a priori preparation to handover a connection …” (in IEEE 802.21 document.) • A MOB_NBR-ADV is not enough for generating a Link_Detectedtrigger, because inclusion of a particular BSID in MOB_NBR-ADV does not mean that the target BS is within the MN's radio coverage. • It is reflected so that when an MN receives MOB_NBR-ADV including new BSID, it identifies the BS’s reachability through scanning, and then the Link_Detected is triggered.

6. Comments & Resolutions • The goal and role of this document is not clearly mentioned. • The goal of this document is to provide developers with implementation guideline so that they provide products which can realize seamless handover in the 802.16 networks. • We will clarify the following role/advantages of documents in the introduction section. • This WG draft selects a set of useful primitives among primitives proposed by IEEE 802.21 which can be cooperated with 802.16 handover messages for efficient FMIPv6 operation, and also provides the most appropriate trigger timing of each of selected primitives during 802.16 handover procedure for optimal FMIPv6 operation. • It introduces the recommended fast handover scenarios in 802.16 network by using L2 (802.16) & L3 (FMIPv6) interaction based on IEEE 802.21 primitives.

7. Comments & Resolutions • WiMAX is an architecture specified for 802.16e radio with its specific procedures and its specific architecture. It should not be regarded as a general case in the context. • WiMAX is practical standard which is being developed by vendors, and we'll clarify the WiMAX-relative texts just as an example only for WiMAX networks. • If the WiMAX document is not a public specification, it be a bit hard to point to it from IETF document. • The document is not a final standard of Wimax Network WG yet, but Referencing it is helpful for giving a concrete example. We will refer it just as a informational reference.

8. Comments & Resolutions • Need more explanation for 802.16 handover • We referred a reference (IEEE 802.16e) again for better understanding in the section where the 802.16 handover procedure is described. • In point-to-point link model, how can we formulate the NCoA because there is no shared prefix? • As Rajeev Koodli said, simply an NCoA based on per-MN prefix can be overridden by NAR in HAck. • Section 6.2.2 of RFC4068, code 3: Handover Accepted, NCoA assigned • RFC 4068 does not make assumptions about how the prefixes are assigned and managed on an AR’s link, and it’s outside the scope of RFC 4068 and also this document.

9. Next Steps • Submit a draft-ietf-mipshop-fh80216e-03 based on the last review’s comment, and move it forward for MIPSHOP WG Last call.