Hi Shahram et al, A few comments on the latest draft.
1) Section 4. I like the diagrams. Missing is the option for the BC to be inside an LSR. I think we've discussed before on the reflector that if an LSR can act as a TC (e.g. terminating peer-delay messages) then it also has the ability to act as a BC. I can contribute such a diagram, if desired. 2) Section 7. "dont" -> "don't" 3) Section 7. There might be some mix-up between "Event" messages and "timestamped" messages. The new "Event" list includes Announce, which is probably not correct. Announce messages are allowed to have 0 timestamp value or to be timestamped with +/-1 second. 4) Section 7. "If Two Step PTP clocks are present, then the FOLLOW_UP, DELAY_RESP, and PDELAY_RESP_FOLLOW_UP ....", probably DELAY_RESP should not be in this list as it relates to two-way messaging, not two-step messaging. 5) Section 18.2 "Behaviour of Timing-capable/aware LSR". I think BC should also be supported here. 6) Section 17. "Applicability Statement". Where a TC is supported/supportable a BC is also supported/supportable. I don't understand the exclusive bundling of LSR with a TC. Regards, Peter -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: October 22, 2012 4:28 AM To: [email protected] Cc: [email protected] Subject: [TICTOC] I-D Action: draft-ietf-tictoc-1588overmpls-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Timing over IP Connection and Transfer of Clock Working Group of the IETF. Title : Transporting Timing messages over MPLS Networks Author(s) : Shahram Davari Amit Oren Manav Bhatia Peter Roberts Laurent Montini Filename : draft-ietf-tictoc-1588overmpls-03.txt Pages : 36 Date : 2012-10-22 Abstract: This document defines the method for transporting Timing messages such as PTP and NTP over an MPLS network. The method allows for the easy identification of these PDUs at the port level to allow for port level processing of these PDUs in both LERs and LSRs. The basic idea is to transport Timing messages inside dedicated MPLS LSPs. These LSPs only carry timing messages and possibly Control and Management packets, but they do not carry customer traffic. Two methods for transporting Timing messages over MPLS are defined. The first method is to transport Timing messages directly over the dedicated MPLS LSP via UDP/IP encapsulation, which is suitable for MPLS networks. The second method is to transport Timing messages inside a PW via Ethernet encapsulation, which is suitable for both MPLS and MPLS-TP networks. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-tictoc-1588overmpls There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-tictoc-1588overmpls-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-tictoc-1588overmpls-03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc _______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
