Hi Richard
Is there any plan or ongoing activities to support telecom profile according to
G.8275.1 / .2?
In particular the red functionalities are missing if I'm not mistaken.
Profile comparison
8275.1
8275.2
Power profile
Transport
L2
- Uses the Ethernet addresses identified in IEEE1588-2008 Annex F
- Support of unicast IP has been proposed but not agreed (yet?)
Unicast IPv4
Not supported by PTP4L
L3E2E: Multicast IPv4 or v6
L2P2P: Multicast L2
Unicast negotiation mechanism
no
Required (as a consequence of unicast addressing)
[cid:image001.jpg@01D3F8D5.C4C78950]
Not supported by PTP4L
no
Master selection
Configuration for master selection
Uses "alternate BMCA": supports multiple active grandmasters for redundancy
Clients must know time servers
Not supported by PTP4L
Same as 8275.1
Default BMCA
Time signal clean up
no
Uses boundary or transparent clocks where necessary to "clean up" time signal
as it passes through the network
PTP4L: a BC inherently does some clean-up. Configurable parameters / control
algorithms in PTP4L
no
With kind regards
Christian Leeb
Senior Project Manager
ABB Switzerland Ltd
PGGA-P5
Bruggerstrasse 72
5400, Baden, SWITZERLAND
Phone: +41 58 585 19 59
Mobile: +41 79 341 57 57
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
