WR changes for PTPv3: update

be9dbd4c · Maciej Lipinski · 326d2b41 · be9dbd4c · be9dbd4c · be9dbd4c
Commit be9dbd4c authored Jan 27, 2013 by Maciej Lipinski
4 changed files
--- a/documents/WR_changes_for_PTPv3/changesToPtpv2.tex
+++ b/documents/WR_changes_for_PTPv3/changesToPtpv2.tex
@@ -2,4 +2,9 @@
 \label{chap:changesToPtpv2}


-\subsection{Transport Annex}
\ No newline at end of file
+\subsection{Annex F}
+
+\subsection{Calibration Pattern}
+
+It shall be defined as RD+K28.7 code group, Appendix 36A.2 of IEEE802.3.
+
--- a/documents/WR_changes_for_PTPv3/highAccuracyOption.tex
+++ b/documents/WR_changes_for_PTPv3/highAccuracyOption.tex
--- a/documents/WR_changes_for_PTPv3/highAccuracyProfile.tex
+++ b/documents/WR_changes_for_PTPv3/highAccuracyProfile.tex
--- a/documents/WR_changes_for_PTPv3/openQuestions.tex
+++ b/documents/WR_changes_for_PTPv3/openQuestions.tex
@@ -10,4 +10,48 @@ other port in the SLAVE state is considered a Secondary Slave - in normal operat
 it does not provide time (and frequency) to the BC but synchronizes (and syntonizes) to the 
 path-partner and acts as a hot-spare in case the Primary Slave breaks.
 A port becomes a Secondary Slave if it is recommended by the State Decision Algorithm 
-(also SDA modified per clause~\ref{chap:modifiedSDA}) to enter PASSIVE state.
\ No newline at end of file
+(also SDA modified per clause~\ref{chap:modifiedSDA}) to enter PASSIVE state.
+
+
+\subsection{High Accuracy Signaling Message address }
+\label{chap:q:haSignalingMessageAddress}
+
+\begin{itemize*}
+  \item It enables HA options to work only ony direct Communication Paths, i.e. the messages
+        will not go through bridges/standard-PTP-clocks so we will never 
+        L1\_LOCK, CALIBRATE or establish HA\_LINK on indirect connections.
+  \item Works for TC, but the L1 Syntonization is on link-by-link bases (like peer-to-peer 
+        mechanism)
+  \item There is nothing against using High Accuracy Options over IP mapping, the problem is
+        there there is no mean to enforce direct link on the Communication Path -- setting
+        Time To Live to 1 (as in peer-to-peer messages) does not prevent from being relayed
+        by bridges (only prevents passing through routeres)        
+\end{itemize*}
+
+\subsection{Phase Detection Option}
+\label{chap:q:phaseDetection}
+
+I am not sure whether it is good/possible/feasible to describe the phase detection techniques
+to achieve sub-LSB timestamping precision in the standard. On the other hand, what we
+measure really precisely is the course round trip. The timestamp on the SLAVE port 
+is in arbitrary place.... such setting would need to be somehow defined. 
+
+
+\subsection{L1 Syntonization related flags}
+
+I'm not sure why AVB has different transportSpecific field value. I think it is only 
+in order to make it not inter-operable with "standard" PTP. If we put the information
+about L1 Syntonization into transportSpecific field of Ethernet mapping (Annex F),
+we will limite High Accuracy options of \textit{{Layer 1 Syntonization}} only to
+this mapping. But, actually, High Accuracy options (even profile) can be used at least over 
+IP as well. 
+
+\subsection{Calibration Pattern definition}
+\label{chap:q:calibrationPatternDefinition}
+It can be defined for different media/speed/whatever, maybe some table in Annexes.
+Or, it can be indicated in the CALIBRATE\_REQ:
+\begin{itemize*}
+  \item give pattern (e.g.: 111110000) and repetition size/rate/whatever
+  \item indicate kind -- some reference somewhere
+  \item indicate character to be sent (e.g.: RD+K28.7 code group)
+\end{itemize*}
\ No newline at end of file