Re: nhrp-05 - Purge packets

[James Luciani <[e-mail]>]

Andrew,
> > > > >When a station receives an NHRP Purge request, it MUST discard any
> > > > >previously cached information that matches the Source Address and
> > > > >Request ID (when the Request ID is zero filled the match is made
> > > > >based only on the Destination Address).


> Doesn't the receiver also have to match on some other things e.g.

I am strongly against keeping this much state around on a per cache entry
basis.  I disagee. (28 bytes for source info X number of cache entries).
> - that the Purge comes from the same guy that supplied the cached 
>   information: match on Source IP Address or Source NBMA Address

Bogus Purges are not very bad things unlike bogus registrations.
I am not concerned about this but I hear your point.
> - what about authentication? Is that used on Purges?

Don't we know the NBMA Subnet ID as a result of knowing which interface
the packet came in on?  A wrong NBMA Subnet ID is in fact an error condition.
> - what about NBMA Subnetwork ID? Nowhere is it mentioned that this
>   is or is not allowed in a Purge: presumably it does need to be
>   there in the Purge if an implementation is using it in Request/Reply 
>   packets. If it's there, it needs to be checked.


Regards,
-- Jim Luciani
__________________________________________________________________________
James V. Luciani    Ascom Nexion                    voice: [phone]
[e-mail]   289 Great Rd., Acton MA 01720   FAX: [phone]