ISO-ISP-11188-1-1995.pdf

INTERNATIONAL STANDARDIZED PROFILE ISOJIEC ISP 11188-I First edition 1995-04-I 5 Information technology - International Standardized Profile - Common upper layer requirements - Part 1: Basic connection oriented requirements Technologies de /information - Profil normalisk international - Prescriptions communes pour la couche sup - European Workshop for Open Systems (EWOS); - OSE Implementors Workshop (OIW). ISO/IEC ISP 11188 consists of the following parts, under the general title Information technology - International Standardized Profile - Common upper layers requirements : - Part 1 : Basic connection oriented requirements - Part 2 : Basic connection oriented requirements for ROSE-based Profiles - Part 3 : Minimal OSI upper layer facilities Annexes A and B form an integral part of this part of ISO/IEC ISP 11188. Annex C is for information only. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 06:16:32 MDTNo reproduction or networking permitted without license from IHS -,-,- ISOAEC ISP 11188-l : 1995 (E) 0 ISO/IEC Introduction This part of ISO/IEC ISP 11188 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 stan- dards, profiles, and registration mechanisms. A profile defines a combination of base standards that collectively perform a specific well-defined IT function. Profiles standardize the use of options and other variations in the base stan- dards, and provide a basis for the development of uniform, internationally recognized system tests. ISO/IEC ISP 11188 as a multi-part ISP specifies general requirements on the use of OSI connection-mode protocols by A-profiles. These are identified as “Common Upper Layer Requirements”. The parts of this multi-part ISP can be referenced normatively by other ISPs or referencing specifications. In addition, a referencing ISP may specify further requirements on the protocols, provided it does not contradict this ISP. The purpose of this multi-part ISP is to provide common text for ISPs or other referencing specifications which specify A-profiles. In addition to simplifying their drafting, it also facilitates the common implementation of the protocols for use in different A-profile contexts. This part of ISO/IEC 11188 specifies the use of the connection-mode proto- cols of the ACSE, Presentation and Session layers of OSI. Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 06:16:32 MDTNo reproduction or networking permitted without license from IHS -,-,- INTERNATIONAL STANDARDIZED PROFILE ISOIEC lSO/lEC ISP 11188-1 : 1995 (E) Information technology - International Standardized Profile - Common upper layers requirements - Part 1: Basic connection oriented requirements 1 Scope 1 .l General This part of ISO/IEC ISP 11188 specifies the common upper layers elements of A-profiles (see TR 10000-2, 5.5.3). The common elements are specified by reference to OSI connection-mode standards for the ACSE protocol, the presentation layer protocol, and the session layer protocol. A specification defining an A-profile (see TR 10000-2, 5.5.3) may reference this part of ISO/IEC ISP 11188 as a common basis for the selection of elements of the up- per layers protocols (ACSE, presentation and session) that it uses. The use of this part of ISO/IEC ISP 11188 is supple- mented by a statement of the specific upper layers requirements of the referencing specification for the use of ACSE, presentation and session protocol standards. The rest of the A-profile definition, including, for in- stance, its use of standards for Application Service Elements (ASE, see also figure l), follows the general rules of TR lOOC01. 1.2 Position within the taxonomy This part of ISO/IEC ISP 11188 does not specify a full A-profile, and therefore has no place within the taxon- omy of TR 100D2. 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). I I Transport service provider Figure 1 - Model of the supportive layers 2 Compliance 2.1 Compliance statement A referencing specification may use the requirements in this part of ISO/IEC ISP 11188 and claim compliance to them, in one of the following ways: 4 b) The referencing specification does not duplicate any of the requirements of this part of ISO/IEC ISP 11188 within its own specifications and instead re- quires the implementation to conform to the re- quirements of this part of ISO/IEC ISP 11188. This is the preferred method. The referencing specification replicates all of the requirements of this part of ISO/IEC ISP 11188 as part of its requirements and related conformance statements. In the case of (b), a reference to this part of ISO/IEC ISP 11188 shall be included in clause 1 (Scope) as well as in clause 3 (Normative references) of the referenc- ing specification. 2.1.1 A referencing specification that replicates all of the requirements of this part of ISO/IEC ISP 11188 complies if the specific upper layers requirements of the referencing specification do not conflict with the requirements of this part of ISO/IEC ISP 11188. 2.1.2 A specification that requires an implementation to conform to the requirements contained within this part of ISO/IEC ISP 11188 complies if a) the conformance requirement of the referencing specification states that an implementation shall conform to the requirements of this part of ISO/IEC ISP 11188; and b) the specific upper layers requirements of the referencing specification do not conflict with the requirements of this part of ISO/IEC ISP 11188. 2.1.3 This part of ISO/IEC ISP 11188 states re- quirements upon implementations to achieve inter- working. A claim of compliance is a claim that all requirements in the relevant base standards are satisfied, and that all requirements in this part of ISO/IEC ISP 11188 are sat- isfied. Annex A states the relationship between these requirements and those of the base standards. Optional features of the referenced base standards for which no requirement is specified in clauses 6, 7, 8, 9 or in annex A, are considered as open for referencing specifications (see table 1 for a definition of “open”). 1 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 06:16:32 MDTNo reproduction or networking permitted without license from IHS -,-,- lSO/lEC ISP 11188-l : 1995 (E) 0 ISOAEC 2.2 Relationship with base standards A compliant referencing specification shall require an implementation that claims conformance to the refer- encing specification to include the aspects specified in 2.2.1 through 2.2.4. 2.2.1 ACSE conformance To conform to the Association Control Service Element (ACSE) protocol as constrained by this part of ISO/IEC ISP 11188, either the X.41 O-l 984 mode, or the normal mode, or both shall be implemented. 2.2.2 Presentation layer conformance To conform to the presentation protocol as constrained by this part of ISO/IEC ISP 11188, implementations shall implement either the normal mode or the X.410- 1984 mode or both and shall implement the initiator role, responder role, or both roles, compatible with those in ACSE (identified in clause A.5). 2.2.3 Transfer syntax conformance An implementation shall support the “Basic Encoding of a single ASN.l type” (BER) as specified in ITU-T Rec. X.690 I ISO/IEC 8825-1, except where the referencing specification or the associated base standard specifies some other mandatory encoding, together with the additional rules defined in clause 8, for the generation of protocol encoding specified in ASN.l. The referencing specification may require support of this or other transfer syntaxes for any abstract syntaxes which it defines. NOTE - At the time of publication, the BER was adequate to satisfy all proposed profiles. 2.2.4 Session layer conformance To conform to the session protocol as constrained by this part of ISO/IEC ISP 11188, implementations shall implement all the features identified in A.6 as required to be implemented. 3 Normative references The following ITU-T Recommendations and Interna- tional Standards contain provisions which, through ref- erence in this text, constitute provisions of this part of ISO/IEC ISP 11188. At the time of publication, the editions indicated were valid. All Recommendations and International Standards are subject to revision, and parties to agreements based on this part of ISO/IEC ISP 11188 are encouraged to investigate the possibility of applying the most recent edition of the Recommendations and International Standards indicated below. Members of IEC and IS0 maintain registers of currently valid International Standards and ISPs. The ITU-T secretariat maintains a list of currently valid Recommendations. 3.1 Identical Recommendations I Inter- national Standards - ITU-T Recommendation X.200 (1994) I ISO/IEC 7498-l :1994, Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model. ITU-T Recommendation X.225 (1994) I ISO/IEC 8327-l: 2), information technology - Open Systems interconnection - Connection-oriented session protocol : Protocol specification. ITU-T Recommendation X.226 (1994) I ISO/IEC 8823-l :1994, information technology - Open Systems interconnection - Connection-oriented presentation protocol : Protocol specification. ITU-T Recommendation X.227 (1994) I ISO/IEC 8650-l: 3), Information technology - Open Systems Interconnection - Connection-oriented protocol for the Association Control Service Element : Protocol specification. ITU-T Recommendation X.245 (1994) I ISO/IEC 8327-2:) , information technology - Open Systems interconnection - Connection-oriented session protocol : Protocol Implementation Conformance Statement (PIGS) proforma. ITU-T Recommendation X.246 (1994) I ISO/IEC 8823-2:-l), Information technology - Open Systems interconnection - Connection-oriented presentation protocol: Protocol Implementation Conformance Statement (PICSI proforma. ITU-T Recommendation X.247 (1994) I ISO/IEC 8650-2: 3), Information technology - Open Systems Interconnection - Connection-oriented protocol for the Association Control Service Element : Protocol Implementation Conformance Statement (PIGS) proforma. ITU-T Recommendation X.680 (1994) I ISO/IEC 8824-l: 4, , Information technology - Abstract Syntax Notation One (ASN. 1) : Specification of basic notation. ITU-T Recommendation X.680.1 (1994) I ISO/IEC 8824-1lAmd.l :I, information technology - Abstract Syntax Notation One (ASN. 7) : Specification of basic notation - Amendment 1 : Rules of Extensibility. ITU-T Recommendation X.690 (1994) I ISO/IEC 8825-l: 5, , Information technology - ASN.l encoding rules : Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). 3.2 Additional references - CCITT Recommendation X.650 (1992), Open Systems Interconnection (OS/) - Reference model for naming and addressing. 1 kurrantly at stage of draft. 2)Revision of I80 8327:1987. To be published. 3)Revision of I60 8650:193. To be published. 4)Revision of ISO/lEC 8824:1990. To be published. 5)Revision of ISO/IEC 8825:1990. To be published. 2 Copyright International Organization for Standardization Provided by IHS under license with ISO Licensee=NASA Technical Standards 1/9972545001 Not for Resale, 04/19/2007 06:16:32 MDTNo reproduction or networking permitted without license from IHS -,-,- Q ISOAEC ISO/IEC ISP 11188-1 : 1995 (E) - IS0 7498-3:1988, information processing systems - Open Systems Interconnection - Basic Reference Model - Part 3: Naming and addressing. - ISO/IEC TR lOm1:1992, information technology - Framework and taxonomy of International Standard- ized Profiles - Part 1 : Framework. - ISO/IEC TR 1COCD2:1994, information technology Framework and taxonomy of International Standardized Profiles - Part 2 : Principles and Taxonomy for OSI Profiles. NOTE - This part of ISO/IEC ISP 11188 makes detailed references to subclauses of the specified editions of some of the above references. 4 Definitions For the purposes of this part of ISO/IEC ISP 11188, the following definitions apply. Terms used in this part of ISO/IEC ISP 11188 are de- fined in the referenced base standards. In addition the following terms are defined. 4.1 General referencing specification : a specification of an A-profile which includes by reference or by replication, the requirements in this part of ISO/IEC 11188. 4.2 Support level To specify the support level of protocol features for this part of ISO/IEC ISP 11188, the following terminology is defined : a) Column 1 of table 1 lists the support level identifiers for a profile used in this part of ISO/IEC ISP 11188; b) Column 2 of table 1 defines the use of these requirements classifications of column 1 by a referencing specification; c) Column 3 of table 1 defines the use of the requirements classifications by an implementation. Table l- Profile status identifiers Identifier Meaning when referenced by a Meaning when referenced by an specification implementation n mandatory - The feature shall be required mandatory - The implementation shall support the for support. The status of the feature shall feature, i.e. its syntax and procedures shall be imple- remain mandatory in a referencing mented as specified in the base standard or in this part specification (see note). of ISO/IEC ISP 11188. However, it is not a requirement that the feature shall be used in all instances of communication unless mandated by the base standard or stated otherwise in this part of ISO/IEC ISP 11188. The feature shall be the subject of an ISP conformance test (see note). 0 optional - The choice of whether this optional - The implementation may decide either tc feature is supported or it is not supported support or to not support the feature. is made by the implementation. The status of the feature shall remain optional in a l Supporting a feature means that the feature referencing specification. shall be handled as if it was mandatory. . Not supporting a feature depends on receiving or sending : For sending, the features capability is not used; For receiving an optional parameter, the syntax shall be implemented and the para- meter may be ignored. The feature shall be the subject of an ISP c