|
ISP
STANDARDIZED
PROFILE 11183-1
First edition
1992-12-15
Information technology - International
Standardized Profiles AOMI n OSI
Management - Management
Communications -
Part 1:
Specification of ACSE, presentation and
Session protocols for the use by ROSE and
CMISE
Technologies de I’in forma tion - Profils normalisbs in terna tionaux AO M 1 n
Gestion de communication -
pour Ia gestion OSI -
Partie 7: Spkification des protocoles ACSE, pr&entation et Session pour
emploi par ROSE et CMISE
Reference number
lSO/IEC ISP 11183~1:1992(E)
---------------------- Page: 1 ----------------------
ISO/IEC ISP 11183-1 : 1992 (E)
Page
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~. vii
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1 Scope
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .~. 1
1.1 General
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Position within the Taxonomy
“.,.~.,. 2
1.3 Scenario
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Normative references
4
3 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.................................................................................. ................ 4
3.1 Base Standard support
4
3.2 Profile support Level .
4
3.2.1 Supported .
4
3.2.2 Optionally supported .
.......... 5
3.2.3 Conditionally supported .
3.2.4 Excluded . 5
3.2.5 Outside the scope . 5
5
3.2.6 Not applicable .
. . . . . . . . . . . . . . .*.
4 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5 Conformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.1 Conformance Statement . 6
5.2 Relationships with base Standards . . 6
5.2.1 ACSE conformance . . 6
5.2.2 Presentation layer conformance . . 6
5.2.3 Transfer Syntax conformance . 6
.................................................................................. 6
5.2.4 Session layer conformance
...................................................................................... 6
5.2.5 Prerequisite requirement
....................................................................................... 7
5.3 Pragmatic PDU size Iimitation
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6 Association Control Service Element (ACSE)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.1 Association establishment
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.2 Association normal release
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.3 Association abnormal release
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
6.4 Application entity title
6.5 Application context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 8
6.6 Abort APDU . . . . . . . . . . . . . . . .*. 8
o ISO/IEC 1992
All rights reserved. No part of this publication may be reproduced or utilized in any form or
by any means, electronie or mechanical, including photocopying and microfilm, without per-
mission in writing from the publisher.
lSO/IEC Copyright Office l Case Postale 56 l CH-1 211 Geneve 20 l Switzerland
Printed in Switzerland
---------------------- Page: 2 ----------------------
ISO/IEC ISP 111834 : 1992 (E)
7 Presentation layer . . 8
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . m.- 8
7.1 Presentation Functional Units
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.2 Presentation context identifier
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.3 Transfer Syntax name in PDV-Iist
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.4 Encoding of User data Parameter
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.5 Encoding of CPC-type value
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.6 Presentation selector size
9
7.7 Default context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .“.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.8 Presentation context definition result list
9
7.9 Invalid encoding and Presentation aborts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
8 Transfer Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
8.1 Tag values .
9
8.2 ASN.1 length fields .
......................................................................................................... 9
8.3 Integer type values
10
8.4 Bitstring type values .
10
8.5 EXTERNAL data type .
10
8.6 PDV-Iist data type .
8.7 Constructed encoding . 10
10
9 Session layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
...................................... 10
9.1 Session Functional Units required .
11
9.2 Session version .
11
9.3 Basic concatenation . .
11
9.4 Session segmenting .
9.5 Re-use of transport connection . 11
11
9.6 Use of transport expedited .
9.7 Receipt of invalid SPDUs . 11
Annexes Page
A ISPICS Requirements List of ACSE, for the use by ROSE and CMISE . . . . . . . . . . . . . . . . . . . . . . . 12
A.l General . 12
............................. 13
A.2 Supported Functions and Initiator/Responder Capabilities
................................................................................... 13
A.2.1 Supported Functions
.................................................................... 13
A.2.2 Initiator/Responder Capability
........................................................................................... 13
A.2.3 Functional Units
A.3 Supported normal mode APDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
A.4 Supported normal mode Parameters . . 14
A.4.1 A-associate-request APDU (AARQ) .
15
A.4.2 A-associate-response APDU (AARE) . .
16
A.4.3 A-release-request APDU (RLRQ) . 17
A.4.4 A-release-response APDU (RLRE) .
17
A.4.5 Abort APDU (ABRT) . . 17
A.5 AE Title Syntax name forms . . 18
A.6 Authentication value forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .*. 18
. . .
Ill
---------------------- Page: 3 ----------------------
ISO/IEC ISP 11183-1 : 1992 (E)
A.7 Meaning of Conditional Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
B ISPICS Requirements List of Presentation, for the use by ROSE and CMISE. 19
B.l General . .
................... 19
B.2 Capabilities, Protocol Mechanisms and Functional Units .
20
B.2.1 lnitiator/Responder Capabilities .
20
B.2.2 Protocol Mechanisms .
.................. 20
B.2.3 Functional Units .
20
B.3 Supported PPDUs and equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
8.3.1 Kerne1 Functional Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
8.3.2 Presentation Context Management Functional Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
8.3.3 Presentation Context Restoration Functional Unit . . . . . . . . . . . . . . . . . . . . .*.
21
B.4 Supported Parameters . . 22
8.4.1 Connect Presentation (CP) PPDU . . 22
B.4.2 Connect Presentation Accept (CPA) PPDU .
23
8.4.3 Connect Presentation Reject (CPR) PPDU . 24
8.4.4 Abnormal Release User (ARU) PPDU .
25
B.4.5 Abnormal Release Provider (ARP) PPDU .
25
B.4.6 Alter Context (AC) PPDU . .
25
...................................................
B.4.7 Alter Context Acknowledge (ACA) PPDU 25
...................................................
B.4.8 Presentation Data (TD) PPDU . 25
............................
B.4.9 Presentation Typed Data (TTD) PPDU . 25
.........................................................................
B.4.10 Expedited Data (TE) PPDU 25
.................................................. .......................
8.4.11 Capability Data (TC) PPDU 25
B.4.12 Capability Data Acknowledge (TCC) PPDU .
25
B.4.13 Resynchronize (RS) PPDU .
25
B.4.14 Resynchronize Acknowledge (RSA) PPDU .
25
................................................................................................
B.5 Support of Syntaxes 26
B.5.1 Transfer Syntaxes Supported . 26
8.52 Abstract Syntaxes Supported . 26
B.6 Meaning of Conditional Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
C ISPICS Requirements List of Session, for the use by ROSE and CMISE . . . . . . . . . . . . . . . . . . . 27
C.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
C.2 Supported Functions, Protocol Mechanisms and
Initiator/Responder Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
C.2.1 Supported Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.2.2 Protocol Mechanisms 29
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
c.2.3 Initiator/Responder Capabilities . . . . . . . . . . . . . . . . 29
c3 . Supported SPDUs . 30
C.3.1 Kerne1 Functional Unit . 30
C.3.1.1 Sending/Receiving by Initiator . 30
C.3.1.2 Sending/Receiving by Responder . . 31
C.3.2 Negotiated Release Functional Unit . 32
C.3.3 Half Duplex Functional Unit . . 32
C.3.4 Duplex Functional Unit . 32
C.3.5 Expedited Data Functional Unit . 32
c.3.6 Typed Data Functional Unit . 32
C.3.7 Capability Data Functional Unit . 32
iv
---------------------- Page: 4 ----------------------
ISO/IEC ISP 11183-1 : 1992 (E)
C.3.8 Minor Synchronize Functional Unit . 32
C.3.9 Symmetrie Synchronize Functional Unit .32
...................................................
C.3.10 Major Synchronize Functional Unit . 32
C.3.11 Resynchronize Functional Unit . 32
C.3.12 Exceptions Functional Unit . 32
C.3.13 Activity Management Functional Unit . 32
C.4 Supported Parameters . 32
C.4.1 Connect (CN) SPDU . 33
C.4.2 Overflow Accept (OA) SPDU .
34
C.4.3 Connect Data Overflow (CDO) SPDU . 34
C.4.4 Accept (AC) SPDU .
35
C.4.5 Refuse (RF) SPDU .
36
C.4.6 Finish (FN) SPDU .
36
C.4.7 Disconnect (DN) SPDU .
37
C.4.8 Not Finished (NF) SPDU
............................................................................. 37
.........................................................................................
C.4.9 Abort (AB) SPDU 37
C.4.10 Abort Accept (AA) SPDU . 37
C.4.11 Data Transfer (DT) SPDU . 37
C.4.12 Expedited Data (EX) SPDU
......................................................................... 37
C.4.13 Typed Data (TD) SPDU . 37
C.4.14 Capability Data (CD) SPDU
......................................................................... 37
C.4.15 Capability Data Ack (CDA) SPDU
............................................................... 37
C.4.16 Give Tokens (GT) SPDU
.............................................................................. 38
C.4.17 Please Tokens (PT) SPDU
........................................................................... 38
C.4.18 Minor Sync Point (MIP) SPDU
.................................................................... 38
C.4.19 Minor Sync Ack (MIA) SPDU
....................................................................... 38
C.4.20 Major Sync Point (MAP) SPDU . 38
C.4.21 Major Sync Ack (MAA) SPDU . 38
C.4.22 Resynchronize (RS) SPDU . 38
C.4.23 Resynchronize Ack (RA) SPDU . 38
C.4.24 Prepare (PR) SPDU . . 38
C.4.25 Exception Report (ER) SPDU . 38
C.4.26 Exception Data (ED) SPDU . 38
C.4.27 Give Tokens Confirm (GTC) SPDU . 38
C.4.28 Give Tokens Ack (GTA) SPDU . 38
C.4.29 Activity Start (AS) SPDU . 38
C.4.30 Activity Resume (AR) SPDU . 38
C.4.31 Activity Interrupt (Al) SPDU . 38
C.4.32 Activity Interrupt Ack (AIA) SPDU . 38
C.4.33 Activity Discard (AD) SPDU .
38
C.4.34 Activity Discard Ack (ADA) SPDU .
38
C.4.35 Activity End (AE) SPDU .
39
C.4.36 Activity End Ack (AEA) SPDU .
39
C.5 Meaning of Conditional Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
V
---------------------- Page: 5 ----------------------
ISO/IEC ISP 11183-1 : 1992 (E)
Foreword
ISO (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 ISO 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. ISO and IEC technical com-
mittees collaborate in fields of mutual interest. Other international organ-
izations, 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 committee, lSO/IEC JTC 1. In addition to developing International
Standards, ISO/IEC JTC 1 has created a Special Group on Functional
Standardization for the elaboration of International Standardized Profiles.
An International Standardized Profile is an internationally agreed,
harmonized document which identifies a Standard or group of Standards,
together with Options and Parameters, necessary to accomplish a function
or set of functions.
Draft International Standardized Profiles are circulated to national bodies
for voting. Publication as an International Standardized Profile requires ap-
proval by at least 75 % of the national bodies casting a vote.
International Standardized Profile lSO/IEC ISP 11183-1 was prepared with
the collaboration of
- OSI Asia-Oceania Workshop (AOW);
- European Workshop for Open Systems (EWOS);
- OSI Implementors Workshop (OIW).
lSO/IEC ISP 11183 consists of the following Parts under the general title
Information technology - International Standardized Profiles AOM In OSI
Management - Management Communications:
- Part 7: Specification of ACSE, presentation and Session protocols
for the use by ROSE and CMISE
- Part 2: CMISE/ROSE for AOMV - Enhanced Management Com-
munica tions
- Part 3: CMISE/ROSE for AOMI 7 - Basic Management Com-
munica tions
Annexes A, B and C form an integral part of this part of lSO/IEC
ISP 11183.
Vi
---------------------- Page: 6 ----------------------
ISO/IEC ISP 11183-1 : 1992 (E)
Introduction
This International Standardized Profile (ISP) is defined within the context of Functional Standardization, in
accordance with the principles specified by ISO/IEC TR 10000, “Framework and Taxonomy of International
Standardized Profiles”. The context of Functional Standardization is one part of the Overall field of Information
Technology (IT) standardization activities, covering base Standards, profiles and registration mechanisms. A
Profile defines a combination of base Standards that collectively perform a specific weil-defined IT Function.
Profiles standardize the use of Options and other variations in the base Standards, and provide a basis for the
development of uniform, internationally recognized conformance test suites.
One of the most important roles for an ISP is to serve as the basis for the development (by organizations other
than ISO and IEC) of internationally recognized tests and test centres. ISPs are produced not simply to
“legitimize” a particular choice of base Standards and Options, but to promote real System interoperability. The
development and widespread acceptance of tests based on this and other ISPs is crucial to the successful
realization of this goal.
The text for this patt of lSO/IEC ISP 11183 was developed in close cooperation among the Network
Management Expert Groups of the three International OSI Workshops: the European Workshop for Open
Systems (EWOS), the NIST Workshop for Implementors of OSI (NIST OIW) and the OSI Asia-Oceania Workshop
(AOW). This ISP is harmonized among these three Workshops and it was finally ratified by the
Workshops’plenary assemblies.
This part of ISO/IEC ISP 11183 contains three normative annexes:
Annex A ISPICS Requirements List of ACSE
Annex B ISPICS Requirements List of Presentation
Annex C ISPICS Requirements List of Session.
The expression “International Standardized Profile” is replaced by the abbreviation “ISP” in the following clauses
and annexes.
vii
---------------------- Page: 7 ----------------------
ISO/IEC ISP 111834 : 1992 (E)
. . .
VIII
---------------------- Page: 8 ----------------------
ISO/IEC ISP 11183=1:1992(E)
INTERNATIONAL STANDARDIZED PROFILE
Information technofogy
- International Standardized
Profiles AOMI n OSI Management
- Management
Communications -
Part 1:
Specification of ACSE, presentation and Session protocols
for the use by ROSE and CMISE
1 Scope
1 .l General
This part of ISO/IEC ISP 11183 specifies how the Association Control Service Element, the Presentation Layer,
and the Session Layer Standards shall be used to provide the required upper layer functions for the
CMISE/ROSE functions (see also figure 1). These specifications are therefore the common basis for the
application functions as defined in ISO/IEC ISP 11183-2, ISO/IEC ISP 11183-3 and any of the subsequent Parts
that might be developed.
NOTE - This part of ISO/IEC ISP 11183 will be aligned with the future ISO/IEC ISP 111884, Common Upper Layer Requirements - Part 1:
Basic connection oriented requirements, which is currently under development.
1.2 Position within the Taxonomy
This part of ISO/IEC ISP 11183 is the first Part, as common text, of a multipart ISP identified in lSO/IEC TR
10000-2 as “AOM, OSI Management Communications” (see also ISO/IEC TR 100004, 8.2 for the definition of
multipatt ISPs).
It may be combined with any T-Profiles (see ISO/IEC TR 10000) specifying the OSI connection-mode transport
Service.
---------------------- Page: 9 ----------------------
ISO/IEC ISP 11183-1 : 1992 (E)
1.3 Scenario
The model used is one of two end Systems running an end-to-end association using the ACSE, Presentation and
Session Services and protocols (see figure 1).
CMISE
ACSE
ROSE
Presentation
Presentation
Session
Session
~
Transport Service provider
Figure 1 - Model of the supportive layers
Any Systems management application entity (SMAE), located on each end System, may be association-initiator
or association-responder, by agreeing on
...