The IP over ATM Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1995-Jun> msg00032



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

your mail

  • From: Mark Laubach <laubach@terra.com21.com>
  • Date: Tue, 20 Jun 1995 18:06:26 -0700 (PDT)
  • CC: ip-atm <ip-atm@matmos.hpl.hp.com>


> Reading between the lines of RFC 1577, section 6.3, ATMARP Server 
> Operational Requirements, I'm making the assumption that a client can 
> respond to the Server's InARP_Request with multiple InARP_Replies, each with 
> a different IP address and the same ATM address. I'm assuming that the 
> Server would table each of them into its cache. Is this a safe assumption?

No it is not really a safe assumption.  The server only makes InARP_Requests
for IP subnets it is configured for and the client can only respond as
per the rules in RFC1293.

Mark

RFC1293 says:

7.1.  Operation with Multi-Addressed Hosts

   In the context of this discussion, a Multi-Addressed host will refer
   to a host that has multiple protocol addresses assigned to a single
   interface.  If such a station receives an InARP request, it must
   choose one address with which to respond. To make such a selection,
   the receiving station must first look at the protocol address of the
   requesting station, and then respond with the protocol address
   corresponding to the network of the requester.  For example, if the
   requesting station is probing for an IP address, the responding
   multi-addressed station should respond with an IP address which
   corresponds to the same subnet as the requesting station.  If the
   station does not have an address that is appropriate for the request
   it should not respond.  In the IP example, if the receiving station
   does not have an IP address assigned to the interface that is a part
   of the requested subnet, the receiving station would not respond.

   A multi-addressed host may choose to send an InARP request for each
   of the addresses defined for the given interface.  It should be
   noted, however, that the receiving side may answer some or none of
   the requests depending on its configuration.

----------