Re: Question on RFC1577.
Mark Laubach <laubach@terra.com21.com> Wed, 28 September 1994 19:32 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa09389; 28 Sep 94 15:32 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa09385; 28 Sep 94 15:32 EDT
Received: from matmos.hpl.hp.com by CNRI.Reston.VA.US id aa15027; 28 Sep 94 15:32 EDT
Received: by matmos.hpl.hp.com (1.37.109.10G/HPL42.42) id AA116580255; Wed, 28 Sep 1994 09:37:35 -0700
Errors-To: atmpost@matmos.hpl.hp.com
X-Orig-Sender: atmpost@matmos.hpl.hp.com
X-Info: Submissions to ip-atm@matmos.hpl.hp.com
X-Info: [Un]Subscribe requests to majordomo@matmos.hpl.hp.com
X-Info: Archives for ip-atm via ftp.hep.net:~ftp/lists-archive/atm
X-Loop: ATM CLP.bit ON
Precedence: bulk
Received: from terra.com21.com by matmos.hpl.hp.com with ESMTP (1.37.109.10G/HPL42.42) id AA116170247; Wed, 28 Sep 1994 09:37:27 -0700
Received: from localhost (laubach@localhost) by terra.com21.com (8.6.5/8.6.5) id JAA11937; Wed, 28 Sep 1994 09:26:33 -0700
Date: Wed, 28 Sep 1994 09:26:33 -0700
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mark Laubach <laubach@terra.com21.com>
Subject: Re: Question on RFC1577.
To: "Peter If the software don't work, rewire the hardware Schulter" <schulter@zk3.dec.com>
Cc: gja@thumper.bellcore.com, ip-atm@matmos.hpl.hp.com
In-Reply-To: <9409272355.AA07441@abyss.zk3.dec.com>
Message-Id: <Pine.3.89.9409280947.B11744-0100000@terra.com21.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
> used (IMHO). I think this is just a layering issue, and using LLC/SNAP > encapsulation implies that the peer LLC entities send packets to each other > and they then demultiplex them to the LLC users (ARP, IP, etc). I don't think > there's a problem as long as you use null encapsulation on the ATMARP > VC, but as soon as you default to LLC/SNAP encapsulation then you introduce > another peer-to-peer layer under ARP/IP. Introducing LLC means that you > differentiate between IP and ARP at the LLC layer rather than at the ATM > (VC) layer and make them reachable via the same LLC entity. Yes? No? Having a multiprotocol encapsulation does not imply that you are supporting all layered (demux'd) protocols above that encapsulation. > > What am I missing in this picture? (he says, hoping for a deluge of > > points....) > > I think there is general confusion about using LLC VCs simply because the > use of the LLC layer for ATM is not well defined (and I too may be greatly > confused here). I hope we get a deluge of comments too, since this will > help us all resolve any potential interoperability problems sooner than later. > I'm always open to a deluge of contructive comments ;-) Our decision process selected LLC/SNAP and that's what we'll work with. I think the wealth of experience that we're accumulating here will be key to driving the definition of how to use the LLC layer in ATM. Mark
- Question on RFC1577. gja
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. Berry Kercheval
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. Berry Kercheval
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Curtis Villamizar
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Rick Bubenik
- Re: Question on RFC1577. Curtis Villamizar
- Re: Question on RFC1577. Craig Partridge
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Curtis Villamizar
- Re: Question on RFC1577. Craig Partridge
- Re: Question on RFC1577. Rick Bubenik
- Re: Question on RFC1577. gja
- LLC/SNAP vs Null Encaps (was Re: Question on RFC1… gja
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. Peter If the software don't work, rewire the hardware Schulter
- Re: Question on RFC1577. Joel Halpern
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Mark Laubach
- Our first public ATM statement Peter If the software don't work, rewire the hardware Schulter
- re: Question on RFC1577. Peter If the software don't work, rewire the hardware Schulter
- Re: Question on RFC1577. Fong-Ching Liaw
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. Fong-Ching Liaw
- Re: Question on RFC1577. Brad Benson
- Re: Question on RFC1577. rajeev
- Re: Question on RFC1577. Andrew Smith
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. rajeev
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Drew Perkins
- Re: Question on RFC1577. rajeev
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Keith McCloghrie
- Re: Question on RFC1577. Drew Perkins
- Re: Question on RFC1577. Drew Perkins
- Re: Question on RFC1577. Keith McCloghrie
- Re: Question on RFC1577. Brad Benson
- Re: Question on RFC1577. Drew Perkins
- Re: Question on RFC1577. Fong-Ching Liaw
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Peter If the software don't work, rewire the hardware Schulter
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Peter If the software don't work, rewire the hardware Schulter
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. gja
- Re: Question on RFC1577. Peter If the software don't work, rewire the hardware Schulter
- Re: Question on RFC1577. Fong-Ching Liaw
- Re: Question on RFC1577. Mike Spengler
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. schulter
- Re: Question on RFC1577. schulter
- Re: Question on RFC1577. Mark Laubach
- Hmmmm..... (was Re: Question on RFC1577.) gja
- Re: Question on RFC1577. (long, but two replies i… schulter
- Re: Question on RFC1577. schulter
- Re: Question on RFC1577. Mark Laubach
- Re: Question on RFC1577. Craig Partridge
- Re: Question on RFC1577. schulter