Thanks To Mark HAMILTON for taking notes for Wednesday PM1. Minutes for 802.11 TG REVmc on Wednesday November 5, 2014 PM2 16:00-18:00 – by Dorothy STANLEY (Aruba) at 4:03pm Called to Review draft agenda 11-14/1421 3GPP reference changes, 11-14/1353 Extend element ID 11-14/1518 Depreciation (or other modification) of 11b: Graham SMITH, 11-14/1358 Mark HAMILTON – ISO comments 11-13-0123, Editor CID Add 11-14-1003 Wookbong to Thursday PM1 Add 11-14/1517 Eldad to Thursday PM1 Add 11-14/973r3 Matt FISCHER to Thursday PM1 No objection, approved 3GPP reference changes, 11-14/1421r0 (Stephen McCann) Response to liaison in 11-14/1411r0 Liaison is addressing the moving of the generic container used in WLAN from one TS to another. This reference is used in .11u Reviewed 11-14/1421r0 We should also send a liaison back to 3GPP that they should reference the published 802.11 spec, now that 802.11u has been incorporated. Will consider this document for motion tomorrow (Thursday) Extended element ID space, 11-14/1353r1 (Adrian Stephens) Recall the concern running out of ANA assigned element IDs, per the discussion in the plenary Reviewed document. Has believed requirements, and some Options for solutions Option 1: allocate an element ID (say, 254), which indicates that the field is actually a 1 octet element ID extension field, and then “Information” Information octets Option 1b: Just noting that we can do this more than once, creating several such blocks, with different element IDs Open 2: do the same thing, but make the new Information field have 2 octets of extension ID, to get 64K new IDs. Decisions: Do we restrict the allocation of existing (remaining) element IDs? This is really a question for the WG. If we have both Option 1 and Option 2 (we could do both), how do we decide which one a given usage should use?
Thanks To Mark HAMILTON for taking notes for Wednesday PM1. Minutes for 802.11 TG REVmc on Wednesday November 5, 2014 – PM2 16:00-18:00 Called to by Dorothy STANLEY (Aruba) at 4:03pm Review draft agenda 11-14/1421 3GPP reference changes, 11-14/1353 Extend element ID 11-14/1518 Depreciation (or other modification) of 11b: Graham SMITH, 11-14/1358 – Mark HAMILTON ISO comments 11-13-0123, Editor CID Add 11-14-1003 Wookbong to Thursday PM1 Add 11-14/1517 Eldad to Thursday PM1 Add 11-14/973r3 Matt FISCHER to Thursday PM1 No objection, approved 3GPP reference changes, 11-14/1421r0 (Stephen McCann) Response to liaison in 11-14/1411r0 Liaison is addressing the moving of the generic container used in WLAN from one TS to another. This reference is used in .11u Reviewed 11-14/1421r0 We should also send a liaison back to 3GPP that they should reference the published 802.11 spec, now that 802.11u has been incorporated. Will consider this document for motion tomorrow (Thursday) Extended element ID space, 11-14/1353r1 (Adrian Stephens) Recall the concern running out of ANA assigned element IDs, per the discussion in the plenary Reviewed document. Has believed requirements, and some Options for solutions Option 1: allocate an element ID (say, 254), which indicates that the “Information” field is actually a 1 octet element ID extension field, and then Information octets Option 1b: Just noting that we can do this more than once, creating several such blocks, with different element IDs Open 2: do the same thing, but make the new Information field have 2 octets of extension ID, to get 64K new IDs. Decisions: Do we restrict the allocation of existing (remaining) element IDs? This is really a question for the WG. If we have both Option 1 and Option 2 (we could do both), how do we decide which one a given usage should use?
11-14-1509-01-000m-revmc-minutes-for-november-san-antonio.docx