From b2b5e58a536d30d4eca8c7f2b54e216cac8f4d82 Mon Sep 17 00:00:00 2001 From: Alberto Losada Date: Fri, 12 Jan 2024 17:33:26 +0100 Subject: [PATCH] Addresses wording confusion with PTP ordinary and boundary clocks (#81) Signed-off-by: Alberto Losada --- documentation/modules/ROOT/pages/5g-ran-context.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/modules/ROOT/pages/5g-ran-context.adoc b/documentation/modules/ROOT/pages/5g-ran-context.adoc index 5fa4a6d..2f6954e 100644 --- a/documentation/modules/ROOT/pages/5g-ran-context.adoc +++ b/documentation/modules/ROOT/pages/5g-ran-context.adoc @@ -90,7 +90,7 @@ Precision Time Protocol (PTP) is used to synchronize clocks in a network. When u PTP can work in three modes: * `GrandMaster`: A PTP daemon connected to a hardware with PTP support to synchronize its clock. Other PTP daemons will connect to this PTP GrandMaster in order to sync their clocks. -* `Ordinary Clock`: A PTP daemon connected to a GrandMaster to synchronize its clock. -* `Boundary Clock`: A PTP daemon connected to a GrandMaster to synchronize its clock and being master for other PTP daemons on the network. +* `Ordinary Clock`: A PTP daemon connected to a GrandMaster to synchronize its clock or also to a Boundary Clock behaving as a GrandMaster. +* `Boundary Clock`: A PTP daemon connected to a GrandMaster to synchronize its clock and being a GrandMaster for other PTP daemons that needs to synchronize their time on the network. image::ptp_diagram.png[PTP Diagram]