Thread View: comp.protocols.iso
1 messages
1 total messages
Started by Doug Montgomery
Tue, 23 Oct 1990 17:20
Re: binary abstract NSAP address length
Author: Doug Montgomery
Date: Tue, 23 Oct 1990 17:20
Date: Tue, 23 Oct 1990 17:20
30 lines
1837 bytes
1837 bytes
>From: REIJS%SURFNET.NL@cunyvm.cuny.edu >Subject: binary abstract NSAP address length >To: iso@nic.ddn.mil > >Is the decimal encoding still valid (it is only not PREFFERRED)? I thought >that at this moment e.g. X.25 does use decimal encoding. Correct? > >So in case there is a possibility that different encoded subnetworks are >connected, then the gateways/interworking units must be able to translate >from binary to decimal encodings. In that case it must be possible to >translate a binary encoded address into a decimal encoded address en vice >versa. How is it then possible to change the length of the binary abstract >syntax? If it is 20 octets long, it does not fit in the decimal encoding! > >Can somebody explain this to me? YES, the decimal encoding is still valid. What is important here is how Network protocols convey OSI NSAPs. Protocols standards dictate how OSI Network Addresses are encoded and coveyed in PDUs (so called Network Protocol Address Information). It is my understanding that current use of X.25 to support the CONS conveys OSI NSAPs using the preferred binary encoding. In situations where it is required to interwork with protocols and subnetworks that employ decimal encoding of *full OSI NSAPs* to do addressing, then one may need to be careful about the length of NSAPs with binary abstract syntax DSPs. dougm
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