1. 21-08-0187-00-0000 IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-08-0187-00-0000 Title: Use of MAC addresses in MIH protocol Date Submitted: June 19, 2008 Presented at IEEE 802.21 teleconference in June 19, 2008 Authors or Source(s): Yoshihiro Ohba (Toshiba) and Anthony Chan (Huawei) Abstract: This document is for discussion of SB4 comment #2 on MAC address usage issue with the new Ethertype for MIH. THIS IS NOT THE FINAL SOLUTION.

2. 21-08-0187-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

3. 21-08-0187-00-0000 Outline Comment #2 IEEE 802.1Q overview Case Study – 802.1X-Rev Solution Framework for 802.21

4. 21-08-0187-00-0000 Comment #2 In your (revised) response to my comment #145 on the second recirc you state: "The MIH Protocol is interoperable at both L2 and L3. At L2 the MIH Protocol uses an ethertype as specified by MIH Protocol Ethertype to achieve interoperability. The IEEE 802.21 WG has applied for this ethertype with the IEEE ethernet assignment body. At L3 the MIH Protocol frames are encapsulated within IP frames using a transport protocol such as UDP/TCP/SCTP. Please refer to subclause 5.7. for more details on transport considerations. The protocol behavior is specified in clause 8." Firstly, if you haven't yet been allocated an Ethertype, then the specification is incomplete and cannot be published; please note that this isn't simply an administrative/editorial issue, as the Ethertype allocation process involves technical vetting of the protocol specification by the IEEE RA's consultant. Secondly, the specification of the protocol doesn't appear to make any clear statements about how L2 addressing is used "...when destination MIHF ID is not known to a sending MIHF" (8.3.1.) The following sentence in 8.3.1 states: "When MIH protocol message with broadcast MIHF ID is transmitted over data plane, the MIH protocol message is broadcasted over either L2 or L3 data plane." If what you are suggesting is that the protocol makes use of the broadcast MAC address (all F's), then think again; this is not a great idea in a LAN environment, as the scope of that address is literally every station on the LAN. No self-respecting protocol specification uses the broadcast MAC address these days. If you mean to use one or more of the reserved group addresses specified in Clause 8 of IEEE Std 802.1Q that have defined transmission scopes within LAN environments, then you'd better specify which addresses you plan to use, and in what circumstances.

5. 21-08-0187-00-0000 IEEE 802.1Q 802.1Q defines the operation of Bridges that permit the definition, operation, and administration of Virtual LANs (VLANs) within Virtual Bridged LANs 802.1Q allows for individual VLANs to communicate with one another with the use of an L3 router

6. 21-08-0187-00-0000 VLAN-aware Bridge Group Addresses (Table 8-1 of 802.1Q-2005) Filtering for these addresses is permanently configured Filtering for other addresses is based on Filtering Database (see back-up slides) 802 group address allocation tables: http://www.ieee802.org/1/files/public/docs2007/admin-jeffree-standard- group-mac-address-assignments-0307.pdfhttp://www.ieee802.org/1/files/public/docs2007/admin-jeffree-standard- group-mac-address-assignments-0307.pdf Bridge Group Address01-80-C2-00-00-00 Clause 31 (MAC Control) of IEEE Std 802.301-80-C2-00-00-01 Clause 43 (Link Aggregation) and Clause 57 (OAM) of IEEE Std 802.301-80-C2-00-00-02 IEEE Std 802.1X PAE address01-80-C2-00-00-03 Reserved for future standardization—media access method specific01-80-C2-00-00-04 Reserved for future standardization—media access method specific01-80-C2-00-00-05 Reserved for future standardization—VLAN-aware Bridge specific01-80-C2-00-00-06 Reserved for future standardization—VLAN-aware Bridge specific01-80-C2-00-00-07 Reserved for future standardization—VLAN-aware Bridge specific01-80-C2-00-00-08 Reserved for future standardization—VLAN-aware Bridge specific01-80-C2-00-00-09 Reserved for future standardization—VLAN-aware Bridge specific01-80-C2-00-00-0A Reserved for future standardization—VLAN-aware Bridge specific01-80-C2-00-00-0B Reserved for future standardization—VLAN-aware Bridge specific01-80-C2-00-00-0C Reserved for future standardization—VLAN-aware Bridge specific01-80-C2-00-00-0D IEEE Std 802.1AB Link Layer Discovery Protocol multicast address01-80-C2-00-00-0E Reserved for future standardization—VLAN-aware Bridge specific01-80-C2-00-00-0F

7. 21-08-0187-00-0000 Case Study: 802.1X-Rev Both individual and group MAC addresses are used Three group addresses allocated in Table 8-1 of 802.1Q-2005 are used: Bridge group address (01-80-C2-00-00-00) Filtered by MAC and VLAN bridges Not filtered by Provider bridges and provider backbone bridges Provider bridges and provider backbone bridges are defined in 802.1AD PAE group address (01-80-C2-00-00-03) Filtered by MAC bridges, VLAN bridges, provider bridges and provider backbone bridges Not filtered by Two-Port MAC Relays Link Layer Discovery Protocol multicast address (01-80- C2-00-00-0E) Filtered by MAC bridges, VLAN bridges, provider bridges, provider backbone bridges and P801.1aj TPMRs (Two-Port MAC Relays)

8. 21-08-0187-00-0000 What about IEEE 802.21? 8.2.4.3.3 Unsolicited MIH capability discovery “An MIHF discovers peer MIHF entities and their capabilities either by listening to media-specific broadcast messages or media independent MIH capability broadcast messages” 8.2.4.3.4 Solicited MIH capability discovery “An MIHF (the requestor) discovers its peer MIH functions and its capability by broadcasting or unicasting an MIH_Capability_Discover request message to either its broadcast domain or a known MIHF ID and address, respectively. Only MIH network entities respond to a broadcasted MIH_Capability_Discover request.” 8.6.1.1 MIH_Capability_Discover request “If a requesting MIHF entity does not know the destination MIHF entity’s MIHF ID, the requesting MIHF entity fills its destination MIHF ID with broadcast MIHF ID and broadcasts this message over the data plane, either L2 or L3.” MIPSHOP is not working on broadcasting MIH message over L3 According to SB4 comment, broadcast address should not be used

9. 21-08-0187-00-0000 Solution Framework Define two standard group addresses for Ethetype transport: 01-80-C2-00-00-30 : All MIH Points of Service 01-80-C2-00-00-31 : All MIH Mobile Nodes (Bridge group addresses are not applicable to MIH since an End Systems may be MIH nodes) Destination MAC address usage for Ethertype transport: “All MIH Mobile Node” address is used for an MIH_Capability_Discover response message with a broadcast destination MIHF ID “All MIH Points of Service” address is used for an MIH_Capability_Discover request message with a broadcast destination MIHF ID An individual MAC address is used for other MIH messages Operational requirement on 802.1D and 802.1Q bridges: All bridges in a LAN where Ethertype is used for transporting MIH protocol must be configured to forward “All MIH Points of Service” and “All MIH Mobile Nodes” group addresses

10. 21-08-0187-00-0000 Back-Up

11. 21-08-0187-00-0000 Internal organization of the MAC sublayer MAC Relay Entity EISS ISS LLC MS LLC MS Media Access Method Independent Functions Media Access Method Dependent Convergence Functions Media Access Method Specific Functions MAC Service User MAC Service Provider LAN VLAN-aware Bridge

12. 21-08-0187-00-0000 ISS and IESS ISS : Internal Sublayer Service (M_UNITDATA.indication/request) The ISS augments the specification of the MAC Service with elements necessary to the performance of the relay function. Within an end station, these additional elements are considered to be either below the MAC Service boundary, and pertinent only to the operation of the service provider; or local matters not forming part of the peer-to-peer nature of the MAC Service. The ISS excludes MAC-specific features and procedures whose operation is confined to an individual LAN. Supports priority EISS: Enhanced Internal Sublayer Service (EM_UNITDATA.indication/request) The EISS is derived from the ISS (see 6.4) by augmenting that specification with elements necessary to the operation of the tagging and untagging functions of a VLAN-aware Bridge Supports VLAN-tag

13. 21-08-0187-00-0000 Protocol VLAN classification Each instance of the tagging and detagging functions that supports the EISS and implements the optional port-and-protocol-based VLAN classification, shall implement a VID Set, each member of which associates values of a Protocol Group Identifier with a VID Each Untagged and Priority-tagged frame received is assigned a vlan_identifier equal to the VID Set value for the receiving Port and the Protocol Group Identifier selected by matching the received frame with a Protocol Template

14. 21-08-0187-00-0000 Protocol Group Identifier A Protocol Group Identifier designates a group of protocols that will be associated with one member of the VID Set of a Port VID Set : A set of VIDs served by the Port The association of protocols into groups is established by the contents of the Protocol Group Database (Frame Type value, Group ID)  (Group ID, VID) The identifier has scope only within single bridge An implicit Protocol Group Identifier is assigned to frames that match none of the entries in the Protocol An implicit Protocol Group Identifier is assigned to frames that match none of the entries in the Protocol Group Database. Therefore, every incoming frame can be assigned to a Protocol Group Identifier.

15. 21-08-0187-00-0000 Virtual bridged LAN A physical topology comprising LANs, Bridges, and Bridge Ports. Each Bridge Port attaches a LAN to a Bridge and is capable of providing bidirectional connectivity for MAC user data frames. Each LAN is connected to every other LAN by a Bridge and zero or more other LANs and Bridges. Calculation of one or more active topologies, each a loop-free subset of the physical topology Rules for the classification of MAC user data frames that allow each Bridge to allocate, directly or indirectly, each frame to one and only one active topology. Management control of the connectivity provided for differently classified data frames by the selected active topology Implicit or explicit configuration of end station location information, identifying LANs with attached end stations that need to receive user data frames with a given destination address Communication of end station location information to allow Bridges to restrict user data frames to LANs in the path provided to their destination(s) by the chosen active topology.

16. 21-08-0187-00-0000 Forwarding Process Forwarding process consists of Active topology enforcement Ingress Frame filtering based on Destination MAC address and VID Egress Flow metering based on Destination MAC, VID and Priority Queuing

17. 21-08-0187-00-0000 Filtering Database Static, and explicitly configured by management action Static Filtering Entry : filtering based on individual destination address and whether to use Extended Filtering Services Static VLAN Registration Entry: filtering based on VIDs, tagging/untagging rules and whether to use dynamic VLAN membership information Dynamic, and automatically configured by the normal operation of the bridge and the protocol it supports Dynamic Filtering Entries: Created by Learning Process and deleted by aging Group Registration Entries: Created and deleted by GMRP (GARP Multicast Registration Protocol) Dynamic VLAN Registration Entries: Created and deleted by GVRP (GARP VLAN Registration Protocol)

18. 21-08-0187-00-0000 Static Filtering Entries A MAC address specification which comprise: an individual address, or a group address, or All Group addresses, or All Unregistered Group Addresses A VID: a specific VID or a wildcard VID Port Map (per port) “Forward”, “Filter” or “Dynamic” “Dynamic” enables the use of Dynamic Filtering Entries

19. 21-08-0187-00-0000 Dynamic Filtering Entries Dynamic Filtering Entries comprise: An individual MAC address Filtering Identifier (FID) Assigned by the MAC bridge to identify a set of VIDs for which more than one Dynamic Filtering Entry can exist for any individual MAC Address Port Map (per port) “Forward” or “Filter”

20. 21-08-0187-00-0000 Group Registration Entries Group Registration Entries comprise: MAC address: a group address, or All Group addresses, or All Unregistered Group Addresses. VID Port Map (per port) “Registered” or “Not registered”

21. 21-08-0187-00-0000 Static and Dynamic VLAN Registration Entries Static VLAN Registration Entries comprise: VID Port Map (per port) “Fixed”, “Forbidden” or “Normal” –“Normal” enables the use of dynamic VLAN Registration Entries Whether frames are to be VLAN-tagged or untagged Dynamic VLAN Registration Entries comprise: VID Port Map (per port) “Registered” or “Not registered”