CAN CSA-ISO IEC 8650-1B-2001 Information technology - Open Systems Interconnection - Connection-oriented protocol for the Association Control Service Element Protocol specification.pdf

1、Amendment 2:2001 toNational Standard of CanadaCAN/CSA-ISO/IEC 8650-1-01Amendment 2:1998 to International Standard ISO/IEC 8650-1:1996 has been adopted without modification asAmendment 2:2001 to CAN/CSA-ISO/IEC 8650-1-01. This Amendment was reviewed by the CSA TechnicalCommittee on Information Techno

2、logy (TCIT) under the jurisdiction of the Strategic Steering Committee onInformation Technology and deemed acceptable for use in Canada.December 2001Reference numberISO/IEC 8650-1:1996/Amd.2:1998(E)B CReference numberISO/IEC 8650-1:1996/Amd.2:1998(E)INTERNATIONALSTANDARDISO/IEC8650-1Second edition19

3、96-10-15AMENDMENT 21998-09-15Information technology Open SystemsInterconnection Connection-orientedprotocol for the Association ControlService Element: Protocol specificationAMENDMENT 2: Fast-associate mechanismTechnologies de linformation Interconnexion de systmes ouverts(OSI) Protocole en mode con

4、nexion applicable llment de service decontrle dassociation: Spcification du protocoleAMENDEMENT 2: Mcanisme dassociation rapideISO/IEC 8650-1:1996/Amd.2:1998(E) ISO/IEC 1998All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by an

5、y means, electronic ormechanical, including photocopying and microfilm, without permission in writing from the publisher.ISO/IEC Copyright Office Case postale 56 CH-1211 Genve 20 SwitzerlandiiContents Page1) Introduction . 12) Subclause 2.1. 13) Subclause 6.3. 14) New subclause 6.4 bis 15) Subclause

6、 7.1.3 26) Subclause 7.1.3.1. 27) Subclause 7.1.3.2. 28) Subclause 7.1.3.3. 29) Subclause 7.1.3.4. 210) Subclause 8.1.2 311) Subclause 8.1.3 312) Clause 12 . 3 ISO/IECISO/IEC 8650-1:1996/Amd.2:1998(E)iiiForewordISO (the International Organization for Standardization) and IEC (the International Elect

7、rotechnical Commission) form thespecialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in thedevelopment of International Standards through technical committees established by the respective organization to deal withparticular fields of technical

8、 activity. ISO and IEC technical committees collaborate in fields of mutual interest. Otherinternational organizations, governmental and non-governmental, in liaison with ISO and IEC, also take part in the work.In the field of information technology, ISO and IEC have established a joint technical co

9、mmittee, ISO/IEC JTC 1. DraftInternational Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as anInternational Standard requires approval by at least 75 % of the national bodies casting a vote.Amendment 2 to ISO/IEC 8650-1:1996 was prepared

10、 by Joint Technical Committee ISO/IEC JTC 1, Information technology,Subcommittee SC 33, Distributed application services, in collaboration with ITU-T. The identical text is published as ITU-TRec. X.227/Amd.2.ISO/IEC 8650-1:1996/Amd.2:1998(E)ITU-T Rec. X.227 (1995)/Amd.2 (1997 E) 1INTERNATIONAL STAND

11、ARDISO/IEC 8650-1 : 1996/Amd.2 : 1998 (E)ITU-T Rec. X.227 (1995)/Amd.2 (1997 E)ITU-T RECOMMENDATIONINFORMATION TECHNOLOGY OPEN SYSTEMS INTERCONNECTION CONNECTION-ORIENTED PROTOCOL FOR THE ASSOCIATION CONTROL SERVICEELEMENT: PROTOCOL SPECIFICATIONAMENDMENT 2Fast-associate mechanism1) IntroductionAdd

12、the following paragraphs:The fast-associate mechanism allows a session connection, including its embedded presentation connection and applicationassociation, to be established using a compressed form of the information that would otherwise be sent on the S-CONNECTexchange. The compressed form, calle

13、d the upper-layer context identifier, is a reference to an upper-layer context specification,which is a definition of the fields of the application ACSE, presentation and session protocols that would be sent on the full-form connect messages. The upper-layer context identifier may be parameterized t

14、o include values for variable fields allowedby the full form protocols for the upper-layers.Within the ACSE protocol, the addition is the definition of the construction of the User-summary parameter of theP-CONNECT primitives from the semantics of the AARQ fields and the User-summary parameter of th

15、e correspondingA-ASSOCIATE primitive.2) Subclause 2.1Insert the following references by numerical order: ITU-T Rec. X.216 (1994)/Amd.1 (1997) | ISO/IEC 8822:1994/Amd.1:1998, Information technology OpenSystems Interconnection Presentation service definition Amendment 1: Efficiency enhancements. ITU-T

16、 Rec. X.217 (1995)/Amd.2 (1997) | ISO/IEC 8649:1996/Amd.2:1998, Information technology OpenSystems Interconnection Service definition for the association control service element Amendment 2: Fast-associate mechanism.3) Subclause 6.3In Table 2, add User Summary to the list of parameters for A-ASSOCIA

17、TE request after User Information.4) New subclause 6.4 bisAdd a new subclause after 6.4:6.4 bis User summary mechanismIf the fast-associate mechanism is used during association establishment, the initiating ACPM as well as forming an AARQAPDU to be passed to the Presentation service-provider in the

18、User-Data parameter of a P-CONNECT request, also passes thesemantic content of the AARQ in the User Summary parameter of the P-CONNECT request. The UserISO/IEC 8650-1:1996/Amd.2:1998(E)2 ITU-T Rec. X.227 (1995)/Amd.2 (1997 E)Summary parameter references an Upper-Layer Context specification and is a

19、purely abstract parameter. If the A-ASSOCIATErequest User Information parameter was present, the semantic content of this will have been supplied to the ACPM in the UserSummary parameter of the A-ASSOCIATE request, and is conceptually included in the User Summary parameter of theP-CONNECT request.If

20、 the Presentation provider (via the Session service and protocol) makes use of the fast-associate mechanism, the respondingACPM will receive only the User Summary parameter on the P-CONNECT indication, and not the User-Data. The respondingimplementation will reconstruct the semantic content of the A

21、ARQ that would have been present in the P-CONNECT User-Data, and issue an A-ASSOCIATE indication with a User Summary parameter in place of its User-Data.Similarly, the responding ACPM will form a User Summary parameter on the P-CONNECT response from the AARE APDU,including the semantic content of th

22、e User Summary parameter of the A-ASSOCIATE response (if present) by reference to thesame Upper-Layer Context specification. The initiating ACPM reconstructs the AARE.NOTE The passing of the User Summary parameters and reconstruction of the ACSE APDUs from the Presentation User Summaryparameters is

23、abstract. There is no requirement for a real implementation to perform these actions.5) Subclause 7.1.3Add in b): User-Data or a User Summary parameter on a P-CONNECT .Add at the end of d):or have a User Summary parameter)6) Subclause 7.1.3.1Add after the first paragraph:If the fast-associate mechan

24、ism is supported, the requesting ACPM identifies the semantic content of the AARQ, including theUser-Data, in the User Summary parameter of the P-CONNECT request.7) Subclause 7.1.3.2Add at the end of the first paragraph:or reconstructs an AARQ APDU from the User Summary parameter of the P-CONNECT in

25、dication primitive.8) Subclause 7.1.3.3Add after the first paragraph:If the fast-associate mechanism is supported, the accepting ACPM identifies the semantic content of the AARE, including theUser-Data, in the User Summary parameter of the P-CONNECT response, by reference to the Upper-Layer Contexts

26、pecification identified by the User Summary parameter of the received P-CONNECT indication.9) Subclause 7.1.3.4Replace the second sentence of the second paragraph with the following:Either the User-Data parameter contains an AARE APDU or the User Summary parameter is a value from which the requestin

27、gACPM can reconstruct the AARE APDU.ISO/IEC 8650-1:1996/Amd.2:1998(E)ITU-T Rec. X.227 (1995)/Amd.2 (1997 E) 310) Subclause 8.1.2Add the following new subclause after 8.1.2.2:8.1.2.3 User SummaryThe User Summary parameter, if used, summarizes the semantic content of the AARQ by reference to an Upper-

28、Layer Contextspecification.11) Subclause 8.1.3Add the following new subclause after 8.1.3.2:8.1.3.3 User SummaryThe User Summary parameter, if used, summarizes the semantic content of the AARQ by reference to the same Upper-LayerContext specification as was used in the User Summary parameter of the

29、P-CONNECT request and indication.12) Clause 12Change three to four in first paragraph and add Upper-Layer Context specifications to the list.Consequently, change the period at the end of the last item of the list, to a semi-colon.Add a new subclause 12.4, at the end of the 2nd paragraph of 12.3:12.4

30、 Upper-layer context specificationsAn upper-layer context specification is a definition of all the field values that are required to format the full-form ACSE,presentation and session establishment PDUs for a given application context and a given peer presentation address.NOTE In practice, it is exp

31、ected that an upper-layer context specification will be parameterized to allow for values which may beexpected to be different for each establishment exchange between two peers (e.g. ACSE user information), or for the same applicationbetween different peers (e.g. addressing information).An upper-lay

32、er context specification may be specified as part of an ITU-T Recommendation | International Standard.An upper-layer context specification may also be specified outside of ITU-T Recommendations | International Standards. Inthis situation, ISO/IEC 9834-1 specifies the procedures to register such an u

33、pper-layer context specification.ISO/IEC 8650-1:1996/Amd.2:1998(E) ISO/IECICS 35.100.70Descriptors: data processing, information interchange, network interconnection, open systems interconnection, application layer,comunication procedure, control procedures, protocols.Proposition de Proposal modific

34、ation for changeNhsitez pas nous faire part de vossuggestions 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 rec

35、ommand dinclurele numro de la norme/publicationle 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 informa

36、tionrequested below and attach your proposalfor change 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: