🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.protocols.iso
Article #1536

Abstract Syntax Specification in X.500 Directory Recommendation.

#1536
From: Joey De Wiele
Date: Fri, 28 Oct 1988 20:13
26 lines
1399 bytes

Abstract Syntaxes and Protocol Specifications
---------------------------------------------

In case anyone is perusing the X.500 document, looking for something new
to figure out, I am stumped on this one:

The macro defined in the Remote operations notation extension in CCITT
X.219 for defining application contexts includes the notation for
specifying abstract syntaxes for application protocols. My understanding
of abstract syntaxes would lead me to believe that an abstract syntax
would be defined in an ASN.1 module, or modules, and would be very
similar to the abstract service definition.

The X.500 application context is defined to use two abstract syntaxes,
identified by the object identifiers id-as-acse and
id-as-directoryAccessAS (for the DAP protocol). Now, I am unable to find
an explicit statement linking the id-as-directoryAccess object
identifier to a given ASN.1 module or set of definitions.

Anyone have any ideas on this one? I'd like to know how this works.



Joey
Technical Details
Message-ID: <3370@geaclib.UUCP>
Path: arc1-ca.pugleaf.net!utzoo!yunexus!geac!geaclib!joey

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!yunexus!geac!geaclib!joey
From: joey@geaclib.UUCP (Joey De Wiele)
Newsgroups: comp.protocols.iso
Subject: Abstract Syntax Specification in X.500 Directory Recommendation.
Keywords: OSI, X.500, Abstract Syntax
Message-ID: <3370@geaclib.UUCP>
Date: 28 Oct 88 20:13:34 GMT
Article-I.D.: geaclib.3370
Organization: GEAC Computers, Toronto, CANADA
Lines: 26