[comp.protocols.tcp-ip] DDN X.25 Diagnostic Codes

lars@salt.acc.com (Lars J Poulsen) (12/22/89)

The DDN X.25 Host Interface Specofication stored at NIC.DDN.MIL
(NETINFO:X25.DOC) is several years old. Is there a newer version
available, and if so, where ?

A subscriber is getting a CLR 33-155 (Incompatible destination)
when connecting to a large subset of other hosts; these hosts can
generally connect to the subscriber in question without problems.

Diagnostic code 155 (9B) is undocumented in the above reference.
What does it mean, and where is it listed ?

--
/ Lars Poulsen <lars@salt.acc.com>   (800) 222-7308  or (805) 963-9431 ext 358
  ACC Customer Service              Affiliation stated for identification only
                My employer probably would not agree if he knew what I said !!

barns@GATEWAY.MITRE.ORG (12/23/89)

I was going to go ping the appropriate DCA person but I guess he's on
Christmas vacation, so I'll give you an unofficial version.  A revision
of the DDN X.25 document is in work, and has been for a while now.
However, it isn't on the street yet.  It hit headwinds here and there
during review; long lists of comments and questions were generated and
most have been resolved, but as of the last I knew, one batch was still
in work.  (I helped create that batch - had a task to review the
draft.)  In the past, some reviewers had sufficiently adverse opinions
about the document that they thought it inadvisable to publish.  I
think that phase may be about over, although I have suggested that it
be published initially as a draft for review and comment (of course
they are hardly obliged to do what I suggest).

According to drafts I've seen, diag 155 means that you tried to open a
"Basic X.25" connection to a host whose PSN port has been configured to
accept only "Standard X.25" connections, i.e., the destination wants to
see a Standard Service facility in the call request and the source
didn't send one.  For historical reasons, a number of hosts are
configured for Basic&Standard even though they only want one of the
two, while other hosts are configured for only one or the other.  This
could explain the obscure subsetting phenomenon.

Bill Barns / MITRE-Washington / barns@gateway.mitre.org