🚀 go-pugleaf

Okay, I'm officially confused. In article 29247@nntpd.lkg.dec.com, 
thomas@lkg.dec.com (Matt 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.

I've been unable to get the official Phase V specs from anyone at DEC, but Martin
and Leben's text, _DECnet Phase V: An OSI Implementation_ seems like the next best
thing. On page 158:

    The following values are two possible SEL field values used by Transport layer
    entities to identify the Transport entity within the ndoe to which a packet
    is destined:
    
      o  32. A packet whose PCI contains this SEL field value is a data or
         control packet sent to an ISO Transport layer entity in a DNA Phase
         V node.
         
      o  33. A packet whose PCI contains this SEL field value is a data or
         control packet sent to an NSP Transport layer entity.

Question for Matt (or anyone else at DEC): Did Martin and Leben get the SEl
values backwards? Can you check and get us a definitive answer on this?

Thanks


---

Stephen Thomas   AT&T Tridom   (404-514-3522)
email: sat@eng.tridom.com, attmail!tridom!sat