ISO/IEC 8650-1:1996/Amd 1:1997
(Amendment)Information technology — Open Systems Interconnection — Connection-oriented protocol for the Association Control Service Element: Protocol specification — Amendment 1: Incorporation of extensibility markers
Information technology — Open Systems Interconnection — Connection-oriented protocol for the Association Control Service Element: Protocol specification — Amendment 1: Incorporation of extensibility markers
Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Protocole en mode connexion applicable à l'élément de service de contrôle d'association: Spécification du protocole — Amendement 1: Incorporation de marqueurs d'extensibilité
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISOAEC
STANDARD
Second edition
1996-10-15
AMENDMENT 1
1997-12-15
Information technology - Open Systems
Interconnection - Connection-oriented
protocol for the Association Control
Service Element: Protocol specification
AMENDMENT 1: Incorporation of extensibility
markers
Technologies de I’information - lnterconnexion de systkmes ouverts
(OSI) - Protocole en mode orient6 connexion pour IWment de service de
contr6le d ’associa tion: Spkcifica tion du protocole
AMENDEMENT I: Incorporation de marqueurs d ’extensibilitb
---------------------- Page: 1 ----------------------
ISO/IEC 8650-l : 1996/Amd.l : 1997 (E)
Foreword
IS0 (the International Organization for Standardization) and IEC (the Inter-
national Electrotechnical Commission) form the specialized system for worldwide
standardization. National bodies that are members of IS0 or IEC participate in the
development of International Standards through technical committees established
by the respective organization to deal with particular fields of technical activity.
IS0 and IEC technical committees collaborate in fields of mutual interest. Other
international organizations, governmental and non-governmental, in liaison with
IS0 and IEC, also take part in the work.
blished a joint
In the field of information technology, IS0 and IEC have esta
technical committee, ISO/IEC JTC 1. Draft Internat onal Standards adopted by the
bodies for voti ng. Pub1 ication
joint technical committee are circulated to national
as an International Standard requires approval by at least 75 % of the n ational
bodies casting a vote.
Amendment 1 to International Standard ISO/IEC $65Q- 1: 1996 was prepared by
Joint Technical Committee ISO/IEC JTC 1, Informatic~~ technology, Sub-
committee SC 21, Open systems interconnection, data management and open
in collaboration with ITU-T. The identical text is
distributed processing,
published as ITU-T Rec. X.227/Amd. 1.
0 ISO/IEC 1997
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or
utilized in any form or by any means, electronic or mechanical, including photocopying and micro-
film, without permission in writing from the publisher.
ISO/IEC Copyright Office l Case postale 56 l CH- 1211 @en&e 20 l Switzerland
Printed in Switzerland
---------------------- Page: 2 ----------------------
0 ISO/IEC
ISO/IEC 8650-l : 1996/Amd.l : 1997 (E)
Introduction
This amendment to the connection-oriented ACSE protocol specification includes the ASN.l extensibility marker in the
module describing the protocol.
. . .
111
---------------------- Page: 3 ----------------------
This page intentionally left blank
---------------------- Page: 4 ----------------------
ISO/IEC 8650-l : 1996/Amd.l : 1997 (E)
INTERNATIONAL STANDARD
ITU-T RECOMMENDATION
INFORMATION TECHNOLOGY
- OPEN SYSTEMS INTERCONNECTION -
CONNECTION-ORIENTED PROTOCOL FOR THE ASSOCIATION CONTROL
SERVICE ELEMENT: PROTOCOL SPECIFICATION
AMENDMENT 1
Incorporation of extensibility markers
Subclause 2.1
1)
Add the following reference.
-
ITU-T Recommendation X.501 (1993) 1 ISO/IEC 9594-2: 1995, Information Technology - Open Systems
Interconnection - The Directory: Models.
Subclause 9.1
2)
Replace the ASN. I module with the foZZowing.
ACSE-1 { joint-iso-itu-t association-control(2) modules(O) apdus(0) versionl(1) }
--
ACSE-I refers to ACSE version 1
DEFINITIONS ::=
BEGIN
EXPORTS
acse-as-id, ACSE-apdu,
aCSE-id, Application-context-name,
AP-title, AE-qualifier,
AE-title, AP-invocation-identifier,
AE-invocation-identifier,
Mechanism-name, Authentication-value,
ACSE-requirements;
IMPORTS Name, RelativeDistinguishedName
FROM InformationFramework
{ joint-iso-ccitt ds(5) module(l) informationFramework(1) 2 };
-- The data types Name and ReZativeDistinguishedName are importedfrom ISO/IEC 9594-2.
--
object ident$er assignments
acse-as-id OBJECT IDENTIFIER ::=
{ joint-iso-itu-t association-control(2) abstract-syntax(l) apdus(0) versionl(1) }
--
may be used to reference the abstract syntax of the ACSE APDUs
aCSE-id OBJECT IDENTIFIER ::=
{ joint-iso-itu-t association-control(2) ase-id(3) acse-ase(1) version(l) }
--
may be used to identz$ the Association Control ASE.
ITU-T Rec. X.227 (1995)/Amd.l (1996 E) 1
---------------------- Page: 5 ----------------------
ISO/IEC 8650-l : 1996/Amd.l : 1997 (E)
--
top level CHOICE
ACSE-apdu ::= CHOICE
\
aarq AARQ-apdu,
aare AARE-apdu,
rlrq RLRQ-apdu,
rlre RLRE-apdu,
abrt ABRT-apdu,
. . .
AARQ-apdu : : = [ APPLICATION 0 ] IMPLICIT SEQUENCE
{ protocol-version IMPLICIT BIT STRING { version1 (0) }
PI
DEFAULT { version1 },
Application-context-name,
application-context-name
PI
AP-title OPTIONAL,
called-AP-title
121
AE-qualifier OPTIONAL,
called-AE-qualifier
PI
called-AP-invocation-identifier AP-invocation-identifier OPTIONAL,
141
called-AE-invocation-identifier AE-invocation-identifier OPTIONAL,
I51
calling-AP-title AP-titleOPTIONAL,
I61
AE-qualifier OPTIONAL,
calling-AE-qualifier
I71
AP-invocation-identifier OPTIONAL,
calling-AP-invocation-identifier
PI
AE-invocation-identifier OPTIONAL,
calling-AE-invocation-identifier
PI
--
The followingfield shall not be present zfonly the Kernel is used.
sender-acse-requirements IMPLICIT ACSE-requirements
PI
OPTIONAL,
--
The followingfield shall only be present zfthe Authentication functional unit is selected.
mechanism-name IMPLICIT Mechanism-name
WI
OPTIONAL,
--
The followingfield shall onZy be present zf ’the Authentication functional unit is selected.
EXPLICIT Authentication-value
calling-authentication-value
WI
OPTIONAL,
IMPLICIT Application-context-name-list
application-context-name-list
WI
OPTIONAL,
--
The abovefield shall only be present zfthe Application Context Negotiation functional unit is selected
implementation-information IMPLICIT Implementation-data
1291
OPTIONAL,
. . . , . . . ,
user-information IMPLICIT Association-information
I301
OPTIONAL
AARE-apdu ::= [ APPLICATION I ] IMPLICIT SEQUENCE
{ protocol-version IMPLICIT BIT STRING{ version1 (0) }
PI
DEFAULT { version1 },
Application-context-name,
application-context-name
Ill
result Associate-result,
I21
result-source-diagnostic Associate-source-diagnostic,
I31
responding-AP-title AP-title OPTIONAL,
I41
AE-qualifier OPTIONAL,
responding-AE-qualifier
151
AP-invocation-identifier OPTIONAL,
responding-AP-invocation-identifier
WI
AE-invocation-identifier OPTIONAL,
responding-AE-invocation-identifier
I71
--
The followingfield shall not be present zfonly the Kernel is used.
responder-acse-requirements IMPLICIT ACSE-requirements
PI
OPTIONAL,
--
The followingfield shall only be present zfthe Authentication functional unit is selected,
mechanism-name IMPLICIT Mechanism-name
PI
OPTIONAL,
--
This foZZowingfieZd shall only be present zfthe Authentication functional unit is selected.
responding-authentication-value EXPLICIT Authentication-value
I 101
OPTIONAL,
IMPLICIT Application-context-name-list
application-c
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.