multi-cache descrived better
This commit is contained in:
parent
941f2b1dd3
commit
ac2c675d32
1 changed files with 5 additions and 7 deletions
|
|
@ -248,13 +248,11 @@
|
||||||
</t>
|
</t>
|
||||||
<t>
|
<t>
|
||||||
A VRP is effective if it is in the fetched set from any of the
|
A VRP is effective if it is in the fetched set from any of the
|
||||||
currently preferred caches. Therefore, if the router is
|
currently preferred caches. Therefore, a VRP takes effect on
|
||||||
fetching from multiple equal preference caches, then withdraws
|
the router when the first cache serves that VRP, and the VRP is
|
||||||
of a particular VRP invalidating some prefix may take effect
|
in effect until the last cache withdraws that VRP. Thus, in a
|
||||||
comparitively later than announcements of that VRP. All in-use
|
global sense, the effect of a VRP announcement propagates more
|
||||||
caches must have withdrawn the VRP for the router to not have a
|
quickly than a withdraw,
|
||||||
copy; but if the router has received an announcement from any
|
|
||||||
cache then that VRP is in effect.
|
|
||||||
</t>
|
</t>
|
||||||
<t>
|
<t>
|
||||||
Periodically, the router sends a Serial Query to the cache the
|
Periodically, the router sends a Serial Query to the cache the
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue