Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!lll-winken!ptavv.llnl.gov!oberman
From: oberman@ptavv.llnl.gov
Newsgroups: comp.protocols.iso
Subject: Re: Does US GOSIP NSAP format conform to ISO standards?
Message-ID: <1991Apr25.171824.1@ptavv.llnl.gov>
Date: 26 Apr 91 00:18:24 GMT
References: <1991Apr25.141954.18249@nntphost.ciba-geigy.ch>
Sender: usenet@lll-winken.LLNL.GOV
Lines: 21
Nntp-Posting-Host: ptavv.llnl.gov

In article <1991Apr25.141954.18249@nntphost.ciba-geigy.ch>, /pn=gary.nebbett/ou=chcgbs21/@ciba-geigy.ch (Gary Nebbett) writes:
> ISO 6523-ICD decimal syntax     20 octets
> ISO 6523-ICD binary syntax      16 octets
> 
> The US GOSIP NSAP address structure has an AFI of 47 indicating that it is in a
> binary syntax ISO 6523-ICD format, but has a total length of 20 octets which
> seems to conflict with the above.
 
This was corrected in a recent addendum to the ISO standard making binary
syntax OK for 20 octets. I believe it is Add. 2, but I may be in error.

The fact that this addendum has not been widely distributed has caused at least
some software designers to make their software incompatible with US GOSIP.
*Sigh*. Fortunately, it's usually pretty trivial to fix.

R. Kevin Oberman			Lawrence Livermore National Laboratory
Internet: oberman@icdc.llnl.gov		(415) 422-6955

Disclaimer: Don't take this too seriously. I just like to improve my typing
and probably don't really know anything useful about anything. Especially
anything gnu.