Todd Glassey wrote: > Rob Neal wrote: >> I support it as well. Go forward, please. >> >> On Thu, 16 Jul 2009, Greg Dowd wrote: >> >> >>> I support the advancement of this draft. >>> >>> > I dont - the design of NTP is flawed from an evidence perspective and > the point of this draft is to securely interface NTP to DHCP which > serves the interests of only those members of this entity who support > the continued advancement of NTP in its current vein - i.e. with code > from the ISC and through the licensing problems which exist now because > the IETF's copyrights are now the controlling ones on the NTP standard. >
This draft has nothing to do with NTP itself. This draft is about the DHCPV6 server providing a list of possible NTP servers for the client to use. The client has the option of using the list as is, adding it to it's own list or totally ignoring the list and not using any of them. The DHCPV6 server will have a list provisioned by an administrator. Whether the list is chosen well or badly has nothing to do with the protocol draft. If you find that NTP is flawed then you have access to the source code to fix it and distribute your own version but it has nothing to do with a DHCP protocol proposal. None of this has anything to do with ISC. NTP is copyrighted by the University of Delaware. The IETF owns the protocol even though it was developed at the University of Delaware by David Mills. You are free to accept, reject or just ignore IETF standards as they have no policing function. > Sorry - I DO NOT support the advancement of this draft since it actually > serves only to increase the value of proprietary code and not advance > NTP. It also totally glosses over that NEA the Network Enablement. It might (or not) increase the value of your own proprietary code but the NTP protocol and the reference implementation is not proprietary and you can do whatever you want with the code. I have no idea what NEA is or the Network Enablement nor to I understand what this has to do with this draft proposal. Danny -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ TICTOC mailing list [email protected] https://www.ietf.org/mailman/listinfo/tictoc
