802.1 Tools
  • Home
  • Maintenance
    • All items
    • Open items
    • Closed items
    • Items for review
    • Status
  • Meetings
  • Help
  • Log in
  1. Maintenance Items
  2. 0387
  3. Request
Requested revision
Standard:IEEE802.1AS-2020Clause:11.2.17.1
Clause title:General
Rationale for revision
The normative text in Cl. 11.2.17.1 does not address the scenario when a MDPdelayReq state machine in a IEEE802.1AS-2020 PTP Instance transmits Pdelay_Requests to the MDPdelayResp state machine in a IEEE802.1AS-2011 PTP instance. As a result, the MDPdelayReq state machine in a IEEE802.1AS-2020 PTP Instance never transitions to asCapable = TRUE.
Proposed text
Add to the paragraph in P199L30-35, "The MDPdelayReq state machine at this PTP Instance shall transmit transport-specific peer-to-peer delay Pdelay Request messages (majorSdoId = 0x1, minorSdoId = 0x0, and domainNumber value of 0). It may stop transmissionof CMLDS Pdelay Request messages (majorSdoOd = 0x2, minorSdoId = 0x0, and domainNumber value of 0)."
Impact on existing networks
In a TSN Network with IEEE802.1AS-2011 and IEEE802.1AS-2020 implementtions, gPTP protocol fails to execute.
Originator
Name:Ganesh VenkatesanEmail:ganesh.venkatesan@intel.com
Affiliation:Intel Corporation
Submitted:2025-05-10