Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!ginosko!aplcen!haven!decuac!shlump.nac.dec.com!michaud
From: michaud@devax.dec.com (Jeff Michaud)
Newsgroups: comp.protocols.iso
Subject: Re: looking for OSI protocol address format
Message-ID: <5022@shlump.nac.dec.com>
Date: 29 Sep 89 04:06:15 GMT
References: <472@excelan.COM>
Sender: news@shlump.nac.dec.com
Organization: DEC
Lines: 22

>     |------|----------------|-------|---------------------|
>     | L1   |  TSAP	    | L2    |	NSAP		  |
>     |------|----------------|-------|---------------------|
> 
>     L1     one byte, specifies byte length of TSAP and must not exceed 32.
>     L2     one byte, specifies byte length of NSAP and must not exceed 20.
>     TSAP   Transport service access point address.
>     NSAP   Network service access point address.

	If I'm not mistaken, what you are calling a TSAP is really
	only a TSEL (Transport Selector).  A TSAP includes the
	next lower layers addressing information (ie. TSAP would
	contain both the TSEL and the NSAP).

	Question, is 32 the max. TSEL length these days?  I still
	hear rumblings that max. length may be increased (or is
	32 the new length?)?

/--------------------------------------------------------------\
|Jeff Michaud    michaud@decwrl.dec.com  michaud@decvax.dec.com|
|DECnet-ULTRIX   #include               |
\--------------------------------------------------------------/