Yup, will do that. Cheers, Manav
> -----Original Message----- > From: Shahram Davari [mailto:[email protected]] > Sent: Wednesday, April 27, 2011 5.08 AM > To: Bhatia, Manav (Manav); [email protected] > Subject: RE: Updating draft-ietf-tictoc-1588overmpls > > Manav, > > In MPLS-TP the P2MP should work fine since it is all > configured by management. May be just add some text that says > using MPLS control plane the co-routing of the forward and > reverse direction is not possible but using management plane > this is possible such as in case of MPLS-TP. > > Thx > Shahram > > -----Original Message----- > From: Bhatia, Manav (Manav) [mailto:[email protected]] > Sent: Tuesday, April 26, 2011 4:35 PM > To: [email protected] > Cc: Shahram Davari > Subject: Updating draft-ietf-tictoc-1588overmpls > > Folks, > > I am working on updating draft-ietf-tictoc-1588overmpls as > per the WG feedback. > > As part of this I will change the OSPF and IS-IS capabilities > to be per link as against per node that its currently defined as. > > Will also clarify that FCS retention for the payload Ethernet > described in [RFC4720] MUST not be used. > > Should I remove Sec 5.3 "1588 over pure MPLS mode" as I > believe we had discussed that IETF cannot define new > encapsulations in Prague? > > I will also add some verbiage that P2MP LSPs may not work as > they only provide unidirectional traffic flow and cannot > guarantee a symmetrical path back to the head nodes. > > Anything else? > > Cheers, Manav > > -- > Manav Bhatia, > Service Router Product Group (SRPG) > Alcatel-Lucent, India > > _______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
