Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!SURFNET.NL!REIJS
From: REIJS@SURFNET.NL
Newsgroups: comp.protocols.iso
Subject: Re: looking for OSI protocol address format
Message-ID: <8910061201.AA09585@ucbvax.Berkeley.EDU>
Date: 4 Oct 89 15:16:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 43


>
>     |------|----------------|-------|---------------------|
>     | 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.
>

Some additional information.

According X.213 Annex A, the nSAP can have a maximum length of 40
(decimal digits encoding of DSP) or 20 (binary octets encoding of
DSP).

In the RARE/COSINE community (Cooperation for Open Systems
Interconnection networking in Europe) the decimal encoding is
recommended, together with the use of NSAP ISO-DCC.

In the same community RARE WG4 is now making a recommendation about
how the allocation of NSAP ISO-DCC can be done by the National Standard
Organizations. Further more a recommendation will be made, how
the DSP will be allocated by the subnetworks.

I hope you canb do something with the above information.


All the best,

                           _   _   _   _
                          |S| |U| |R| |F|
___________________________|___|___|___|_________________________
                             |   |   |
                            (n) (e) (t)
Victor Reijs                                   tel: +31 30 310290
Network development                            fax: +31 30 340903
SURFnet b.v.                             E-mail: Reijs@surfnet.nl
P.O.box 19035
3501 DA Utrecht
The Netherlands