This amendment specifies protocols, procedures, and managed objects for hot standby without use of the Best Master Clock Algorithm (BMCA), for time-aware systems, including:
- A function that transforms the synchronized times of two generalized Precision Time Protocol (gPTP) domains into one synchronized time for use by applications;
- A function that directs the synchronized time of one gPTP domain into a different gPTP domain; and
- Mechanisms that determine whether a gPTP domain has sufficient quality to be used for hot standby.
This amendment also addresses errors and omissions in the description of existing functionality.
|Current Draft||(not available yet)|
|PAR & CSD||Full title: Draft Standard for Local and Metropolitan Area Networks: Timing and Synchronization for Time-Sensitive Applications — Amendment: Hot Standby
PAR (Approved: 03 Jun 2020; Expires: 31 Dec 2024)
|Web page||Craig Gunther|
|not available yet|
The above list includes only the latest version of (proposed) dispositions. See the project folder for a complete list). The dates listed are the website file dates; they may differ from the creation dates in the documents.
Important NOTICE on contributions.
|09 Mar 2020||4 domains
|18 Feb 2020||Multiple domains
|16 Jan 2020||802.1AS Hot Standby Amendment: Scope Discussion
The above list includes only the latest version of updated documents and omits those superseded by subsequent discussion or inclusion in the current draft (see filenames beginning “dm-” in the 2020 or 2021 public directories for a complete list). The dates listed are the website file dates; they may differ from the creation dates in the documents.
Please contact Craig Gunther if you have comments to this page.