NHRP specification comments

["Eric W. Gray" <[e-mail]>]

Jim,

	Some more comments (specifically relating to operations):

All references are to draft 8 (beta).

Section 6.2.1 ("Caching Requirements") - in the paragraph relating to
caching at "Transit NHSs" - currently this says that cache information
MUST be discarded when it has exceeded its holding time.  It also says 
that this information may be used to form a reply to a non-authoritative 
request. 

I believe that the negative effects of caching at intermediate NHSs can 
be substantially reduced if hold time returned in a non-authoritative
response MUST be the result of decreasing the original hold time by the
elapsed time since initially caching the information.  This information
is either immediately available or easily derivable (depending on your
implementation) and limits the length of time that stale information can
persist in the system to approximately that intended by the original
responder.

I would be interested in whether or not this is a commonly-held opinion.

Section 6.2.2 ("Dynamics of Cached Information") contains a note (at the
end of the subsection entitled "NBMA-Connected Destinations" that might
be interpreted as meaning that it is okay to cache information contained
in a Next Hop Resolution Request (as opposed to Reply) because it is 
considered stable.  Is this what you mean to imply here?

--
Eric Gray