Dear IEEE 802 LMSC members,
Please find below the IEEE 802.3 responses to the comment submitted on the IEEE P802.3dt PAR modification request and the IEEE P802.3dx PAR and CSD. The final draft IEEE P802.3dt PAR modification request and the IEEE P802.3dx PAR and CSD can be accessed
as follows.
Thanks, and best regards,
David
IEEE 802.11 comment IEEE P802.3dt PAR modification request
IEEE 802.11 PAR item 5.2.b Scope of the project comment:
5.2b: Expand the acronym “SFD”
Response part #1:
PAR item 5.2.b Scope of the Project is being modified to the following:
Compare PAR modification text: … in the preamble field and start-of-frame delimiter (SFD)
fields of packets …
Clean PAR modification text: … in the preamble field and start-of-frame delimiter (SFD) fields of packets …
IEEE 802.1 and IEEE 802.15 comments on IEEE P802.3dx PAR and CSD
IEEE 802.1 PAR item 5.2.b Scope of the project comment part #1:
The scope of the project seems to be open ended. It sounds like additions and modifications to enhance the control of PLCA packet transmission. Nonetheless, 5.2.b does not give any hint on the nature of
enhancements that are planned to be added. You might consider having a limited scope for progressing the work quickly.
Response part #1:
PAR item 5.2.b Scope of the project is being modified to the following:
Compare: The scope of the project is to make additions and modifications to the IEEE Std 802.3 Physical Layer Collision Avoidance (PLCA) Reconciliation sSublayers
to enhance the control of PLCA packet transmission, including management parameters and physical layer service access points.
Clean: The scope of the project is to make additions and modifications to the IEEE Std 802.3 Physical Layer Collision Avoidance (PLCA) Reconciliation Sublayer to enhance the control of PLCA packet transmission, including management parameters
and physical layer service access points
IEEE 802.1 PAR item 5.2.b Scope of the project comment part #2:
It might be good to clarify in 5.2.b what kind of enhancements will be added to the base standard by the proposed project. Perhaps at least give an example enhancement.
Response part #2:
This is stated in the Broad Market Potential item in the CSD which is being modified to the following:
Compare: Enhancements to the PLCA and associated Reconciliation sSublayers
to reduce maximum latency, differentiated by station and/or by frame priority, e.g. Priority Code Point (PCP), and improve determinism to allow broader application of 10BASE-T1S/M technology
to existing and emerging market segments such as automotive, aerospace, controls, automation, and robotics.
Clean: Enhancements to the PLCA Reconciliation Sublayer to reduce maximum latency, differentiated by station and/or by frame priority, e.g. Priority Code Point (PCP), and improve determinism to allow broader application of 10BASE-T1S/M
technology to existing and emerging market segments such as automotive, aerospace, controls, automation, and robotics.
IEEE 802.1 PAR item 5.2.b Scope of the project comment part #3:
Where does the information for differentiating latency come from? What is the information for differentiating latency (e.g. priority)?
Note that answers to these questions may go into the CSD rather than the scope.
Are there 802.1 specifications (e.g. 802.1AC, 802.1Q, 802.1DC) that you’d like to leverage as you define your solution? If so, we’d like to help.
Response part #3:
Please see the modified Broad Market Potential item in the CSD above in response part #2.
IEEE 802.1 PAR items 5.2.b Scope of the project and 5.5 Need for project comment:
The distinction of the term “control” in 5.2.b and in 5.5 may be not that clear. Consider expanding it in 5.5, e.g., replace “control application” with “control loop” or “control loop, e.g., in industrial automation and in-vehicle networks”.
Response:
No change to PAR item 5.2.b Scope of the project as ‘control’ in this case is not talking about a control loop or application but instead means limit, restrict, etc.
PAR item 5.5 Need for project is being modified to the following:
Compare: The current maximum latency properties of PLCA are insufficient to serve some closed-loop control applications (e.g., in industrial automation and in-vehicle networks).
Reduced maximum latency and enhanced determinism for some closed-loop control applications are needed on some multidrop shared networks.
Clean: The current maximum latency properties of PLCA are insufficient to serve some closed-loop control applications (e.g., in industrial automation and in-vehicle networks). Reduced maximum latency and enhanced determinism for some
closed-loop control applications are needed on some multidrop shared networks.
IEEE 802.1 CSD Broad Market Potential item comment:
Slide 4 paragraph 1 • Suggest changing: "10BASE-T1S/M (single pair multidrop) network is widely adopted Ethernet PHY" to "10BASE-T1S/M (single pair multidrop) network is a widely adopted Ethernet PHY"
Response:
The Broad Market Potential item in the CSD which is being modified to the following:
Compare: 10BASE-T1S/ or 10BASE-T1M (single pair multidrop)
PHYs with Physical Layer Collision Avoidance (PLCA) are network is widely adopted Ethernet PHY in automotive and industrial networks.
Clean: 10BASE-T1S or 10BASE-T1M single-pair multidrop PHYs with Physical Layer Collision Avoidance (PLCA) are widely adopted in automotive and industrial networks.
IEEE 802.15 PAR item 8.1 Additional Explanatory Notes comment:
Please add additional explanation (8.1) in PAR about the need for the project – e.g. a summary of the CSD: Broad Market Potential.
Response:
The following change to PAR item 5.5 Need for project is being made in response to IEEE 802.1 PAR items 5.2.b Scope of the project and 5.5 Need for project comment above:
Compare: The current maximum latency properties of PLCA are insufficient to serve some closed-loop control applications (e.g., in industrial automation and in-vehicle networks).
Reduced maximum latency and enhanced determinism for some closed-loop control applications are needed on some multidrop shared networks.