| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Colleagues, I'm slow this cycle in proposing comments to the PARs from other WGs ad hoc. Below is what I propose using as the basis for discussion on Monday. I haven’t seen any proposed comments from others. —Bob New Standard PAR ---------------- IEEE P802.15.14 Standard: Ad-Hoc Impulse Radio Ultra Wideband Wireless Networks PAR: https://mentor.ieee.org/802.15/dcn/21/15-21-0274-04-0014-sg14-ns-uwb-par-working-draft.docx General — Even though this document might be copied from myProject output, it is not output from myProject, and therefore, reduces confidence that the correct form is being used, and that the NesCom submittal will match what is reviewed. Further, there are formatting problems that should be fixed when entering into myProject, and some of the formatting indicates changes in the docx that likely didn’t come from myProject (e.g., . 3.1 — Why does the WG name not agree with what is listed on ieee802.org? Did the WG change its name without approval of the EC, or is the EC page wrong? (The draft PAR WG name does agree with the WG name in myProject.) 5.5 — Typo: “805.15.4w” should be 802.15.4w. The IEEE standards numbers in the answer should be prefaced by “IEEE Std”. Similar errors are found throughout the PAR, sometimes including IEEE but not Std (e.g., in 8.1). 5.6 — Grammar: “and manufacturers and” 6.1.2, Explanation — "Unique Identifiers (EUI)” should be “Extended Unique Identifiers (EUI)”. 7.1 — The response only partially answers the question. What project will remove the extracted content from IEEE Std 802.15.4-2020. If a future revision project will remove the IEEE Std 802.15.4-2020 content after approval or P802.15.14 and P802.14.15 that should be stated. Or, should there be a co-contingent revision project of IEEE 802.15.4-2020 to run in parallel. Is there any contingency on the active project P802.15.4aa? 7.1 — There appear to be 30 Letters of Assurance on IEEE Std 802.15.4 and its amendments in the PatCom LOA listing. A reminder that LOAs only apply to a standard, and new LOAs will need to be obtained for this new standard for the material where potentially essential patent claims covered by some of these LOAs may be applicable to the material extracted from IEEE Std 802.15.4. 7.1.1 — "P802.15.4-2020" is neither a proper standard or project number. There is no P802.15.4 revision project to be found in myProject nor in the package of July PARs. Typo in the title "IEEE Standard for Low Rate Wireless Networks” the published standard uses “Low-Rate“. No comments. IEEE P802.15.15 Standard: Ad-Hoc Low-Rate Wireless Networks PAR: https://mentor.ieee.org/802.15/dcn/21/15-21-0265-03-0015-sg15-ns-nb-par-working-draft.docx 3.1 — Why does the WG name not agree with what is listed on ieee802.org? Did the WG change its name without approval of the EC, or is the EC page wrong? (The draft PAR WG name does agree with the WG name in myProject.) 5.2 — Different form than in the project title: “adhoc” should be "ad-hoc”. 5.5 — Typo: “805.15.4w” should be 802.15.4w. The IEEE standards numbers in the answer should be prefaced by “IEEE Std”. Similar errors are found throughout the PAR, sometimes including IEEE but not Std (e.g., in 8.1). 6.1.2, Explanation — "Unique Identifiers (EUI)” should be “Extended Unique Identifiers (EUI)”. 7.1 — The response only partially answers the question. What project will remove the extracted content from IEEE Std 802.15.4-2020. If a future revision project will remove the IEEE Std 802.15.4-2020 content after approval or P802.15.14 and P802.14.15 that should be stated. Or, should there be a co-contingent revision project of IEEE 802.15.4-2020 to run in parallel. Is there any contingency on the active project P802.15.4aa? 7.1 — There appear to be 30 Letters of Assurance on IEEE Std 802.15.4 and its amendments in the PatCom LOA listing. A reminder that LOAs only apply to a standard, and new LOAs will need to be obtained for this new standard for the material where potentially essential patent claims covered by some of these LOAs may be applicable to the material extracted from IEEE Std 802.15.4. 7.1.1 — "P802.15.4-2020" is neither a proper standard or project number. There is no P802.15.4 revision project to be found in myProject nor in the package of July PARs. Typo in the title "IEEE Standard for Low?Rate Wireless Networks” the “?” should be a “-“. No comments. Amendment PARs -------------- 802.15.6a Amendment: Dependable Human and Vehicle Body Area Networks, PAR and CSD PAR: https://mentor.ieee.org/802.15/dcn/21/15-21-0259-03-006a-ieee-802-15-6a-par-draft.pdf 3.1 — Why does the WG name not agree with what is listed on ieee802.org? Did the WG change its name without approval of the EC, or is the EC page wrong? (The draft PAR WG name does agree with the WG name in myProject.) 5.4 — The mix of text for medical and auto is very awkward and deserves a better change than the new second paragraph. Perhaps: "Additionally this standard provides enhanced dependability that is required for some medical and automotive use cases. This includes remote medical healthcare, therapy and other monitoring that can enhance quality of life (QoL) in various population segments." 1.2.1, a — "IEEE 802.15.6-2012” should be "IEEE Std 802.15.6-2012”. Second paragraph “Enhancement to” should be "The enhancement of" 1.2.4, a — "IEEE 802.15.6-2012” should be "IEEE Std 802.15.6-2012”. Second paragraph “Enhancement to” should be "The enhancement of” 802.15.4ab Amendment: Enhanced Ultra Wide-Band (UWB) Physical Layers (PHYs) and Associated MAC Enhancements PAR: https://mentor.ieee.org/802.15/dcn/21/15-21-0126-02-nuwb-p802-15-4ab-par-draft-from-myproject.pdf 3.1 — Why does the WG name not agree with what is listed on ieee802.org? Did the WG change its name without approval of the EC, or is the EC page wrong? (The draft PAR WG name does agree with the WG name in myProject.) Compatability, b — The response from 802.1 should be included even though it is largely predictable. ------------------------ IEEE P802.15.4-2020/Cor1 Corrigendum 1:Correction of errors preventing backward compatibility PAR: https://mentor.ieee.org/802.15/dcn/21/15-21-0270-04-Cor2-tg4-2020-cor1-par-modification-draft.docx General — I don’t see how the original Corrigendum PAR got approve. it does not appear that this proposed work is properly a corrigendum, but rather should be an amendment. (It seems to be intended to fix poor specifications related to compatibility, not errors.) From the IEEE SA Standards Board Operations Manual:
General — This appears to be a markup to the Corrigendum PAR is this really what myProject would produce? (I can’t verify in myProject.) 5.1.b "errors found in IEEE Std 802.15.4-2020 and its amendments." Can we do a corrigendum for multiple documents????????? I guess so since it was an approved corrigendum. PAR Extension request --------------------- 802.1Qcw - Amendment: YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing PAR: https://www.ieee802.org/1/files/public/docs2021/cw-PAR-extension-0521-v01.pdf 2 — I assume the second through fourth paragraphs are about the revision (the fourth could apply to either the revision or the amendment), because of the answer to 4. But it could be if the assumption is correct, merging the one sentence paragraphs into one or repeating references to clarify to which project the sentence applies would eliminate confusion. “P802.1Q-Rev” may be an 802.1 internal reference, but the revision project is “P802.1Q”. 3.3 — Don’t know if myProject allows a way to fix the in-person number, but I doubt the project has met in person 6 times in the last year. No comments. 802.1Qcj - Amendment: Automatic Attachment to Provider Backbone Bridging (PBB) services PAR: https://www.ieee802.org/1/files/public/docs2021/cj-PAR-extension-0521-v01.pdf 2 — On this one the second and third paragraphs seem to apply to the amendment project. With both the revision and the project being part of the justification for extension, making it clear which project is the subject of the paragraphs is important. “P802.1Q-Rev” may be an 802.1 internal reference, but the revision project is “P802.1Q”. 3.3 — Don’t know if myProject allows a way to fix the in-person number, but I doubt the project has met in person 6 times in the last year. No comments. IEEE P802.15.13 Standard: Multi-Gigabit per Second Optical Wireless Communications (OWC) PAR: https://mentor.ieee.org/802.15/dcn/21/15-21-0267-01-0000-par-extension-request-for-p802-15-13.docx 3.3 — Don’t know if myProject allows a way to fix the in-person number, but I doubt the project has met in person 6 times in the last year. 3.4 Four drafts (answer to 3.6) in 10 months (start of drafting until SA ballot on D4) doesn’t work out to 6 per year. No comment. ICAID renewal ------------- 802.1 - Industry Connetions: Nendica ICAID: https://mentor.ieee.org/802.1/dcn/21/1-21-0011-05-ICne-draft-nendica-icaid-renewal.docx No comment. To unsubscribe from the STDS-802-3-DIALOG list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-DIALOG&A=1 |