The Routing Over Large Clouds Mailing List Archive by date

[Bruce Cole <bcole@cisco.com>]

> There are a number of error conditions for which you just cannot test 
> without a demux mechanism.

Yes, but the point is the protocol already provides enough information for
an implementation to demux things.

> What about the case when you have 2 or more NHCs which are co-resident with 
> their NHS?  You can't figure out for whom the packet was sent in this case 
> without burdening all NHCs to check to their database.

I don't think I understand the need for multiple distinct clients in an NBMA
station (where the clients share the same IP address and interface).

Having multiple logical IP addresses associated with a single physical 
NBMA interface is of course reasonable, and is neither precluded nor required
by NHRP.

When you have multiple logical IP networks associated with a single 
physical interface, you can treat this as a single instance of NHRP running
over multiple virtual interfaces.  Or you can stick with the concept of
multiple logical instances of NHRP.  But these are implementation details
that don't require changes to the text of the spec.

> but what do you want to do about the statement:
>     : An NHS is configured with its own identity, a set of IP address
>     : prefixes that correspond to the IP addresses of the stations it
>     : serves, a logical NBMA subnetwork identifier (see Section 5.7.2),
>     : and in the case of "server" mode, the identities of other NHSs in
>     : the same logical NBMA subnetwork.  If a served station is attached

I would clarify "own identify".  For the purposes of this section, I believe
it means the set of IP addresses and NBMA addresses assigned to the NHS
station itself.