|
|
# White Rabbit Standardization
|
|
|
|
|
|
## Introduction
|
|
|
|
|
|
*White Rabbit** (WR) is a protocol developed to synchronize nodes in a
|
|
|
packet-based network with sub-ns accuracy. The protocol results from the
|
|
|
combination of IEEE1588-2008 (*Precision Time Protocol*, PTP) with two
|
|
|
further extensions: automatic precise measurement of the link delay and
|
|
|
clock syntonization over the physical layer (similar to SyncE).
|
|
|
packet-based network with sub-ns accuracy.
|
|
|
The protocol results from the combination of IEEE1588-2008 (*Precision
|
|
|
Time Protocol*, PTP) with two further extensions:
|
|
|
|
|
|
1. automatic precise measurement of the link delay and
|
|
|
2. clock syntonization over the physical layer (similar to SyncE).
|
|
|
|
|
|
White Rabbit evolved into an extension of the Precision Time Protocol
|
|
|
(PTP) and is therefore referred to as WRPTP. WRPTP is fully compatible
|
|
|
with PTP and is currently defined as a PTP Profile.
|
|
|
with PTP and is currently being defined as a PTP Profile.
|
|
|
|
|
|
The solutions included in WRPTP are now being evaluated by [P1588
|
|
|
The solutions included in WRPTP are now being evaluated by the [P1588
|
|
|
Working Group](https://ieee-sa.centraldesktop.com/1588public/) to be
|
|
|
included into the PTP standard in its next revision.
|
|
|
included into the next revision of the PTP standard.
|
|
|
|
|
|
-----
|
|
|
|
... | ... | @@ -24,7 +28,7 @@ The White Rabbit Protocol is defined in the White Rabbit Specification |
|
|
- hardware requirements for implementing WRPTP
|
|
|
- protocol requirements for WRPTP-compatibility
|
|
|
|
|
|
*White Rabbit Specification** material:
|
|
|
### White Rabbit Specification material
|
|
|
|
|
|
- WR Specifications
|
|
|
- [WR Specification - latest
|
... | ... | @@ -56,16 +60,16 @@ Advantages of standardization: |
|
|
Standardization is a considerably long process that can be approached in
|
|
|
various ways and from various directions. Potential paths (see
|
|
|
[presentation](https://www.ohwr.org/project/white-rabbit/uploads/b5d237adf2198f9da783fd44e87c4eeb/ITU-T_meetingReport.pdf))
|
|
|
for WR's standardization have been identified. These include:
|
|
|
for WR's standardization had been identified. These include:
|
|
|
|
|
|
- [Standardization at International Telecommunication Union-
|
|
|
- [Standardization at the International Telecommunication Union-
|
|
|
Telecommunication Standardization Sector
|
|
|
(ITU-T)](ITU-Tstandardization)
|
|
|
- within Telecom Profile (G.827x) - currently being developed
|
|
|
- as a separate Profile (similar to Telecom)
|
|
|
- [Standardization at Institute of Electrical and Electronics
|
|
|
- [Standardization at the Institute of Electrical and Electronics
|
|
|
Engineers (IEEE)](IEEEstandardization)
|
|
|
- as a PTP Profile
|
|
|
- as an IEEE1588 PTP Profile
|
|
|
- included into version 3 of PTP (PTPv3)
|
|
|
- as a part of
|
|
|
[AVB](http://www.ieee802.org/1/pages/avbridges.html) Gen2,
|
... | ... | @@ -132,67 +136,67 @@ Protocol. |
|
|
<tr class="odd">
|
|
|
<td></td>
|
|
|
<td><b> Task </b></td>
|
|
|
<td><b> Expected end time </b></td>
|
|
|
<td align="center">* End date *</td>
|
|
|
</tr>
|
|
|
<tr class="even">
|
|
|
<td>1.</td>
|
|
|
<td>Establishment of WR Standardization Group</td>
|
|
|
<td>end of April 2012</td>
|
|
|
<td align="center">end of April 2012</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>2.</td>
|
|
|
<td>Potential standardization path evaluation</td>
|
|
|
<td>end of September 2012</td>
|
|
|
<td align="center">end of September 2012</td>
|
|
|
</tr>
|
|
|
<tr class="even">
|
|
|
<td>3.</td>
|
|
|
<td>Decision of standardization path choice</td>
|
|
|
<td>end of 2012</td>
|
|
|
<td align="center">end of 2012</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>4.</td>
|
|
|
<td>Start of standardization efforts</td>
|
|
|
<td>February 2013</td>
|
|
|
<td align="center">February 2013</td>
|
|
|
</tr>
|
|
|
<tr class="even">
|
|
|
<td>5.</td>
|
|
|
<td>First face-to-face IEEE1588 Study Group meeting</td>
|
|
|
<td>April 2013</td>
|
|
|
<td align="center">April 2013</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>6.</td>
|
|
|
<td>Project Authorization Request (PAR) submitted</td>
|
|
|
<td>May 2013</td>
|
|
|
<td align="center">May 2013</td>
|
|
|
</tr>
|
|
|
<tr class="even">
|
|
|
<td>7.</td>
|
|
|
<td>Project Authorization Request (PAR) approved</td>
|
|
|
<td>June 2013</td>
|
|
|
<td align="center">June 2013</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>8.</td>
|
|
|
<td>P1588 Working Group formalized</td>
|
|
|
<td>August 2013</td>
|
|
|
<td align="center">August 2013</td>
|
|
|
</tr>
|
|
|
<tr class="even">
|
|
|
<td>9.</td>
|
|
|
<td>High Accuracy Enhancements sub-committee created</td>
|
|
|
<td>August 2013</td>
|
|
|
<td align="center">August 2013</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>10.</td>
|
|
|
<td>P1588 Plenary Meeting organized at CERN</td>
|
|
|
<td>April 2014</td>
|
|
|
<td align="center">April 2014</td>
|
|
|
</tr>
|
|
|
<tr class="even">
|
|
|
<td>11.</td>
|
|
|
<td>... standardizing ...</td>
|
|
|
<td>...</td>
|
|
|
<td align="center">...</td>
|
|
|
</tr>
|
|
|
<tr class="odd">
|
|
|
<td>12.</td>
|
|
|
<td>New revision of IEEE1588 with WR published</td>
|
|
|
<td>not later then 2018</td>
|
|
|
<td>New revision of IEEE1588 with <em>High Accuracy Option/Profile</em> published</td>
|
|
|
<td align="center">not later than 2018</td>
|
|
|
</tr>
|
|
|
</tbody>
|
|
|
</table>
|
... | ... | |