Thanks Stewart. I understand from the "may" that you used that MPLS-TP nodes may also possibly support IP forwarding plane, correct? (I mean, MPLS-TP does not rule out using IP forwarding in the same node). If so, then I understand that the problem that TICTOC is trying to solve is mainly the case of MPLS-TP nodes not supporting IP forwarding. Is that correct? Another question for my clarification (sorry for my poor knowledge on MPLS-TP...): does MPLS-TP only imply that IP forwarding only may not be supported, or also that IP may not be supported at all in the equipment (e.g. for other purposes than forwarding plane, such as management)? Thanks. BR,
Sébastien ________________________________ De : Stewart Bryant [mailto:[email protected]] Envoyé : vendredi 9 juillet 2010 11:35 À : JOBERT Sebastien RD-CORE-LAN Cc : [email protected]; [email protected] Objet : Re: [TICTOC] FW: 1588 over MPLS draft On 09/07/2010 09:23, [email protected] wrote: Thank you Shahram (and Yaakov) for the reply. Just for my clarification: "one method is to use direct IP routing. However there are cases that this doesn't work. For example MPLS-TP networks don't support IP routing." => Does it mean that MPLS-TP nodes do not understand IP? They may not. Indeed I have always though that it was strange that Q13 are working on an IP based time distribution protocol, whilst the other Questions who are designing the transports over which timing have to flow are insisting that IP may not be present in the equipment, especially in the forwarding plane. Stewart
_______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
