On Wed, 26 Feb 2003, Vijayabhaskar A K wrote: > > > Ofcourse, the requesting router can generate these values itself. > > > With DHCPv6 server sending T1 and T2 values, the requesting > > > router dont need to recalculate the values again and again.. > > > Trust the DHCPv6 server, the values provided by it makes the > > > requesting router to refresh its bindings well before the expiry.. > > > > Well, typically the conventional wisdom is *not* to trust any > > external > > parties to any extent greater than necessary :-) > > If you are able to trust the prefixes given by DHCPv6, then there will be > no harm in trusting the time values provided by it :-)
It's not about that kind of trust -- rather "I trust that the times provided to me by the operator are the best possible choices, and they have in fact provided them" -- I'd imagine you trust your own DHCPv6 implementation and configuration more than your ISP's. -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -------------------------------------------------------------------- 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] --------------------------------------------------------------------
