TGbh reflector, Focusing on the April 4 call, I would like to suggest that we consider the results of the vote at the F2F in Atlanta, on how to proceed. As you all should know, I suggested that we set aside the additional solution proposals for now, and (effectively) that we proceed to D1.0 with the D0.2 technical content. That motion got 74% support (but needed 75% to pass). So, we need to decide how we can best proceed. I propose that we organize the discussion as follows: - Review/confirm our status on CC41 comments, except those requesting an additional solution be added. That is, confirm that there are no concerns with the proposed resolutions in the latest comments tracking spreadsheet (11-22/0973r20) marked as “Ready for motion” (and highlighted in green).
- Consider CID 35, and an off-line proposal from Amelia (the commenter) working with Dan:
- Insert a new paragraph at the end of 12.2.11, "An identifier may optionally be constructed by the network using the procedure in Annex Z, or the network may employ a different mechanism provided it affords comparable security and privacy."
- Consider CIDs 19 and 20, and whether the group wants to pursue a PASN mechanism for D1.0, and if so consider updates to 11-22/1806r0 per the discussion in Atlanta.
- Discuss further our consensus on “Way forward?” CIDs and any consideration of adding another solution, into a D1.0. At this time I am aware of two potential solutions being proposed:
- Are there any other options/proposals anyone suggests?
- What is the group consensus on these proposals, for inclusion in D1.0? Can we reach some consensus (more straw polls, etc., if helpful) on a way to reach D1.0?
- Plan for upcoming teleconferences:
- If we need additional contributions, when will they be ready? (We have weekly teleconference slots scheduled, when will they be useful, and not just a re-hash?)
- Should we plan for any motions (for example, on the “Ready for motion” CIDs and CIDs 35, 19 and/or 20?)?
- My target, of course, is to have a plan that gets us to a D1.0 consensus in the May session.
If anyone has comments on the above, or other suggestions, please let me know. I’ll put this into the usual agenda deck, shortly. Mark From: mark.hamilton2152@xxxxxxxxx <mark.hamilton2152@xxxxxxxxx>
Sent: Wednesday, March 22, 2023 10:19 AM
To: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: 802.11 TGbh teleconferences through May All, With 10 days’ notice, I am announcing the following teleconference schedule for 802.11 TGbh: - Tuesdays, 9:30 – 11:30 am ET:
- April 4, 11, 18, 25
- May 2, 9
Call in details on Google calendar and 802.11 web page, as usual, and links below: Mark
To unsubscribe from the STDS-802-11-TGBH list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBH&A=1 |