Bill, I meant that the working set is extracted/derived from the BGP routing database.
To remove the confusion, I suggest to consider i) pull from local database (e.g. BGP RIB) - one could refer to local pull, ii) pull from remote databases (e.g. DNS) - one could refer to remote pull, and as I stated in my previous post iii) "hybrid pull-push" to cover the case of proactive cases. Would that work for you ? -dimitri. > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of William Herrin > Sent: Sunday, December 21, 2008 9:21 AM > To: PAPADIMITRIOU Dimitri > Cc: [email protected] > Subject: Re: [GROW] Operational experience with cache based mapping ID > > On Thu, Dec 18, 2008 at 6:56 PM, PAPADIMITRIOU Dimitri > <[email protected]> wrote: > > Section 3.4: Acquisition Techniques > > - Push: e.g. BGP > > - Pull: e.g. DNS > > - Hybrid Push-Pull > > Hi Dimitri, > > BGP is not a cache acquisition technique. BGP is a database > distribution mechanism. The very essence of a cache is that it > contains only a small working set carved from the full database. > > Caches can pull from local databases and remote databases. They can > pull from central and distributed databases. But without fail, they > are populated when requests for data pull it in from the larger > database. > > To the extent information is pushed to a cache, it generally falls > into two categories: extra information included in response to a pull > and speculative information that an external system has some reason to > believe the cache will need. > > The "additional" section of a DNS response is an example of extra > information. Gratuitous ARP is an example of a speculative push. > > Regards, > Bill Herrin > > > > -- > William D. Herrin ................ [email protected] [email protected] > 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/> > Falls Church, VA 22042-3004 > _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
