[RM Ch03] Update chapter03.md (#2404)

* Update chapter03.md Adding reference for SyncE and NTP, and more clarifications. * Update doc/ref_model/chapters/chapter03.md Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com> * Update doc/ref_model/chapters/chapter03.md Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com> * Update doc/ref_model/chapters/chapter03.md Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com> * Update doc/ref_model/chapters/chapter03.md Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com> * Update chapter03.md Co-authored-by: Pankaj Goyal <52107136+pgoyal01@users.noreply.github.com>
anuket-project · May 23, 2021 · 10dcb45 · 10dcb45
1 parent 4949c3f
commit 10dcb45
Showing 1 changed file with 9 additions and 2 deletions.
diff --git a/doc/ref_model/chapters/chapter03.md b/doc/ref_model/chapters/chapter03.md
@@ -528,9 +528,16 @@ The SFC management components together with the control components are responsib
 
 Precise Synchronization require specialized card that can be on server or network device motherboard or be part of NIC or both.
 
-OpenStack and Kubernetes clusters use NTP as the default time synchronization for the cluster. That level of synchronization is not sufficient for many network functions. Just like real-time operating system requirement instead of base OS so is precision timing for clock synchronization. Precision Time Protocol version 2 [PTP] (IEEE 1588-2019) is commonly used for Time-Sensitive Networking. This allow synchronization in microsecond range rather than millisecond range that NTP provides.
+OpenStack and Kubernetes clusters use Network Time Protocol (NTP) ([Protocol and Algorithms Specification](https://tools.ietf.org/html/rfc5905), [Autokey Specification](https://tools.ietf.org/html/rfc5906), [Managed Objects](https://tools.ietf.org/html/rfc5907), [Server Option for DHCPv6](https://tools.ietf.org/html/rfc5908)) as the default time synchronization for the cluster. That level of synchronization is not sufficient for some network functions. Just like real-time operating systems instead of base OS, so is precision timing for clock synchronization. Precision Time Protocol version 2 [PTP](https://standards.ieee.org/standard/1588-2019.html) is commonly used for Time-Sensitive Networking. This allow synchronization in microsecond range rather than millisecond range that NTP provides.
 
- Some Network functions, like vDU, of vRAN, also require SyncE. Control, User and Synchronization (CUS) Plane specification defines different topology options that provides Lower Layer Split Control plane 1-4 (LLS-C1 - LLS-C4) with different synchronization requirements (ITU-T G.8275.2).
+Some Network functions, like vDU, of vRAN, also require [SyncE](http://www.itu.int/rec/T-REC-G.8262). Control, User and Synchronization (CUS) Plane specification defines different topology options that provides Lower Layer Split Control plane 1-4 (LLS-C1 - LLS-C4) with different synchronization requirements ([ITU-T G.8275.2](https://www.itu.int/rec/T-REC-G.8275.2/en)).
+
+SyncE was standardized by the ITU-T, in cooperation with IEEE, as three recommendations:
+
+* ITU-T Rec. G.8261 that defines aspects about the architecture and the wander performance of SyncE networks
+* ITU-T Rec. G.8262 that specifies Synchronous Ethernet clocks for SyncE
+* ITU-T Rec. G.8264 that describes the specification of Ethernet Synchronization Messaging Channel (ESMC)
+SyncE architecture minimally requires replacement of the internal clock of the Ethernet card by a phase locked loop in order to feed the Ethernet PHY. 
 
 <a name="3.6"></a>
 ## 3.6 Storage