Excerpts from William Herrin at 12:52:01 -0600 on Mon 1 Dec 2008: > On Sun, Nov 30, 2008 at 11:52 PM, Scott Brim <[EMAIL PROTECTED]> wrote: > > The issue will rarely come up. In order for it to arise, a site > > border router must come up cold with no knowledge of prefixes where it > > wants to find its NTP servers. Once it maps these prefixes, which > > will very probably be few and well-used, it will have mappings for > > them until it comes up cold again. So as yet another alternatives, > > avoid completely cold restarts, or give it what it needs via > > configuration or synchronization. There are probably other > > possibilities. > > Scott, > > It need only expire the cached map entry for inactivity. Which it will > tend to do over tens of minutes with no use
Correct me if I'm wrong but it seems to me that whatever higher stratum NTP servers are used will be (1) well used, and (2) in popular prefixes. What servers do you use? My little MBP uses apple.com and nist.gov. I doubt that they would be removed from the cache. If a site communicates with zillions of others, so there is a lot of churn in the cache, it probably wants to reconsider its caching strategy in the first place, but second, steps can be taken to make sure a map for a particular prefix doesn't get squeezed out. (That doesn't mean it doesn't get refreshed as TTL expiration approaches.) Scott _______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
