home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!decwrl!pa.dec.com!engage.pko.dec.com!nntpd.lkg.dec.com!lkg.dec.com!thomas
- From: thomas@lkg.dec.com (Matt Thomas)
- Newsgroups: comp.protocols.iso
- Subject: Re: Default NSAP selector - DEC
- Message-ID: <1992Nov10.153709.16046@nntpd.lkg.dec.com>
- Date: 10 Nov 92 15:37:09 GMT
- Article-I.D.: nntpd.1992Nov10.153709.16046
- References: <1992Nov9.160204.16846@bnrmtl.bnr.ca>
- Sender: thomas@mipsbx.lkg.dec.com (Matt Thomas)
- Reply-To: thomas@lkg.dec.com
- Organization: Digital Equipment Corporation
- Lines: 18
-
-
- In article <1992Nov9.160204.16846@bnrmtl.bnr.ca>, kenneth@bnrmtl.bnr.ca (Ken Rosenfeld) writes:
- |>Matt Thomas points out that the network selector in
- |>
- |>> DECnet Phase V defaults OSI Transport to 33 though you are
- |>> allowed to change it to any value except 0, 1, and 32.
- |>
- |>Question: why can't the value be changed to 1?
-
- Because some time ago we weren't sure if we needed to reserve another selector
- value or not. Note that some time in future in a product far far away we will
- be allowing 0 and 1 for endsystem. As are routers the restriction about 0 will
- still be in force but the one about 1 will be lifted
- --
- 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.
-