Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [STDS-802-11-TGBH] 802.11 TGbh teleconferences through May



Thanks for your comments, Jay.

 

I agree, let’s not stress the result of that motion.

 

My intention for the call, per the agenda outline below, is to focus on how we proceed from here.  I only added the information at the start about the failed motion to provide the background and status for those who were not in attendance at that F2F meeting.

 

If you have any suggestions for change/comments on the agenda outline, please let me know.  As I hope you can see, I’m trying to reach finalization on all the open easier(I hope?) CIDs, and then dive into the discussion about the “Way forward?” topic.

 

Mark

 

From: Zhijie Yang (NSB) <zhijie.yang@xxxxxxxxxxxxxxx>
Sent: Thursday, March 23, 2023 1:22 AM
To: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBH] 802.11 TGbh teleconferences through May

 

Hi Mark,

 

I suggest we refrain from stressing the result on any failed motion. If you look at the voting member name during the call, some members just make their ballot on the motion and then drop the call even if they don’t follow anything talked in 11bh meeting. If we follow such working styles, we can also invite other IEEE voting members to vote it, as the results, we will fall into the dead cycle again.

IMHO, we should focus on how much the compromise the group can made, no compromise, hard to move forward.

 

 

Thanks

 

Best Regards

 

Jay Yang

 

From: Mark Hamilton <mark.hamilton2152@xxxxxxxxx>
Sent: 2023323 1:25
To: STDS-802-11-TGBH@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBH] 802.11 TGbh teleconferences through May

 

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:

When

Title

Meeting

Tue, 4 Apr 2023 09:30-11:30

TGbh

Webex-11a: 2331 386 0598

Tue, 11 Apr 2023 09:30-11:30

TGbh

Webex-11a: 2332 568 8559

Tue, 18 Apr 2023 09:30-11:30

TGbh

Webex-11a: 2343 362 1849

Tue, 25 Apr 2023 09:30-11:30

TGbh

Webex-11a: 2330 765 9100

Tue, 2 May 2023 09:30-11:30

TGbh

Webex-11a: 2347 009 8354

Tue, 9 May 2023 09:30-11:30

TGbh

Webex-11a: 2343 213 2095

 

 

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


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


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