1、 Amendment 1:2001 toNational Standard of CanadaCAN/CSA-ISO/IEC 8650-1-01Amendment 1:1997 to International Standard ISO/IEC 8650-1:1996 has been adopted without modification asAmendment 1:2001 to CAN/CSA-ISO/IEC 8650-1-01. This Amendment was reviewed by the CSA TechnicalCommittee on Information Techn
2、ology (TCIT) under the jurisdiction of the Strategic Steering Committee onInformation Technology and deemed acceptable for use in Canada.ISBN 1-55324-578-4 December 2001INTERNATIONAL STANDARD ISOAEC Second edition 1996-10-15 AMENDMENT 1 1997-12-15 Information technology - Open Systems Interconnectio
3、n - Connection-oriented protocol for the Association Control Service Element: Protocol specification AMENDMENT 1: Incorporation of extensibility markers Technologies de Iinformation - lnterconnexion de systkmes ouverts (OSI) - Protocole en mode orient6 connexion pour IWment de service de contr6le da
4、ssocia tion: Spkcifica tion du protocole AMENDEMENT I: Incorporation de marqueurs dextensibilitb 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 worldwid
5、e 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 fi
6、elds of mutual interest. Other international organizations, governmental and non-governmental, in liaison with IS0 and IEC, also take part in the work. In the field of information technology, IS0 and technical committee, ISO/IEC JTC 1. Draft Internat joint technical committee are circulated to natio
7、nal as an International Standard requires approval by bodies casting a vote. IEC have esta blished a joint onal Standards adopted by the bodies for voti ng. Pub1 ication at least 75 % of the n ational Amendment 1 to International Standard ISO/IEC $65Q- 1: 1996 was prepared by Joint Technical Committ
8、ee ISO/IEC JTC 1, Informatic technology, Sub- committee SC 21, Open systems interconnection, data management and open distributed processing, in collaboration with ITU-T. The identical text is published as ITU-T Rec. X.227/Amd. 1. 0 ISO/IEC 1997 All rights reserved. Unless otherwise specified, no pa
9、rt 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 IMPORTS Name, RelativeDistinguishedName FROM
10、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) versi
11、onl(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 ISO/IEC 8650-l : 1996/Amd.l : 19
12、97 (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 PI IMPLICIT BIT STRING version1 (0) DEFAULT version1 , application-context-name PI Application-context-
13、name, called-AP-title 121 AP-title OPTIONAL, called-AE-qualifier PI AE-qualifier OPTIONAL, called-AP-invocation-identifier 141 AP-invocation-identifier OPTIONAL, called-AE-invocation-identifier I51 AE-invocation-identifier OPTIONAL, calling-AP-title I61 AP-titleOPTIONAL, calling-AE-qualifier I71 AE-
14、qualifier OPTIONAL, calling-AP-invocation-identifier PI AP-invocation-identifier OPTIONAL, calling-AE-invocation-identifier PI AE-invocation-identifier OPTIONAL, - The followingfield shall not be present zfonly the Kernel is used. sender-acse-requirements PI IMPLICIT ACSE-requirements OPTIONAL, - Th
15、e followingfield shall only be present zfthe Authentication functional unit is selected. mechanism-name WI IMPLICIT Mechanism-name OPTIONAL, - The followingfield shall onZy be present zfthe Authentication functional unit is selected. calling-authentication-value WI EXPLICIT Authentication-value OPTI
16、ONAL, application-context-name-list WI IMPLICIT Application-context-name-list OPTIONAL, - The abovefield shall only be present zfthe Application Context Negotiation functional unit is selected implementation-information 1291 IMPLICIT Implementation-data OPTIONAL, . . . , . . . , user-information I30
17、1 IMPLICIT Association-information OPTIONAL AARE-apdu := APPLICATION I IMPLICIT SEQUENCE protocol-version PI IMPLICIT BIT STRING version1 (0) DEFAULT version1 , application-context-name Ill Application-context-name, result I21 Associate-result, result-source-diagnostic I31 Associate-source-diagnosti
18、c, responding-AP-title I41 AP-title OPTIONAL, responding-AE-qualifier 151 AE-qualifier OPTIONAL, responding-AP-invocation-identifier WI AP-invocation-identifier OPTIONAL, responding-AE-invocation-identifier I71 AE-invocation-identifier OPTIONAL, - The followingfield shall not be present zfonly the K
19、ernel is used. responder-acse-requirements PI IMPLICIT ACSE-requirements OPTIONAL, - The followingfield shall only be present zfthe Authentication functional unit is selected, mechanism-name PI IMPLICIT Mechanism-name OPTIONAL, - This foZZowingfieZd shall only be present zfthe Authentication functio
20、nal unit is selected. responding-authentication-value I 101 EXPLICIT Authentication-value OPTIONAL, application-context-name-list IllI IMPLICIT Application-context-name-list OPTIONAL, - The abovefield shaZZ only be present zfthe Application Context Negotiation functional unit is selected implementat
21、ion-information 1291 IMPLICIT Implementation-data OPTIONAL, . . . , . . . , 2 ITU-T Rec. X.227 (1995)/Amd.l (1996 E) ISO/IEC 8650-l : 1996/Amd.l : 1997 (E) user-information WI IMPLICIT Association-information OPTIONAL RLRQ-apdu := APPLICATION 2 IMPLICIT SEQUENCE reason PI IMPLICIT Release-request-re
22、ason OPTIONAL, . . . , . . . , user-information WI IMPLICIT Association-information OPTIONAL 1 RLRE-apdu := APPLICATION 3 IMPLICIT SEQUENCE reason PI IMPLICIT Release-response-reason OPTIONAL, . . . , . . . , user-information W IMPLICIT Association-information OPTIONAL 1 ABRT-apdu := APPLICATION 4 I
23、MPLICIT SEQUENCE abort-source PI IMPLICIT ABRT-source, abort-diagnostic Ill IMPLICIT ABRT-diagnostic OPTIONAL, Thisfield shall not be present zfonZy the Kernel is used. . . . , . . . , user-information PO1 IMPLICIT Association-information OPTIONAL ABRT-diagnostic := ENUMERATED no-reason-given (l), p
24、rotocol-error (2), authentication-mechanism-name-not-recognized (3), authentication-mechanism-name-required (4), authentication-failure (5), authentication-required (6), ABRT-source := INTEGER acse-service-user (0), acse-service-provider (1) (Ol, . ) ACSE-requirements := BIT STRING authentication (0
25、), application-context-negotiation(l) Application-context-name-list := SEQUENCE OF Application-context-name Application-context-name := OBJECT IDENTIFIER - Application-entity title productions follow (not in alphabetical order) AP-title := CHOICE ap-title-form1 ap-title-form2 . . . 1 AP-title-forml,
26、 AP-title-form2, AE-qualifier := CHOICE ae-qualifier-form1 AE-qualifier-forml, ae-qualifier-form2 AE-qualifier-form2, . . . - When both AP-title and AE-quaZzer data values arepresent in an AARQ or AARE APDU, both must - have the same form to allow the construction of an AE-title as discussed in CCIT
27、T Rec. X 665 1 - ISO/IEC 9834-6. AP-title-form1 := Name - The value assigned to AP-title-form1 is The Directory Name of an application-process title. AE-qualifier-form1 := RelativeDistinguishedName - The value assigned to AE-qualifier-form1 is the relative distinguished name of a particular - applic
28、ation-entity of the application-process identified by AP-title-form I. AP-title-form2 := OBJECT IDENTIFIER AE-qualifier-form2 := INTEGER AE-title := CHOICE ae-title-form1 ae-title-form2 . . . AE-title-form 1, AE-title-form2, ITU-T Rec. X.227 (1995)/Amd.l (1996 E) 3 ISO/IEC 8650-l : 1996/Amd.l : 1997
29、 (E) - As deJined in CCITT Rec. X 650 1 IS0 7498-3, an application-entity title is composed of an application- - process title and an application-entity quaZiJier. The ACSE protocol provides for the transfer of an - application-entity title value by the transfer of its component values. However, the
30、 following data type - is providedfor International Standards that reference a single syntactic structure for AE titles. AE-title-form1 := Name - For access to The Directory (ITU-T Rec. X500-Series 1 ISO/IEC 9594), an AE title has AE-title-formI. - This value can be constructedfrom AP-title-formI an
31、d AE-quaZ$er-form1 values contained in an AARQ or AARE APDU. A discussion offorming an AE-title-form1 from AP-title-form1 and AE-qualzjier- 1: formI may be found in CCITT Rec. X 66.5 1 ISO/IEC 9834-6. AE-title-form2 := OBJECT IDENTIFIER A discussion offorming an AE-title-form2 from AP-title-form2 an
32、d AE-quaZ$er-form2 may be 11 found in CCITT Rec. X 66.5 1 ISOLEC 9834-6. AE-invocation-identifier := INTEGER AP-invocation-identifier := INTEGER - End of Application-entity title productions Associate-result := INTEGER ( accepted (0), rejected-permanent (l), rejected-transient (2) (02, . ) Associate
33、-source-diagnostic := CHOICE acse-service-user acse-service-provider 1 INTEGER null HO), no-reason-given (l), application-context-name-not-supported (2), calling-AP-title-not-recognized (3), calling-AP-invocation-identifier-not-recognized (4), calling-AE-qualifier-not-recognized (5), calling-AE-invo
34、cation-identifier-not-recognized (6), called-AP-title-not-recognized (7), called-AP-invocation-identifier-not-recognized (S), called-AE-qualifier-not-recognized (9), called-AE-invocation-identifier-not-recognized (lo), authentication-mechanism-name-not-recognized (1 l), authentication-mechanism-name
35、-required (12), authentication-failure (13), authentication-required (14) (014 , . ). 2 INTEGER 1 null (Oh no-reason-given (l), no-common-acse-version (2) (02 , . ) Association-information := SEQUENCE SIZE (1, . . . . 0 2MAX) OF EXTERNAL Authentication-value := CHOICE charstring 0 IMPLICIT GraphicSt
36、ring, bitstring 1 IMPLICIT BIT STRING, external 21 IMPLICIT EXTERNAL, other 3 IMPLICIT SEQUENCE ( other-mechanism-name MECHANISM-NAME&id (ObjectSet), other-mechanism-value MECHANISM-NAME&Type (ObjectSet (&other-mechanism-name) - The abstract syntax of (calling/responding) authentication-value is det
37、ermined by the authentication - mechanism used during association establishment. The authentication mechanism is either explicitly - denoted by the didfield (of type OBJECTIDENTIFIER) f or a mechanism belonging to the class - MECHANISM-NAME, or it is known implicitly by - prior agreement between the
38、 communicatingpartners. If the “other” component is chosen, then - the “mechanism-name ” component must be present in accordance with - ITU-T Rec. X 680 1 ISOLEC 8824. If the value “mechanism-name ” occurs in the AARQ-apdu or the - AARE-apdu, then that value must be the same as the value for “other-
39、mechanism-name ” 4 ITU-T Rec. X.227 (1995)/Amd.l (1996 E) ISO/IEC 8650-l : 1996/Amd.l : 1997 (E) Implementation-data := GraphicString Mechanism-name := OBJECT IDENTIFIER MECHANISM-NAME :=TYPE-IDENTIFIER ObjectSet MECHANISM-NAME := . Release-request-reason := INTEGER normal (0) , urgent (1) , user-de
40、fined (30) (0 1 1 130, . ) Release-response-reason := INTEGER normal (0) , not-finished (1) user-defined (30) (0 1 1 I 30, . ) END ITU-T Rec. X.227 (1995)/Amd.l (1996 E) 5 This page intentionally left blank This page intentionally left blank ISOAEC 8650-l :1996/Amd.l :1997(E) ISOAEC ICS 35.100.70 De
41、scriptors: data processing, information Interchange, network Interconnection, open systems interconnection, connection oriented transmission, data transmission, communication procedure, protocok. application layer, ges Proposition de Proposal modification for changeNhsitez pas nous faire part de vos
42、suggestions et de vos commentaires. Aumoment de soumettre des propositions demodification aux normes CSA et autrespublications CSA prire de fournir lesrenseignements demands ci-dessous et deformuler les propositions sur une feuillevolante. Il est recommand dinclurele numro de la norme/publicationle
43、numro de larticle, du tableau ou de lafigure visla formulation proposela raison de cette modification.CSA welcomes your suggestions andcomments. To submit your proposals forchanges to CSA Standards and other CSApublications, please supply the informationrequested below and attach your proposalfor ch
44、ange on a separate page(s). Be sure toinclude theStandard/publication numberrelevant Clause, Table, and/or Figure number(s)wording of the proposed changerationale for the change.Nom/Name: Affiliation: Adresse/Address: Ville/City: tat/Province/State: Pays/Country: Code postal/Postal/Zip code: Tlphone/Telephone: Tlcopieur/Fax: Date:
