I'm not sure, but I think we're talking semantics here. I think what you're referring to is that the Ethernet types you reference for Novell are based on standards... but if I remember my Novell history correctly, Novell's encapsulation types aren't the standards as we know them.
For example, Novell guessed at what the standard was going to be for 802.3 and missed. Novell's 802.3 had scalability issues and as such, had to create 802.2. Now 802.2 by itself isn't an encapsulation type in the IEEE world now is it? And that's what I mean when I say that they're proprietary--they're Novell's own design and naming structure. I don't remember enough about SAP or SNAP to comment at this point... All my Novell courseware manuals are at home and I'm not. -- Leigh Anne > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Priscilla Oppenheimer > Sent: Wednesday, October 03, 2001 9:00 PM > To: [EMAIL PROTECTED] > Subject: RE: CCIE Written: Ethernet 802.3 Frames [7:21945] > > > At 09:39 PM 10/3/01, Leigh Anne Chisholm wrote: > >1. See Priscilla's response first. > > > >2. Your query wondering about what protocols other than Novell > that can use > >the 802.3 frame makes me wonder if you have misunderstood encapsulation. > >Novell's encapsulations were developed prior to the IEEE finalizing their > >standards. They're Novell-proprietary. > > I understand your point, but, actually only Novell raw is > proprietary. The > other options for Novell encapsulation are all standard. > > ETHERNET_II, aka arpa, Ethernet V.2 and Ethernet II, is standard. > ETHERNET_802.2, aka sap, and 802.3 with 802.2, is standard. > ETHERNET_SNAP, aka snap, and 802.3 with 802.2 and SNAP, is standard. > > > >To illustrate this point, if you set the IPX encapsulation type to be > >novell-ether and you typed "show ipx interface ethernet 0", you'll see > >"novell-ether" on the Ethernet 0 interface. However, if you type "show > >interface ethernet 0", you'll see that the encapsulation is ARPA which is > >different than the IPX encapsulation on that same interface. > > I would say that's a bug (limitation) with show int. IP uses > ARPA, which is > Cisco's ridiculous term for Ethernet II. Other encapsulations are > used for > other protocols. The show int probably just shouldn't show the > encapsulation if it's not going to be more specific. > > Priscilla > > > > -- Leigh Anne > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > > > Lists Wizard > > > Sent: Wednesday, October 03, 2001 4:29 PM > > > To: [EMAIL PROTECTED] > > > Subject: CCIE Written: Ethernet 802.3 Frames [7:21945] > > > > > > > > > Hi Group, > > > > > > I am checking on the what the Certification Zone CD is saying about > 802.3 > > > ethernet frames. Here is what they say: > > > > > > "Novell 802.3 raw frames do not use 802.2, so they do not > have a protocol > > > identifier. In > > > practice, encapsulated IPX frames do have an hexadecimal FF > in the first > > > byte, so the > > > protocol can be identified." > > > > > > my questions are: > > > > > > What protocols other than novell can use the 802.3 frame? How are they > > > identified within the frame header? > > > > > > Any comments are welcomed > > > > > > Thanks > > > > > > Lists Wizard > ________________________ > > Priscilla Oppenheimer > http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=22059&t=21945 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
