MuGM IEEE MEDIA INDEPENDENT HANDOVER DCN: MuGM Title: Definition of IEEE d multicast identifiers Date Submitted: November, 2012 Authors or Source(s): Daniel Corujo (ITAv), Antonio de la Oliva (UC3M) Abstract: This document describes the use of a subset of the MIHF_ID space to describe multicast identifiers.

MuGM IEEE presentation release statements This document has been prepared to assist the IEEE 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 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 Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3 IEEE presentation release statements This document has been prepared to assist the IEEE 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 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 Section 6 of the IEEE-SA Standards Board bylawshttp://standards.ieee.org/guides/bylaws/sect6-7.html#6

Multicast MIHF Identifiers Each MIHF has a unique MIHF_ID, which is also used in transactions to indicate the source/destination of a MIH Protocol message Currently, a zero-length MIHF_ID is able to be used as a broadcast identifier However, this is now enough to individually address different multicast groups Moreover, any change to the MIHF_IDs needs to be backwards compatible

Multicast MIHF Identifiers Proposal: to use MIHF identifiers as the means for identifying MIH-enabled multicast groups – We can create multicast MIHF_IDs by using the NAI representation of a L2 or L3 multicast address Features: – Allows a node to have several multicast-enabled MIHF_IDs, in addition to it’s own unique unicast MIHF_ID – Relies on already-existing multicast procedures at both L2 and L3 level Thus maintains the already existing MIHF_ID determination capability – This MIHF_ID is still a NAI-encoded IP address (for L3) or a NAI- encoded link-layer address (for L2) – Enables the use of.21 messages without further modification