The IP over ATM Mailing List Archive by date

[gja@thumper.bellcore.com]

Rick,

I've deliberately separated my replies to your post because you
raise an issue supplementary to the original scope of my concerns.

	[..]
>>> >>Since the LLC/SNAP demultiplexes on fields in the
>>> >>data stream, it doesn't make sense to indicate in the SETUP what value
>>> >>will exclusively be used.
>>> 
>>> I haven't said we _should_. I've noted that we _can't_,

	[..]
>>I'm not proposing that we _should_ do this either (I think that the
>>approach in the RFC is reasonable the way it stands).  However, I'd
>>like to clear up a misconception.  Namely, SVCs _can_ be created in
>>this manner.

I wasn't clear about my "can't" above. Given the
assumptions of LLC/SNAP encapsulated traffic on the VCs, we
"can't" indicate the LLC client in the SETUP. I fully agree with
you that a SETUP can be constructed to explicitly identify
an LLC client entity, but this falls outside the 'default'
scope of rfc1577 (LLC/SNAP VCs). I'm just raising issues within
rfc1577's present scope. Haven't the energy to pursue the wider
picture just yet (its the end of the week, after all! :-)

cheers,
gja