The Routing Over Large Clouds Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1995-Jul> msg00016



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

NHRP protocol modifications and clarifications

  • From: James Luciani <luciani@nexen.com>
  • Date: Tue, 11 Jul 1995 17:59:28 -0400
  • cc: rolc@nexen.com
  • X-Orig-Sender: owner-rolc@nexen.com

> 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.

I think I understand what you don't see now.  I am not saying that:
"the clients share the same IP address and interface".

I am saying that in order to demux the traffic, when two or more Next Hop 
Clients (NHC) are physically co-located in the same box with an NHS then they 
must have DIFFERENT IP addresses NOT a shared IP address.  How else would you 
demux the client messages to their appropriate destination?

There are a number of error conditions for which you just cannot test without a
demux mechanism.  If you get an error message, how do you intuit for whom it 
was sent?...  Lets say it is an error case of incorrect message type.
What about the case when you have 2 or more Next Hop Clients (NHCs) which are 
co-resident with their NHS?  You can't figure out for whom a reply was sent 
in this case without burdening all NHCs to check to their database.