The IP over ATM Mailing List Archive by date

Cell Relay Retreat>List Archive>month:1995-Sep> msg00027



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

Hardware Address Space

  • From: "Andrew G. Malis" <malis@nexen.com>
  • Date: Fri, 08 Sep 1995 16:47:35 -0400
  • CC: malis@nexen.com, ip-atm@matmos.hpl.hp.com, laubach@terra.com21.com, tjsmith@vnet.ibm.com, malis@nexen.com

Mike,

> My apologies.  No one asked me for a document, so I didn't supply one.
> We're using type 21, and I cannot see how to replace its functionality
> with type 16 or 19.
> 
> Here is what the document would say about type 21:
> 
> Hardware type 21 is a virtual circuit identifier.  This allows you to
> use ARP and associated protocols to map between VCIs and other address
> types.
> 
> When the hardware protocol type is 21:
> 	The hardware length field should be set to 4
> 	The protocol type field should be set to:
> 	   1 if you are mapping to or from a 48-UID (Ethernet address)
> 	   x if you are mapping to or from addresses with Ethernet type x

Thanks!  Out of curiosity, is the VPI/VCI coded right-justified in the
four octets, or the same as the first octets of a header (with GFC, PT,
and CLP set to zero)?

So future generations don't ask this question again, can you ask the
IANA to update value 21 to read something like "Asynchronous
Transmission Mode (ATM) VPI/VCI", or something similar?  Can you also
provide a public reference, if one exists?

This still leaves the mystery of value 16, and who JXB2 is!

Thanks much,
Andy