Hi Matt,
Thanks for the work! A few comments as attached.
BR,
Chaoming
发件人: Matthew Fischer <matthew.fischer@xxxxxxxxx>
发送时间: 2024年11月28日
6:22
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBN] [EXTERNAL] [STDS-802-11-TGBN] PDT-MAC-NPCA
Based on Salvatore's comments, an r4:
Dear Matthew,
Many thanks for preparing this document, and the specification text.
Please find embedded in the attachment, a few comments for your consideration.
As for the terminology, since the expansion of the acronym will be likely used/defined once, then I personally do not have a strong opinion😊
Have a good thanksgiving,
-Salvatore (Nokia)
Thanks to those who submitted comments on 1762r1.
Due to the large volume of motions that were passed regarding the NPCA feature, there is a new revision of 1762 that has been uploaded.
This revision is constructed from several comments/proposed text sections that I received from various TTT members and then consolidated into
the r2 version of 1762.
This latest revision can be found on the server:
Note that because of the amount of changes made to the earlier revision of the document, those comments that were sent to this email thread
were not directly addressed.
As to the comment from John Wullert regarding terminology, I agree that the term NPCA primary channel seems a bit clumsy upon expansion of
the acronym.
John's suggestion is an interesting alternative, but I would not unilaterally adopt it without first soliciting additional opinion on the matter.
[of course, at this point, no one else has responded... so maybe there is no other opinion!]
[and I'll note that if you do not expand the acronym, the term isn't so clumsy]
[and I'll note that even with John's proposal, upon expansion, you still get a "double primary" problem - e.g. APCA Primary Channel = Alternate
Primary Channel Access Primary Channel]
How about TACA - Temporary Alternate Channel Access
No change has yet been made to that term.
Matt,
Thanks for this. The one comment I have is related to terminology
– It seems to me that “non-primary channel access primary channel”, the expansion of
“NPCA primary channel”, has the potential to lead to confusion. It might be better to call this feature
“Alternate Primary Channel Access”? In that case, what is currently labeled
“NPCA primary channel” would become the
“alternate primary channel”, which seems much more descriptive and clearer to me. (Given that the motions use NPCA, it may be that this is the wrong place to have the discussion…)
John
From: Matthew Fischer <matthew.fischer@xxxxxxxxx>
Sent: Wednesday, November 6, 2024 5:55 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: [EXTERNAL] [STDS-802-11-TGBN] PDT-MAC-NPCA
This is the initial email for:
Proposed Draft Text for NPCA
As POC,I have created an initial PDT document which is
11-24-1762:
The NPCA feature currently has one passing motion.
The initial PDT-MAC-NPCA document r0 includes proposed text based on this single motion.
As additional motions are passed, we will add to the text in the document.
I have taken the author list from the TTT list found in the document
11-24-1698-11-00bn-tgbn-d0-1-spec-text-volunteers-and-status
If you have volunteered for the NPCA TTT, please check the author list of 1762r0.
If your name is spelled incorrectly, or is missing an affiliation, or has an incorrect affiliation, or if your name is missing entirely, or if you are in the
list and do not wish to be included in the author list, then please send an individual email to:
to indicate which particular problem exists so that I can update the document.
At the end of this week, I will upload an r1 with such corrections.
Feel free to send any comments on the existing PDT (i.e. the draft text, not the author list) in 1762r0 as a
response to this email, so that all TTT members may see your comment and so that we can discuss the comment and then debate any changes to the document. This will be the general process going forward for text that is included in the document. I hope
that there is little discussion on the initial text, since it is so high level and there are only a few sentences. If there is a firestorm over these first few sentences, then I will be anxiously awaiting the next passing motion...
At some point, the group should pass a few more motions relating to NPCA, and when this happens, then we will try to find volunteers to create draft text sections
corresponding to those new motions. Depending on the size/complexity of that text, it should appear for discussion within this email thread either as:
a) text that is directly included as native text within an email sent to this thread (usually for small text additions/changes)
b) text included within a new WORD document that does not need to be an official 802.11 submission or uploaded to the server, since the text on its own will not
be subject to a motion, but will only be subject to motion as part of a complete NPCA PDT document (i.e. 1762rx) - such a document would be sent as an attachment to this email thread for discussion
c) text included within a copy of the 1762rx WORD document, showing additions and changes to the existing 1762rx doc that again, should not be uploaded to the
server, but attached to the email thread.
We will try, with any new proposed draft text, to discuss new proposed text within this thread and come to a super-majority regarding such new text (e.g. 75%
of the TTT membership, whatever that is). I do not want to use the word consensus, because that implies near unanimous agreement and I feel that such a goal is impractical. But suggesting something like 75% is also problematic, as there is no real defined
TTT membership - it is fluid. So there will be a judgement call as to when we should close the debate on any new text; Such a decision will occur when the number of objections quiets down to some small number of members (e.g. <25%, which is currently estimated
to be about 15 people - but that too will be a judgement call because someone could invite a dozen of their friends to send an objection to the thread even though they are not listed as TTT members and there probably is nothing that can be done about that).
In cases where such quieting does not occur, then we will have to throw the text into TGbn for a straw poll and update our document 1762rx based on that outcome.
I hope it will be generally obvious when we can accept text vs when we need to perform an SP in the TG, and I hope that we do not need to frequently submit to
SPs in the TG or we will never complete a D0.1....
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or
entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering
the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the
sender, delete it from your computer, and destroy any printed copy of it.
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
--
To unsubscribe from the STDS-802-11-TGBN list, click the following link:
https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
To unsubscribe from the STDS-802-11-TGBN list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBN&A=1
|