| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Please find the following EC Comments on 802.3cb PAR and CSD, and responses.
IEEE 802.3 Study Group approved the following responses, and any changes below are reflected in respective documents in
http://www.ieee802.org/3/CU4HDDSG/index.html. Please let me know if you have any questions or concerns that are not resolved. Thank you for your efforts. Yong Kim. 1. From James Gilb PAR General question: With wireless standards, we often specify a target operating range. Is there a reason why a target distance is not specified for this standard?
It seems that the stakeholders would have some expectation of the backplane distance or copper twinax length over which this standard can reliably deliver the advertised data rate. This distance should be stated in the scope. .3SG Response: The scope text is modified additional text to clarify the distance/reach, as indicated below
•
5.2.b. Scope of the project:
The scope of this project is to specify additions to and appropriate modifications of IEEE Std 802.3 to add 2.5 Gb/s and 5 Gb/s Physical Layer (PHY) specifications and management parameters for operation over channels
such as backplanes and twinaxial copper cables
consistent with current storage interconnect applications within a single rack. 2. From James Gilb CSD Compatibility: This 5C states that "shall be compatible with 2.5 Gb/s and 5 Gb/s MAC operation being defined in IEEE P802.3bz". If so, then the PAR (5.3) should
reflect that this standard depends on the completion of IEEE P802.3bz. .3SG Response: The compatibility does not depend on the completion of P802.3bz, but leverages the addition of 2.5 Gb/s and 5 Gb/s MAC operation common to both projects.
The text is modified to remove possible and unintended reading.
•
As an amendment to IEEE Std 802.3, the proposed PHY types shall be compatible with
3. From Paul Nikolich PAR Purpose: The 802.3cb draft PAR 5.4 Purpose: Why isn't a purpose clause included? .3SG Response: IEEE 802.3 does not have a purpose clause and as an amendment to 802.3, this PAR will not have one ================ End of Comment Response ============= -----Original Message----- David My comments on the PARs are as follows: 802.3ca -General question: With wireless standards, we often specify a target operating range. Is there a reason why a target distance is not specified for NG EPON? It seems that the stakeholders would have some expectation of the length of fiber over which this standard can reliably deliver the advertised data rate. This distance should be stated in the scope 802.3b -General question: With wireless standards, we often specify a target operating range. Is there a reason why a target distance is not specified for this standard? It seems that the stakeholders would have some expectation of the backplane distance or copper twinax length over which this standard can reliably deliver the advertised data rate. This distance should be stated in the scope. CSD Compatibility: This 5C states that "shall be compatible with 2.5 Gb/s and 5 Gb/s MAC operation being defined in IEEE P802.3bz". If so, then the PAR (5.3) should reflect that this standard depends on the completion of IEEE P802.3bz. James Gilb ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv. |