1. 21-14-0154-00-MuGM IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-14-0154-00-MuGM Title: Suggested remedy for i-115 Date Submitted: Oct, 10, 2014 Presented at IEEE 802.21d Sponsor Ballot comment resolution Authors or Source(s): Yoshikazu Hanatani, Yoshihiro Ohba (Toshiba) Abstract: The Sponsor Ballot Comment Resolution on Comment i- 115. 1

2. 21-14-0154-00-MuGM IEEE 802.21 presentation release statements This 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 outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html> Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3 http://standards.ieee.org/board/pat/guide.html IEEE 802.21 presentation release statements This 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 and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/faq.pdf> Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6 http://standards.ieee.org/board/pat/faq.pdf 2

3. Problem Description of MIH PDU protected through Group key generated MIHSA or digital signature is missed, when MIH PDU fragmentation is occurred. 21-14-0154-00-MuGM3

4. Proposed remedy: Outline Protect each fragment by the same method for the Service Specific TLVs. 21-14-0154-00-MuGM4 MIH Header Source MIHF Identifier TLV Destination MIHF Identifier TLV A fragment GKB-SA Signature GKB-SA & Signature MIH Header Source MIHF Identifier TLV Destination MIHF Identifier TLV A fragment MIH Header Source MIHF Identifier TLV Destination MIHF Identifier TLV Signature TLV SAID TLV Security TLV MIH Header Source MIHF Identifier TLV Destination MIHF Identifier TLV SAID TLV Security TLV Signature TLV

5. Proposed Remedies (1/2) 1.Revise Figure 31 and 32 (p.37). 1. Change “MIH Service Specific TLVs” to “MIH Service Specific TLVs or a fragment.” 2.Simplify 9.5.3.1.2 and Figure 40. 1. Current 9.5.3.1.2 explains how to generate the MIH_Net_Group_Manipulate indication/request message. 2. Proposed remedy is revise 9.5.3.1.2 to explain how to generate the Service Specific TLVs of the MIH_Net_Group_Manipulate indication/request message. 3. I.e., the description on the MIH protection method et al. is removed from 9.5.3.1.2. 3.Simplify 9.5.3.2 and Figure 42. 1. Current 9.5.3.2 explains how to operate the MIH_Net_Group_Manipulate indication/request message. 2. Proposed remedy is revise 9.5.3.2 to explain how to operate the Service Specific TLVs in the MIH_Net_Group_Manipulate indication/request message. 3. I.e., the description on the operation for the protected MIH PDU is removed from 9.5.3.2. 21-14-0154-00-MuGM5

6. Proposed Remedies (2/2) 4.Revise 9.6.2. 1. Change “MIH Service Specific TLVs” to “MIH Service Specific TLVs or a fragment.” 5.Revise 9.6.3.1 and 9.6.3.2. (Revised version by 21-14-0152- 02-MuGM-sb-comment-i15-and-i37) 1. Change “MIH Service Specific TLVs” to “MIH Service Specific TLVs or a fragment.” 21-14-0154-00-MuGM6