Thank you for your question.
I agree with your point that when the PHY configuration of an NPCA STA is set based on the NPCA primary channel, any operation described in the PHY clauses referencing the "primary channel" should be interpreted as referring to the NPCA primary channel.
However, I believe that the specific type of parameter used to indicate the NPCA primary channel is not directly related to the clarity issue you mentioned regarding which primary channel is being referenced in the PHY clauses.
Furthermore, among the CIDs currently assigned to me, there are no comments addressing the need to clarify the referred primary channel in the PHY clauses. Therefore, I believe the most appropriate way to handle this would be to submit a new comment and discuss it during the next round.
Please let me know if you have any other suggestions.
Best regards,
Shawn
Hi Shawn,
Thank you for preparing the CR.
I understand that reusing OPERATING_CHANNEL instead of NPCA_PRIMARY_CHANNEL is intended to make NPCA transparent to the PHY.
If so, during NPCA operation, any reference to the primary channel in the PHY clauses may actually refer to the NPCA primary channel.
However, the baseline already defines the primary channel in REVmf D2.2 as follow:
Could this create an inconsistency between the PHY usage of “primary channel” and the existing definition? Is any clarification needed?
Best regards,
Sixian
From: Shawn Kim <shawn.kim@xxxxxxxxxxxxxx>
Sent: Wednesday, June 24, 2026 10:57 AM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 答复: [STDS-802-11-TGBN] Reminder: Planning towards July F2F
Hi Alfred,
Could you please add the following CRD to the SP queue?11-26/0083r2, LB291: CR for NPCA primitives (4 CIDs)
@NPCA folks,
Regarding the main changes in r2, the NPCA switch and switch-back operations have been modified to be performed using the OPERATING_CHANNEL parameter of the PHYCONFIG_VECTOR.
This change was made in accordance with the PHY group’s decision to remove the NPCA_PRIMARY_CHANNEL parameter and reuse the OPERATING_CHANNEL parameter instead. Additionally, please note that the texts of the NOTES have been simplified.
Please feel free to reach out if you have any questions or if there is anything we should discuss further.
Best regards,
Shawn
2026년 6월 18일 (목) 오후 10:02, Shimi Shilo (TRC) <000018c72fccabed-dmarc-request@xxxxxxxxxxxxxxxxx>님이 작성:
Hi Alfred,
Please add the following document to the PHY queue:
2026
1116
0
TGbn
LB291 CR for Interference Mitigation related comments - Part 2
10 CIDs
@all – this has been uploaded to Mentor, please take a look and let me know if you have any comment.
Best regards,
Shimi
From: Alfred Asterjadhi <asterjadhi@xxxxxxxxx>
Sent: Monday, June 8, 2026 9:08 PM
To: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
Subject: Re: [STDS-802-11-TGBN] 答复: [STDS-802-11-TGBN] Reminder: Planning towards July F2F
Block Ack [
Feedback: Please classify all CIDs of 934 as green tagged and scheduled for presentation during Thursday Joint call.
]
Regards,
AA
On Fri, Jun 5, 2026 at 6:03 PM Liyunbo <00001846a2e5e0c1-dmarc-request@xxxxxxxxxxxxxxxxx> wrote:
HI Alfred,
Could you please add the following document to the MAC queue?
2026
1190
0
TGbn
CR for some miscellaneous CIDs
10 CIDs
together with existing DCNs 11-26/46 and 11-26/934, I will resolve all the remaining CIDs assigned to me.
Doc 11-26/934 is easy, can be presented at anytime.
For 11-26/46 and 11-26/1190, I expect to present them during July F2F meeting.
Regards,
Yunbo
发件人: Pooya Monajemi <pmonajemi@xxxxxxxxx>
发送时间: 2026年6月6日 5:36
收件人: STDS-802-11-TGBN@xxxxxxxxxxxxxxxxx
主题: Re: [STDS-802-11-TGBN] Reminder: Planning towards July F2F
Hello Alfred,
I will have the following two CR documents:
- 11-25/2005, 4CIDs, will be ready by July meeting
- 11-25/2377, 7 CIDs (4 previously deferred and 3 new), will be ready by Jun 20.
Best
Pooya
On Tue, Jun 2, 2026 at 10:06 AM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:
Hello all,
Please consider this as a gentle reminder for the deadline below:
"
Please make sure that you send a CR submission request no later than June 5th, 2026, anywhere on earth (AOE)
- If the submission is not uploaded when the CR submission request is sent then please provide an ETA as to when the CR is ready to be presented (making sure that the CR submission is uploaded at least 24 hours prior to that meeting slot)
"
Regards,
Alfred
On Fri, May 29, 2026 at 8:36 AM Alfred Asterjadhi <asterjadhi@xxxxxxxxx> wrote:
Hello all,
I am extending the announcement we made during the May 28th meeting and setting some deadlines so that we can plan for the next couple of months.
- Planning:
- Prioritization of CRs will continue as usual, except that temporarily expanded the time allocated to MAC normal CR queue to one hour
- Green tagging will continue as usual, except that-when possible, green tagging will be performed also on CRs from normal MAC queue.
- Joint meeting slots will continue to dedicate time for prioritized MAC CRs
- Call for prioritized submissions and submissions from top 40 assignees:
- There is limited number of CR submissions with ≥10 CIDs.
- Please submit CRs with ≥10 CIDs so that they can be prioritised
- There is a limited number of CR submissions from the top 20 assignees.
- Please submit CRs (preferably with ≥10 CIDs) and send requests/upload them as soon as possible (upload at least 24 hours in advance of the scheduled meeting slot).
- Alternatively provide ETAs as to when ready to present.
In summary, if you are planning a CR submission (the items below are highly recommended for MAC CR submissions, and advisory for PHY/Joint CR submission):
- Please make sure that you send a CR submission request no later than June 5th, 2026, anywhere on earth (AOE)
- If the submission is not uploaded when the CR submission request is sent then please provide an ETA as to when the CR is ready to be presented (making sure that the CR submission is uploaded at least 24 hours prior to that meeting slot)
- Please share the CR submissions with the TGbn group via the reflector as early as possible to seek early feedback from members.
Let me know if you have any questions.
Regards,
Alfred
--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Cell #: +1 858 263 9445
Office #: +1 858 658 5302
--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Cell #: +1 858 263 9445
Office #: +1 858 658 5302
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
--
Alfred Asterjadhi, PhD
IEEE802.11 TGbe/TGbn Chair,
Qualcomm Technologies Inc.
Cell #: +1 858 263 9445
Office #: +1 858 658 5302
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
--
Sanghyun Kim, Ph.D
WILUS Inc.
5th Fl., 216 Hwangsaeul-ro Bundang-gu,
Seongnam-si Gyeonggi-do 13595, Korea
T +82 31 712 0523
www.wilusgroup.com
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
WILUS Inc.
5th Fl., 216 Hwangsaeul-ro Bundang-gu,
Seongnam-si Gyeonggi-do 13595, Korea
T +82 31 712 0523
www.wilusgroup.com