Hi Lars, > * TC: Transparent Clocking --> Transparent Clock > * PTP PW: > Should the text read: A PW within a PTP LSP that is > dedicated to carry PTP messages ? > That at least is my understanding of the PTP PW. > Put another way, can you have an Ethernet PW that is > sometimes carrying PTP, sometimes "data"? > More general, mustn't all labels in the stack (apart from > reserved labels) be PTP labels? > * CW: duplicate
Will do. > > Section 5 > * Figure 1+2: should top label read "PTP label", ref. section 4? The current text looks ok to me. Its called PTP Tunnel Label to explicitly indicate that it's the outermost label that LSRs would use to switch the packets on. > > * For my understanding: the range of PTP reserved labels, is > that defined by the operator? I am not sure I understand the reserved labels that you are referring to. > Section 15 > * last paragraph says: > "The use of Penultimate Hop Pop (PHP) is acceptable as long as either > the PHP label is the bottom of stack label (applicable > only to UDP/IP > encapsulation) or the label below the PHP label is a PTP label." > This implies that the PHP-label is also a PTP label, right? > > > A more general comment: would you agree that there is a > general class of tunnel technologies > (PBB, MPLS, IPoverIP) that share the problem you have > described here, and to which you found a solution for MPLS? I think Yes. Cheers, Manav _______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
