PLE Comment Resolution March 2007 Date: 2007-03-14 Authors: Notice: This document has been prepared to assist IEEE 802.11. 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. Release: 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.11. Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures <http:// ieee802.org/guides/bylaws/sb-bylaws.pdf>, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair <stuart.kerry@philips.com> as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE 802.11 Working Group. If you have questions, contact the IEEE Patent Committee Administrator at <patcom@ieee.org>. Zhao and Walker, Intel Corp

March 2007 Abstract This submission summarizes the proposed updates to resolve comments from LB93 on Peer Link Establishment protocol, as specified in 11-07/440r0. Zhao and Walker, Intel Corp

Agenda Protocol overview Comment resolution summary Major updates March 2007 Agenda Protocol overview Comment resolution summary Major updates Finite State Machine Configuration parameters Randomness of link IDs Interface Reason codes Zhao and Walker, Intel Corp

Protocol Overview March 2007 A B A B Open(A, B, LinkIDA) Open(B, A, LinkIDB) Confirm(B, A, LinkIDB, LinkIDA) Confirm(A, B, LinkIDA, LinkIDB) Open(B, A, LinkIDB) Open(A, B, LinkIDA) A B Confirm(B, A, LinkIDB, LinkIDA) Confirm(A, B, LinkIDA, LinkIDB) Zhao and Walker, Intel Corp

Protocol Design Overall protocol design is unchanged March 2007 Protocol Design Overall protocol design is unchanged 4-message exchange Link IDs Holding state Timer model Name change: Peer Link Management protocol New name represents the protocol functionality better Zhao and Walker, Intel Corp

Summary of PLE comments March 2007 Summary of PLE comments Finite state machine CIDs 1148, 1647, 3624, 3837, 3975, 3976, 4339, 4346, 4347, 4348, 4351, 4353, 4356, 4359, 4360, 4361, 3839, 4216, 4217, 4354, 4363 Configuration parameters CIDs 3981, 4355, 4362 Randomness of link IDs CIDs 12, 1183, 1184, 1185, 1811, 1952, 3835, 4979, 1594, 2427 Reason codes CIDs 203, 1147, 1638, 1811, 2452, 2672, 5301, 5302, 5303, 5304, 5305, 5309, 5312, 5313, 5314, 5315, 5319, 5641 Interface specification CIDs 1146, 1209, 2193, 2428, 3980, 4321, 4748, 5264, 5265, 5266, 5267, 5268, 5269, 5272, 5273, 5274, 5275, 5277, 5278, 5279, 5280, 5281, 5282, 5283, 5284, 5286, 5287, 5288, 5292, 5293, 5295, 5296, 5297, 5299, 5300, 5306, 5307, 5308, 5311, 5310, 5311, 5316, 5317, 5318 Miscellaneous Issues CIDs 2325, 3560, 4325, 3623, 4783, 5656, 4805, 1210, 2191, 3833 Zhao and Walker, Intel Corp

Comments on Finite State Machine March 2007 Comments on Finite State Machine Comments CIDs 1148, 1647, 3624, 3837, 3975, 3976, 4339, 4346, 4347, 4348, 4351, 4353, 4356, 4359, 4360, 4361, 3839, 4216, 4217, 4354, 4363 Issues Conditional state transition for message processing and retry timer Add a diagram Abbreviations for specification Need a link IDs? (see see Link ID issue) Need 4-message exchange? (see protocol requirements) Misc issues Zhao and Walker, Intel Corp

Updates to FSM More events March 2007 Updates to FSM More events Message classification OPN_ACPT, OPN_RJCT, OPN_IGNR CNF_ACPT, CNF_RJCT, CNF_RJCT CLS_ACPT, CLS_IGNR Timeout with MaxRetries TOR1 – Continue retry TOR2 – Reach the limit All states, events, actions are specified using abbreviations Add a diagram Clean up text on state transition Zhao and Walker, Intel Corp

March 2007 Example of Updated FSM Zhao and Walker, Intel Corp

Comments on Configuration Parameters March 2007 Comments on Configuration Parameters Comments, CIDs 3981, 4355, 4362 Issue: Configuration parameters are not defined No description on how to handle them Zhao and Walker, Intel Corp

Updates Define configuration parameters for message processing March 2007 Updates Define configuration parameters for message processing Fields in Mesh Capability element “Operating as MP” Supporting Power Save Mode Require Power Save Mode from Peer Supporting Synchronization MDA Active Request in Mesh Fields in Active Profile Announcement Active Protocol ID Active Metric ID RSN information element Zhao and Walker, Intel Corp

Comments on Link IDs Comments Issues March 2007 Comments on Link IDs Comments CIDs 12, 1183, 1184, 1185, 1811, 1951, 3835, 4979, 1594, 2427 Issues Why they are random? What’s the scope of random numbers? 4-octet number are too long Zhao and Walker, Intel Corp

Updates Requirement of link IDs March 2007 Updates Requirement of link IDs Unique among all peer links by the MP Haven’t been used recently to identify a peer link by the MP Hence, the link IDs can be either random or deterministic Resolution: Use deterministic numbers Clearly specify the requirements Length: 2 octets Zhao and Walker, Intel Corp

Comments on Reason Codes March 2007 Comments on Reason Codes Comments CIDs 203, 1147, 1638, 1811, 2452, 2672, 5301, 5302, 5303, 5304, 5305, 5309, 5312, 5313, 5314, 5315, 5319, 5641, 1952 Issues Should try to re-use existing reason codes Define new ones in Clause 7.3.17 Consistent specification on reason code usage Zhao and Walker, Intel Corp

Updates March 2007 46—65 535 Reserved 46 Reason code Meaning 46—65 535 Reserved 46 “MESH-LINK-CANCELLED”. IEEE 802.11 SME cancels the link instance with the reason other than reaching the maximum number of neighbors 47 “MESH-MAX-NEIGHBORS”. The Mesh Point has reached the supported maximum number of neighbors 48 “MESH-CAPABILITY-POLICY-VIOLATION”. The received information violates the Mesh Capability policy configured in the Mesh Point profile 49 “MESH-CLOSE-RCVD”. The Mesh Point has received a Peer Link Close message requesting to close the peer link. 50 “MESH-MAX-RETRIES”. The Mesh Point has re-sent dot11MeshMaxRetries Peer Link Open messages, without receiving a Peer Link Confirm message. 51 “MESH-CONFIRM-TIMEOUT”. The confirmTimer for the mesh peer link instance times out. 52—65 535 Zhao and Walker, Intel Corp

Comments on Interface Comments Issues March 2007 Comments on Interface Comments CIDs 1146, 1209, 2193, 2428, 3980, 4321, 4748, 5264, 5265, 5266, 5267, 5268, 5269, 5272, 5273, 5274, 5275, 5277, 5278, 5279, 5280, 5281, 5282, 5283, 5284, 5286, 5287, 5288, 5292, 5293, 5295, 5296, 5297, 5299, 5300, 5306, 5307, 5308, 5311, 5310, 5311, 5316, 5317, 5318 Issues PassiveOpen, ActiveOpen, CancelLink, SignalStatus primitives are not needed Inconsistency in specification Vague specification on how to use them Incorrect specification on interaction between SME and MAC Zhao and Walker, Intel Corp

Updates Interface is essential for control the behavior of the MP March 2007 Updates Interface is essential for control the behavior of the MP Control creation and deletion of FSM Control protocol initiation Control # peer links Updated definition MLME-PassivePeerLinkOpen(localLinkID) MLME-ActivePeerLinkOpen (peerMAC, localLinkID) MLME-CancelPeerLink(localLinkID, ReasonCode) MLME-SignalPeerLinkStatus.indication(localLinkID, statusCode) Zhao and Walker, Intel Corp

Conclusions Keep the basic design of PLM Updates to March 2007 Conclusions Keep the basic design of PLM Updates to State Machine Deterministic Link IDs Detailed specification on interface, reason code, parameter configuration Propose full resolution to 106 comments and partial resolution to 5 comments Zhao and Walker, Intel Corp