Rob, I think you mentioned in an earlier email about the need for NTP in order to use DNSSEC.
From the discussion on the list it sounds like the timing requirement for DNSSEC is for the host to have a clock that is +/- 5 minutes. This could be implemented with NTP or something else (e.g., accurate clock). I read some of RFC2030 "Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and OSI". I think is what would be needed in most hosts. RFC2030 has three mechanisms for a host to communicate with a SNTP server: Unicast, Multicast, and Anycast. The Multicast and Anycast use well know IANA assigned multicast addresses and don't need any learned configuration. The use of anycast is different than what we usually discuss as it also uses the well known multicast addresses but assumes some cooperation between the servers so only one responds. I would think the unicast approach should work with well known unicast addresses (like the current DNS discovery proposal) at it uses UDP for a transport and consists of a single request with a single response. I will add SNTP server addresses to the list of desirable features in the requirements text. Bob -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
