The IP over ATM Mailing List Archive by date

[jhalpern@Newbridge.COM (Joel Halpern)]

Actually, I look at the demux problem differently.

If one has an RFC1577 ATMARP server, and it is co-resident with another
function (such as routing, or host services, or...) then it may do either
of the following:
1) Send an InARP on every incoming connection.  It will get the information,
    and "may" need to filter some out depending on the LIS and service
    boundaries, and other things.
2) It may choose to use a different ATM address for its function as
    ATMARP server.  If so, it would only send InARPs for connections that
    were to its relevant address.  As a side effect, someone who wants
    both InARP and other functions from this device will need two
    separate circuits to the device.  Whether that is good or bad is
    probably in the eyes of the implementor and the customer.

Take your pick,
they both work,
Yours,
Joel M. Halpern			jhalpern@newbridge.com
Newbridge Networks Inc.

PS Yes, we could add additional signalling encodings for the function,
    but I think that this is a bad spot for such.