Thread View: comp.protocols.iso
2 messages
2 total messages
Started by Ken Rosenfeld
Mon, 09 Nov 1992 16:02
Default NSAP selector - DEC
Author: Ken Rosenfeld
Date: Mon, 09 Nov 1992 16:02
Date: Mon, 09 Nov 1992 16:02
10 lines
730 bytes
730 bytes
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? Ken Rosenfeld kenneth@bnr.ca Bell-Northern Research
Re: Default NSAP selector - DEC
Author: Matt Thomas
Date: Tue, 10 Nov 1992 15:37
Date: Tue, 10 Nov 1992 15:37
18 lines
1437 bytes
1437 bytes
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.
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