| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Colleagues, Though I will not be attending the November plenary, as a distraction from world events, I ended up reviewing November PARs from other WGs. Below are my observations in case there is a desire to submit comments from 802.3. —Bob Grow No comments. __________ 802.1ACea - Amendment - Support for IEEE Std 802.15.6 PAR, 1.1.2,b — Could be improved. The project isn’t adding “wireless specifications” as many would interpret that term. It is adding a wireless network type to the set of IEEE 802 networks supported by the specified service interface. Remedy: Replace with: The project will add IEEE Std 801.15.6 to the set of IEEE 802 networks supported by the service interface. The project will not involve coexistence issues related to the use of wireless spectrum. CSD, 1.2.1,a — This doesn’t really answer broad sets of applicability and is difficult to parse. Remedy: There is a need for interconnecting wireless personal networks to infrastructure in multiple applications where MAC bridges can simplify access for 801.15.6 network connection to a data center. One target application for example is for hospitals and healthcare providers, to support a wide range of personal wireless devices. Both healthcare providers and patients will benefit from simplified networks that aggregate data streams while providing guaranteed delivery to remote data centers supporting both healthcare monitoring and emergency events. Other applications will similarly benefit from use of 802.1 bridged network topologies. __________ 802.1AXdz - Amendment - YANG for Link Aggregation No comments. __________ 802.15.4ad - Amendment - Data rate and range extensions to IEEE 802.15.4 Smart Utility Network (SUN) Physical layer (PHY) PAR, 5.2.1 — It looks like the posted PAR is not output from myProject. The P802.15.4ad PAR's "Scope of the complete standard” text does not match the published base standard 1.1 Scope, and none of the published amendments/corrigendum nor the two other active amendment PARs modify the Scope. The PAR’s “Change to scope of the complete standard” only differs from the PARs “Scope of the complete standard” by insertion of spaces in a couple places. Remedy: Assuming the document is not myProject output, please submit draft output from myProject! (Introducing modifications to the unmodifiable current Scope wastes time of reviewers! And, pasting text later into myProject increases the probability of inadvertently introducing changes not approved by IEEE 802!) As to content of the posted document, the “Scope of the complete standard” text should be the published Scope statement in IEEE Std 802.15.4-2020. It appears that the Scope of the published standard does not need to be changed, and that the proposed changes indicating a limitation on the MAC specifications here instead only belong in and are currently covered by 5.2.b, Scope of the project. If though there is really a desire to change the Scope of the standard, the changes to the Scope should fix the typos “boattery” and “modificatins”, as well as delete the inserted space before the new full stop of first sentence and the inserted space before “modificatins”. __________ 802.19.3a - Recommended Practice Amendment: Enhanced sub-1GHz Coexistence PAR, 4.3 — No date provided for RevCom submittal. PAR, 5.5 — I have no idea what the sentence "Also experience within the industry can be used to update recompensates.” is trying to say. (Looking at a dictionary and IEEE Std 802.19.3 didn’t helped. And this is for unlicensed spectrum who is getting compensated, let alone recompensated?) My inability to deal with this one might just be enough to make this my last attempt to review 802 PARs. 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 |