Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
W
White Rabbit Standardization
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
White Rabbit Standardization
Commits
be9dbd4c
Commit
be9dbd4c
authored
Jan 27, 2013
by
Maciej Lipinski
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
WR changes for PTPv3: update
parent
326d2b41
Expand all
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
329 additions
and
134 deletions
+329
-134
changesToPtpv2.tex
documents/WR_changes_for_PTPv3/changesToPtpv2.tex
+6
-1
highAccuracyOption.tex
documents/WR_changes_for_PTPv3/highAccuracyOption.tex
+205
-86
highAccuracyProfile.tex
documents/WR_changes_for_PTPv3/highAccuracyProfile.tex
+73
-46
openQuestions.tex
documents/WR_changes_for_PTPv3/openQuestions.tex
+45
-1
No files found.
documents/WR_changes_for_PTPv3/changesToPtpv2.tex
View file @
be9dbd4c
...
...
@@ -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.
documents/WR_changes_for_PTPv3/highAccuracyOption.tex
View file @
be9dbd4c
This diff is collapsed.
Click to expand it.
documents/WR_changes_for_PTPv3/highAccuracyProfile.tex
View file @
be9dbd4c
This diff is collapsed.
Click to expand it.
documents/WR_changes_for_PTPv3/openQuestions.tex
View file @
be9dbd4c
...
...
@@ -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
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment