Re: ipv6nd-02.txt & autoconfig

[Andrew Smith <[e-mail]>]

> From [e-mail] Fri May 10 15:39:45 1996
> Date: Fri, 10 May 1996 18:41:36 -0700
> From: Albert Manfredi <[e-mail]>
> Organization: Rockwell Defense Electronics - Collins
> To: [e-mail]
> Cc: IP-ATM Working Group <[e-mail]>
> Subject: Re: ipv6nd-02.txt & autoconfig

> But insisting on useful ATM addresses is noble from the ATM perspective,
> to facilitate cut-through, native ATM effectiveness, and so forth.

I don't understand your point here: existing ATM protocols (UNI/PNNI) know 
what to do with internal NSAP or E.164 structure. They know how to route
calls to the correct switch (PNNI routing) and then the last switch knows
which UNI interface to route to (ESI) and then the end-station knows how
to demux to the correct application or logical interface (SEL). I don't
understand why any layer other than "ATM" needs to understand these
concepts.

...

> I agree. We need something to support autoconfiguration here. LANE is not
> relevant.

LANE is only relevant in the sense that it already has auto-configuration figured 
out fairly well for its own needs - there might be some lessons to be learned for 
your issue there (ftp://ftp.atmforum.com/pub/approved-specs/af-lane95-0021.000.*)


Andrew


> Bert
> [e-mail]
> 

********************************************************************************
Andrew Smith					TEL:	[phone]
Bay Networks, Inc. 				FAX:	[phone]
Santa Clara, CA					E-m:	[e-mail]
********************************************************************************