🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.protocols.iso
3 messages
3 total messages Started by Wendy Teller Fri, 30 Oct 1992 14:31
Use of SELs in OSI stack
#21
Author: Wendy Teller
Date: Fri, 30 Oct 1992 14:31
43 lines
2229 bytes
I am attempting to understand the proper use of the selector fields 
in the OSI stack: NSEL, TSEL, SEL and PSEL. In the discussion of the
ISO network layer addresses in "Interconnections", page 157, 
Radia Perlman says
"The purpose of the SEL octet is to differentiate among multiple
network layer users". On page 161 of the same book, it also states
"..an NET should take the same form as an NSAP and that the selector
value of 0 would be reserved to mean the network layer itself." 

RFC 1139 uses NSAP selectors in a similar way: "The choice of 
echo-request and echo-reply NSAP selectors is a local matter.
However, to insure interoperability, and as an interim measure
until use of the directory service becomes widespread, this memo
will recommend the following default values ...."

So, it seems, selectors allow multiple n+1 layers to make use
of layer n's services. Somehow I need to know which selector
values to use. There are several possibilites:

1. Assign values permanently, as seems to be recommended in the
quotations above. This could become yet another registration problem.

2. Agree locally before hand which values to use. This could become
an  interoperations nightmare.

3. Depend on a directory service to provide all information needed.
How far along are we on actually getting such a directory implemented?
If we do depend on the directory service, what values of the
selector will we use for the directory service?

4. And all the other possibilities....

In summary I have several questions:

1. Are there standards or defacto standards on the use of selectors?
Any detailed formation on these would be appreciated.

2. If there are no standards, how should these fields be used?

Wendy Teller
Tellabs Operations, Inc
wendy@tellabs.com
708-512-7956
Re: Use of SELs in OSI stack
#22
Author: Stephen Thomas
Date: Fri, 30 Oct 1992 19:34
16 lines
1123 bytes
>1. Are there standards or defacto standards on the use of selectors?
>Any detailed formation on these would be appreciated.

Here are the NSAP Selectors I know about:

#define CLNPNsapSel          0			  /* network stuff */
#define RFPNsapSel           1			  /* AT&T Tridom Proprietary */
#define EchoReqNsapSel      30			  /* RFC1139 echo request */
#define EchoRplNsapSel      31			  /* RFC1139 echo reply */
#define ISOTransportNsapSel 32			  /* from DECnet Phase V */
#define DECPHIVNsapSel      33			  /* DECnet Phase IV PDU */

---

Stephen Thomas   AT&T Tridom   (404-514-3522)
email: sat@eng.tridom.com, attmail!tridom!sat
Re: Use of SELs in OSI stack
#24
Author: Matt Thomas
Date: Sat, 31 Oct 1992 16:20
20 lines
1496 bytes
In article <Bwy918.Kps@tridom.com>, sat@eng.tridom.com (Stephen Thomas) writes:
|>#define ISOTransportNsapSel 32			  /* from DECnet Phase V */

This is the NSEL for NSP (the DECnet Phase IV transport).  It is a constant in
the DECnet Phase V architecure.  (ie. NSP is always 32).  So for those of you
who have network protocol analyzers, if you see an NSAP with last octet being
a hex 20, use NSP decoder to interpet the rest of the packet.


|>#define DECPHIVNsapSel      33			  /* DECnet Phase IV PDU */

DECnet Phase V defaults OSI Transport to 33 though you are allowed to change it
to any value except 0, 1, and 32.

--
Matt Thomas                     Internet:   thomas@lkg.dec.com
DECnet-ULTRIX Development       UUCP:       ...!decwrl!thomas
Digital Equipment Corporation   Disclaimer: This message reflects my own
Littleton, MA                               warped views, etc.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads