Eliot, > -----Original Message----- > From: Eliot Lear [mailto:[email protected]] > Sent: Sunday, December 21, 2008 10:36 AM > To: PAPADIMITRIOU Dimitri > Cc: Ron Bonica; [email protected]; Routing Research Group Mailing List > Subject: Re: [rrg] [GROW] Operational experience with cache > based mapping ID > > Dimitri, > > I've written quite a bunch on this already, and you are free > to borrow > from any of the NERD versions you would like to snip from.
Thanks for the offer ! > HOWEVER... > > The title of the draft explicitly states "operational experience with > cache based mapping". Can you please help me with that? I > would think > that as far as such mappings are concerned there are really only two > groups of people who have any: LISPers and HIPsters. > > If we are just going to talk about previous uses of caching, > that's okay too, This is indeed the purpose i.e. "Lessons Learned with Caching" and such lessons can be learned from both successful and unsuccessful experiences. > but I would suggest that the impact of a cache miss is HIGHLY > variable based on application, and the actual occurrence of a > cache miss > is highly variable not only based on application, but based on > configuration as well. The question on how far the similarity holds with ongoing applications listed here above is to be interpreted as follows: caching mechanisms share a core set of common principles - so except if any of these new application relies on a new caching mechanism there is no reason to believe we will be left without useful material as outcome of this exercise. Now i think there is another question in your statement - nature of the cached information - as you seem to infer that mapping caches in the networking space are specific to the two applications of LISP ad HIP: the same answer applies here. > As a case in point, I used netnews to distribute the precursor of the > Human Genome Project (GenBank) throughout the net to > scientists' systems > who would then suck the thing into an RDB. Consistent > distribution was > important, and so a cache miss would stall an update. But > once the file > had been loaded, any further misses were irrelevant. There > are a lot of > netnews design examples out there from the server side. > > It's been said that we've done caching before on routers, and this is > true. And so my point is simply this: the question must be > asked, what > are the similarities and differences between the systems in > use and what was done previously? Imho such document can provide for an analysis grid of what is currently ongoing at RRG (or even at other groups) based on experience. Nevertheless, the term "operational experience" MAY induce a certain confusion in that it assumes currently deployed routing system makes de-facto use of caching - this is why i would prefer the title "Lessons Learned with Caching" so as to prevent any pre-assumption on any usage or positive/negative experience. Thanks, -d. > Eliot > _______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
