1. 21-07-xxxx-00-0000 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-07-xxxx-00-0000 Title: Multiple MIH User Issues Date Submitted: November, 12-16, 2007 Presented at IEEE 802.21 session #23 Atlanta, GA Authors or Source(s): Ajay Rajkumar, David Faucher Abstract: This is the abstract text. Replace this text with a short statement of the contents and purpose of the presentation. Communicate well, you only have a few lines or so to convey the essence of the slides.

2. 21-07-xxxx-00-0000 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

3. 21-07-xxxx-00-0000 Problem MIH_Capability_Discover The current description has the MIH User specifying the supported events, commands, query types and transport list within the request and response primitives. The intent here was to allow the MIH User to restrict what capabilities the peer MIHF would see. However, there are no functions within MIH that would support this feature, e.g. an MIH User could still request (and receive service for) a command or event that was not reported by the peer MIHF in the capabilities discover yet is supported by the peer MIHF. Exceptions to this would be those functions that are supported only by the MIH User. For example, it is reasonable to expect that a MIH User would receive and process MIH Get Information requests (indications) thus in this instance the MIH User should provide this in the MIH Capability Discover.

4. 21-07-xxxx-00-0000 Proposal 1 Remove MIH_EVENT_LIST and MIH_TRANSPORT_LIST from the request and response primitives as these would be filled in either by the local or peer MIHF. Leave MIH_IS_QUERY_TYPE_LIST as this is a function that is provided by the MIH User. MIH_COMMAND_LIST is more complicated as there are bit definitions that comprise more than one command (some of which may not be implemented by the MIH User). B0-B2: should not be specified by the MIH User as these are filled in by MIHF B3: the candidate query and all N2N commands are implemented by the MIH User and should be specified by the MIH User, the Net_HO_Commit command is implemented by the MIHF so the MIH User should not specify this command. B4: the candidate query and complete commands are implemented by the MIH User and should be specified by the MIH User. However, with the changes expected for MN_HO_Commit, it is unclear whether this should be specified by anyone (e.g. since it is a local command only)

5. 21-07-xxxx-00-0000 Proposal 2 Keep the primitives as they are now but allow the MIHF to change those parameters which conflict with its view of what capabilities are provided. This brings up the question of whether an MIHF should be allowed to add parameters that the MIH User did not specify. Also, should MIHF become an arbitrator of all messages that pass through it.