The IP over ATM Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1995-Oct> msg00019



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

denser ar$pro space.

  • From: james@newbridge.com (James Watt)
  • Date: Wed, 11 Oct 1995 11:31:17 -0400 (EDT)
  • CC: ip-atm@matmos.hpl.hp.com, gja@thumper.bellcore.com

Grenville Armitage writes:
+--------
|The description of ar$pro would now read:
|
|      0x0000 to 0x00FF  Protocols defined by the equivalent NPLIDs.
|      0x0100 to 0x03FF  Reserved for future use by the IETF.
|      0x0400 to 0x05FF  Designated for use by the ATM Forum.
|      0x0600 to 0xFFFF  Protocols defined by the equivalent Ethertypes.
|
|(based on the observations that valid Ethertypes are never smaller
|than 0x600, and NPLIDs never larger than 0xFF.)
+---------
One interesting case is where the NLPID = 80.  This means (see RFC 1490
for example) that a 5 byte LLC/SNAP value follows.  Where would I put
this ?

In the data plane, the LLC/SNAP could clearly be part of the "Extended
Layer 3 packet" shown in Section 5.5.

But it isn't clear to me where the LLC/SNAP would go in the control plane,
i.e. in a MARS packet.

Did I miss 5 bytes somewhere ?

Regards,
-james

____________________________________________________________________________
James W. Watt,     james@newbridge.com                   Ph: +1 613 591-3600
Newbridge Networks 600 March Rd Kanata ON Canada K2K 2E6 FAX:+1 613 591-3680