Hi Stewart, That is a bigger issue which is outside the scope of this draft. We shouldn't add capabilities to this draft for an NTP function that doesn't exist yet.
Besides even assuming NTP is retrofitted with CF capability you still can use our draft to update its CF since existing HW can easily parse an IP/UDP packet. But adding new fields to CW is something that requires extensive HW change. Thanks, Shahram -----Original Message----- From: Stewart Bryant [mailto:[email protected]] Sent: Wednesday, February 02, 2011 10:20 AM To: Shahram Davari Cc: Yaakov Stein; Bhatia, Manav (Manav); [email protected] Subject: Re: [TICTOC] Transporting PTP messages (1588) over MPLS Networks Shahram I think that it would be useful to retrofit TC to NTP to give it greater accuracy. There are far more NTP clients out there than there 1588 clients, a situation that is likely to continue for the foreseeable future. Stewart On 02/02/2011 18:02, Shahram Davari wrote: > Hi Yaakov, > > But I thought NTP doesn't require TC capability (Correction Field Update) at > every hop. If so then why do we need such capability for NTP? If what you > have in mind is for faster synchronization without waiting for local clock > convergence then that is not the way NTP is implemented today. > > Thx > Shahram _______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
