Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Alfred,
Could you help add the following CR document to the Joint agenda?
-23/716r0, LB271 CR for clause 6.3
Best Regards!
李炎 Li Yan
标准预研工程师 Standard Development Engineer
架构团队/有线规划部/有线产品经营部 Architecture Team/Wireline Product Planning Dept/Wireline Product Operation
南京市雨花台区软件大道50号中兴通讯 ZTE Corporation,50 Software Avenue, Yuhuatai District, Nanjing, P.R.China, 210012 T: +86 755 xxxxxxxx F:+86 15850568971M: +86 xxxxxxxxxxx E: li.yan16@xxxxxxxxxx |
Hi Alfred
Could you help add the following CR document to the MAC agenda?
-23/688r0, LB271: CR for 35.3.5.4
Thanks
Best Regards
Insun
From: Alfred Asterjadhi [mailto:asterjadhi@xxxxxxxxx]
Sent: Friday, April 21, 2023 2:11 AM
To: STDS-802-11-TGBE@xxxxxxxxxxxxxxxxx
Subject: [STDS-802-11-TGBE] Announcements made during Joint Conf Call of 04/19
Hello all,
I am sending the announcements that were made during yesterday's Joint conf call to the reflector as well:
· Plan for aligning TGbe draft to REVme draft:
§ TGbe editor incorporates editorial changes to align the drafts as per his review and prepare a preliminary draft that is to be shared with the review volunteers (ETA May 12, 2023). These changes are expected to be included in D3.2 of TGbe.
· If there are thecnical conflicts between TGbe draft and REVme draft, then the TGbe editor will add an Editor’s Note to TGbe D3.2 near the conflict to point out the inconsistency between the drafts.
§ Review volunteers (a call for volunteers was sent by the TGbe Editor in February 2023) to review the subclauses they volunteered and provide feedback regarding misalignments to the Editor by May 31, 2023)
§ TGbe is expected to discuss and solve any such technical conflicts, as part of CR process if a CID already exists or as a bug fix if a CID does not exist (tagged with [#Fix]).
· Call for assignees to ramp up LB271 comment resolutions:
§ By end of April 2023 (MAC) assignees are expected to have resolved around 20% of the comments assigned to them, and the number jumps to 40% by the and of the planned May MAC ad-hoc.
· If you are an assignee who has resolved less than 20% (40% after MAC Ad-hoc) of the comments assigned to you then please:
· Prepare and upload CRs that solve enough CIDs to (at least) be in track with the expected CR trends (requests for addition to the agenda to be sent by the end of April, and upload of the doc within a week of said request), or
· Coordinate with TGbe officers and TTT members to re-assign some CIDs to (TTT) members by end of April to align with the expected CR trend.
· Otherwise, TGbe officers will initiate the proportional distribution of a subset of the CIDs to TTT members so that the CIDs assigned to assignees remains aligned to expected CR targets (plan is to initially focus on Top 20 assignees with limited number of resolved CIDs (see table above).
· Call for assignees to check on “comments presented and no consensus yet”
§ There are currently 115 CIDs in this category (based on 272r15).
§ CIDs in that list, for which there has been no request for SP within two weeks after the presentation, have ended in quarantine.
· Motions for quarantined CIDs (refer to Item 10 of the guidelines) are expected to be run during the May F2F meeting
Let me know if you have any further questions and/or clarifications.
Regards,
AA
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1
To unsubscribe from the STDS-802-11-TGBE list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBE&A=1