| Colleagues:
As has been my custom the last few years, I have reviewed the PARs (and supporting CSDs) submitted for March consideration. This includes a maintenance PAR that could have been submitted during the plenary week. Any additional input that any of you may have would be appreciated. It would be especially helpful if anyone with free space optics expertise looked at the proposed P802.15.7a CSD and my comments.
• 802.1ASdm Amendment: Hot Standby, PAR and CSDNo comment.
• 802.1CQ Amendment: Multicast and Local Address Assignment, PAR Extension and CSDNo comment.
• 802.1Q Revision: Bridges and Bridged Networks, PAR
The PAR file linked above is change marked but there is no approved P802.1Q revision PAR on myProject, so my comments treat this as a new revision PAR even though it appears to be a PAR modification based on some section headings. That said, no comments. (I assume any issues with myProject will be fixed prior to the March meeting, and the submission will use the correct form for NesCom review.)
• 802.15.7a - Amendment - Defining High Data Rate Optical Camera Communications (OCC), PAR and CSDPAR I had one comment on 6.1.b. Because this is RAC related and previous ad hocs have suggested I submit such comments directly as the RAC Chair, I have already submitted the following comment to the EC reflector. Obviously, the WG could choose to make a similar comment if felt necessary.
802.15 colleagues: I submit the following personal comment for consideration during the March Plenary session.. (Comment has not been review nor approved by the RAC.) Item 6.1.b — The RAC has the option to review any project and doesn’t need the box checked to give them permission in case they may want to review a draft. The answer and explanation are not consistent with the PAR form instructions (quoted below) in that the explanation does not indicate a new registry or new use of an existing registry expected to be included in the project. Either the explanation needs to be improved (see the P802.1ASdm draft PAR also submitted for March 802 consideration as an example), or the answer should be “No”.
The IEEE Registration Authority Committee (RAC) is a mandatory coordination body.If the proposed standard requires (or is expected to require) the unique identification of objects or numbers for use in industry, the project has registration activity. This does not cover things like code points defined within the standard.A YES answer with brief explanation is appropriate if:1. The proposed standard creates a new registry.2. The proposed standard includes new use of an existing registry (whether IEEE RA or other registry authority).Please visit the IEEE Registration Authority website (http://standards.ieee.org/regauth/index.html) for additional information regarding existing registries.
1.2.1,a — The response has unexpanded acronyms (MIMO, OCC), please expand.
1.2.1,a — The assertion "extending to billions of existing devices to provide secure non RF based communications capability” is not credible. Existing devices probably do not have optical communication interfaces. While the promise is there for future devices, it isn’t there for many existing devices. The ease of retrofitting existing devices is grossly oversimplified by this statement as well as other parts of the CSD. Recommend replace “existing” with “future” and improve grammar: "extending to billions of future devices the option of using secure non RF based communications capability”.
1.2.1,b — The last sentence is more credible for “applications" than it is for “devices” (assuming “applications” refers to a type of usage of the standard rather than a specific installation of existing devices). The sentence should be edited because it is unlikely that the retrofit market will significantly increase the number of vendors and users. It is more likely that existing devices could be engineered at reasonable cost to alternately use optical communications than it is that “billions” of existing devices are likely to be upgradable to optical communication. Recommend the last sentence be edited to read: "This translates to a large community of vendors and users.”
1.2.3 — Unexpanded acronym “OWC”. Please expand.
1.2.5,c — It is not likely that a many devices can be upgraded to use an optical transmitter and receiver with only firmware upgrade. At a minimum, the device needs the hardware for an optical transmitter and receiver. Many of the devices cited in 1.2.1,b would be subject to extensive qualification of the new optical interface (e.g., automotive, biomedical, process control, etc.) This has significant potential impact to the economic feasibility of the retrofit market. Some of the devices cited in 1.2.1,b may not be upgradable, for example low cost drones likely do not have replaceable modules for the communication interface. Device physical design may also not support the differences in radio propagation from an antenna versus optical transmission from the optical transmitter (e.g., the device itself may provide minimal attenuation because of it materials to a radio signal but totally block optical transmission in certain directions, significantly changing the operational profile for the device.
1.2.5,a — Again, "existing hardware" is not credible. It needs to be rewritten to perhaps to “hardware designs” or something that does not imply existing installed hardware.
1.2.5,b — Again, “billions of existing devices” is not credible and is not supported in the CSD. The first sentence has little relevance to “known cost factors”, delete it.
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
|