> > > The problem that I was alluding to in the jabber room is this. I'll > keep > > the problem simple and to one example. > > > > A takes its time from B over an IPv4 address. A then gets a time > query > > from C over IPv6. How does it know if B and C are the same system or > > different system? A has no information about that. > > > > Is this clearer? > > > > Yes, it's clear. How does the current ntpd implementation deal with this > > problem? Â > > > > Currently it doesn't. One of my proposals is for each system to generate > a RefID and use that for all interfaces. I'm not sure if that works for > all cases or causes other issues. >
OK. To clarify: you are proposing an extension to NTP where a server that has multiple IP addresses can choose a special value as its refID, and communicate that to its clients. Then, if the clients choose to take time from that server, they put that special value in as their refID, instead of an IP address. AFAIK this functionality is not part of NTP today, right? It would probably require an extension field? Also its not backwards compatible, since a server that chooses to do this would need to make sure that its clients understand what it is doing. And currently clients don't know how to do this, right? Please clarify if I have misunderstood. -- Sharon Goldberg Computer Science, Boston University http://www.cs.bu.edu/~goldbe
_______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
