35.100.01 开放系统互连(OSI)综合 标准查询与下载

GSO ISO/IEC 10181-1:2013 信息技术 开放系统互连 开放系统的安全框架：概述

The security frameworks address the application of security services in an Open Systems environment, where the term Open Systems is taken to include areas such as Database, Distributed Applications, ODP and OSI. The security frameworks are concerned with defining the means of providing protection for systems and objects within systems, and with the interactions between systems. The security frameworks are not concerned with the methodology for constructing systems or mechanisms. The security frameworks address both data elements and sequences of operations (but not protocol elements) which are used to obtain specific security services. These security services may apply to the communicating entities of systems as well as to data exchanged between systems, and to data managed by systems. The security frameworks provide the basis for further standardization, providing consistent terminology and definitions of generic abstract service interfaces for specific security requirements. They also categorize the mechanisms that can be used to achieve those requirements. One security service frequently depends on other security services, making it difficult to isolate one part of security from the others. The security frameworks address particular security services, describe the range of mechanisms that can be used to provide the security services, and identify interdependancies between the services and the mechanisms. The description of these mechanisms may involve a reliance on a different security service, and it is in this way that the security frameworks describe the reliance of one security service on another. This part of the security frameworks: — describes the organization of the security frameworks; — defines security concepts which are required in more than one part of the security frameworks; — describes the inter-relationship of the services and mechanisms identified in other parts of the frameworks.

Information technology -- Open Systems Interconnection -- Security frameworks for open systems: Overview

GSO ISO/IEC 10181-4:2013 信息技术 开放系统互连 开放系统的安全框架：不可否认框架

This Recommendation | International Standard addresses the application of security services in an Open Systems environment, where the term "Open Systems" is taken to include areas such as Database, Distributed Applications, Open Distributed Processing and OSI. The Security Frameworks are concerned with defining the means of providing protection for systems and objects within systems, and with the interactions between systems. The Security Frameworks are not concerned with the methodology for constructing systems or mechanisms. The Security Frameworks address both data elements and sequences of operations (but not protocol elements) which are used to obtain specific security services. These security services may apply to the communicating entities of systems as well as to data exchanged between systems, and to data managed by systems. This Recommendation | International Standard: — defines the basic concepts of Non-repudiation; — defines general Non-repudiation services; — identifies possible mechanisms to provide the Non-repudiation services; — identifies general management requirements for Non-repudiation services and mechanisms. As with other security services, Non-repudiation can only be provided within the context of a defined security policy for a particular application. The definitions of security policies are outside the scope of this Recommendation | International Standard. The scope of this Recommendation | International Standard does not include specification of details of the protocol exchanges which need to be performed in order to achieve Non-repudiation. This Recommendation | International Standard does not describe in detail the particular mechanisms that can be used to support the Non-repudiation services nor does it give details of the supporting security management services and protocols. Some of the procedures described in this framework achieve security by the application of cryptographic techniques. This framework is not dependent on the use of a particular cryptographic or other algorithm or on particular cryptographic techniques (i.e. symmetric or asymmetric) although certain classes of Non-repudiation mechanisms may depend on particular algorithm properties. Indeed it is likely, in practice, that a number of different algorithms will be used. Two entities wishing to use cryptographically-protected data must support the same cryptographic algorithm. [ | NOTE — Although ISO does not standardize cryptographic algorithms, it does standardize the procedures used to register them in ISO/IEC 9979.] A number of different types of standard can use this framework including: 1) standards that incorporate the concept of Non-repudiation; 2) standards that specify abstract services that include Non-repudiation; 3) standards that specify uses of a Non-repudiation service; 4) standards that specify the means of providing Non-repudiation within an open system architecture; and 5) standards that specify Non-repudiation mechanisms. Such standards can use this framework as follows: — standards of type 1), 2), 3), 4) or 5) can use the terminology of this framework; — standards of type 2), 3), 4) or 5) can use the facilities defined in clause 7; and — standards of type 5) can be based upon the classes of mechanism defined in clause 8.

Information technology -- Open Systems Interconnection -- Security frameworks for open systems: Non-repudiation framework

GSO ISO/IEC 10181-6:2013 信息技术 开放系统互连 开放系统的安全框架：完整性框架

The Recommendation | International Standard on Security Frameworks for Open Systems addresses the application of security services in an Open Systems environment, where the term "Open System" is taken to include areas such as Database, Distributed Applications, Open Distributed Processing and OSI. The Security Frameworks are concerned with defining the means of providing protection for systems and objects within systems, and with the interactions between systems. The Security Frameworks are not concerned with the methodology for constructing systems or mechanisms. The Security Frameworks address both data elements and sequences of operations (but not protocol elements) which may be used to obtain specific security services. These security services may apply to the communicating entities of systems as well as to data exchanged between systems, and to data managed by systems. This Recommendation | International Standard addresses the integrity of data in information retrieval, transfer, and management: 1) defines the basic concept of data integrity; 2) identifies possible classes of integrity mechanism; 3) identifies facilities for each class of integrity mechanisms; 4) identifies management required to support the class of integrity mechanism; 5) addresses the interaction of integrity mechanism and the supporting services with other security services and mechanisms. A number of different types of standard can use this framework, including: 1) standards that incorporate the concept of integrity; 2) standards that specify abstract services that include integrity; 3) standards that specify uses of an integrity service; 4) standards that specify means of providing integrity within an open system architecture; and 5) standards that specify integrity mechanisms. Such standards can use this framework as follows: — standards of type 1), 2), 3), 4) and 5) can use the terminology of this framework; — standards of type 2), 3), 4) and 5) can use the facilities identified in clause 7; — standards of type 5) can be based upon the classes of mechanisms identified in clause 8. Some of the procedures described in this security framework achieve integrity by the application of cryptographic techniques. This framework is not dependent on the use of particular cryptographic or other algorithms, although certain classes of integrity mechanisms may depend on particular algorithm properties. NOTE — Although ISO does not standardize cryptographic algorithms, it does standardize the procedures used to register them in ISO/IEC 9979. The integrity addressed by this Recommendation | International Standard is that defined by the constancy of a data value. This notion (constancy of a data value) encompasses all instances in which different representations of a data value are deemed equivalent (such as different ASN.1 encodings of the same value). Other forms of invariance are excluded. The usage of the term data in this Recommendation | International Standard includes all types of data structures (such as sets or collections of data, sequences of data, file-systems and databases). This framework addresses the provision of integrity to data that are deemed to be write-accessible to potential attackers. Therefore, it focusses on the provision of integrity through mechanisms, both cryptographic and non-cryptographic that do not rely exclusively on regulating access.

Information technology -- Open Systems Interconnection -- Security frameworks for open systems: Integrity framework

GSO ISO/IEC 10181-5:2013 信息技术 开放系统互连 开放系统的安全框架：保密框架

This Recommendation | International Standard on Security Frameworks for Open Systems addresses the application of security services in an Open Systems environment, where the term "Open System" is taken to include areas such as Database, Distributed Applications, Open Distributed Processing and OSI. The Security Frameworks are concerned with defining the means of providing protection for systems and objects within systems, and with the interactions between systems. The Security Frameworks are not concerned with the methodology for constructing systems or mechanisms. The Security Frameworks address both data elements and sequences of operations (but not protocol elements) which may be used to obtain specific security services. These security services may apply to the communicating entities of systems as well as to data exchanged between systems, and to data managed by systems. This Recommendation | International Standard addresses the confidentiality of information in retrieval, transfer and management. It: 1) defines the basic concepts of confidentiality; 2) identifies possible classes of confidentiality mechanisms; 3) classifies and identifies facilities for each class of confidentiality mechanisms; 4) identifies management required to support the classes of confidentiality mechanism; and 5) addresses the interaction of confidentiality mechanism and the supporting services with other security services and mechanisms. A number of different types of standards can use this framework, including: 1) standards that incorporate the concept of confidentiality; 2) standards that specify abstract services that include confidentiality; 3) standards that specify uses of a confidentiality service; 4) standards that specify means of providing confidentiality within an open system architecture; and 5) standards that specify confidentiality mechanisms. Such standards can use this framework as follows: — standards of type 1), 2), 3), 4) and 5) can use the terminology of this framework; — standards of type 2), 3), 4) and 5) can use the facilities defined in clause 7 of this framework; — standards of type 5) can be based upon the classes of mechanism defined in clause 8 of this framework. As with other security services, confidentiality can only be provided within the context of a defined security policy for a particular application. The definitions of specific security policies are outside the scope of this Recommendation | International Standard. It is not a matter for this Recommendation | International Standard to specify details of the protocol exchanges which need to be performed in order to achieve confidentiality. This Recommendation | International Standard does not specify particular mechanisms to support these confidentiality services nor the full details of security management services and protocols. Generic mechanisms to support confidentiality are described in clause 8. Some of the procedures described in this security framework achieve confidentiality by the application of cryptographic techniques. This framework is not dependent on the use of particular cryptographic or other algorithms, although certain classes of confidentiality mechanisms may depend on particular algorithm properties. NOTE — Although ISO does not standardize cryptographic algorithms, it does standardize the procedures used to register them in ISO/IEC 9979:1991, Procedures for the registration of criptographic algorithms. This framework addresses the provision of confidentiality when the information is represented by data that are read-accessible to potential attackers. Its scope includes traffic flow confidentiality.

Information technology -- Open Systems Interconnection -- Security frameworks for open systems: Confidentiality framework

GSO ISO/IEC 14765:2013 信息技术 协议定义和封装的框架

In a layered approach to protocol architecture, protocols have a relationship to one another such that a protocol at layer (n) uses the services of the layer below it — the (n − 1) services — which, in turn, are provided by a layer (n − 1) protocol. One of the services used by a layer (n) protocol is the encapsulation of its (n) Protocol Data Units (PDUs) in a way which is transparent to it. Such encapsulation is realized by the carriage of the (n) PDUs as user data in an (n − 1) Service Data Unit (SDU). In a limited case, the operation of a particular protocol at layer (n − 1) implies the operation, above layer (n − 1), of a single layer (n) protocol or single set of related (n) / (n + 1)... protocols. However, in a more general case, there may be more than one protocol (or set of related protocols starting) at layer (n) that can operate above layer (n − 1) in a given environment. In such cases, there is a need for explicit identification of the protocol (or set of protocols starting) at layer (n). There also may be a need to manipulate the (n − 1) protocol (i.e. the encapsulating protocol) in certain ways specific to the layer (n) protocol (i.e. the encapsulated protocol). Such manipulations form the basis of a set of procedures that must be specified for the layer (n) protocol. The above observations regarding protocol identification and encapsulation are also applicable in cases where an (n) layer is further divided into sublayers. Cases in which an (n) protocol operates for the purpose of establishing a parallel universe of protocols (regardless of the layered structure of that universe) also give rise to a need for the (n) protocol to be able to identify the protocol(s) in the parallel universe. In these cases, however, there is no encapsulating/encapsulated relationship between the (n) protocol and the parallel universe set of protocols. The above principles lead to a need to establish a framework for protocol identification and encapsulation. These principles apply to the relationship between two protocols (recognizing that one of them may be a set of related protocols) and can be applied recursively. This Recommendation | International Standard provides a framework for explicit protocol identification and for protocol encapsulation. Implicit protocol identification (see 4.2) is beyond the scope of this Recommendation | International Standard.

Information technology -- Framework for protocol identification and encapsulation

GSO ISO 7498-2:2013 信息处理系统 开放系统互连 基本参考模型 第2部分：安全设计

This part of ISO 7498: a) provides a general description of security services and related mechanisms, which may be provided by the Reference Model; and, b) defines the positions within the Reference Model where the services and mechanisms may be provided. This part of ISO 7498 extends the field of application of ISO 7498, to cover secure communications between open systems. Basic security services and mechanisms and their appropriate placement have been identified for all layers of the Basic Reference Model. In addition, the architectural relationships of the security services and mechanisms to the Basic Reference Model have been identified. Additional security measures may be needed in endsystems, installations and organizations. These measures apply in various application contexts. The definition of security services needed to support such additional security measures is outside the scope of this standard. OSI security functions are concerned only with those visible aspects of a communications path which permit end systems to achieve the secure transfer of information between them. OSI Security is not concerned with security measures needed in end systems, installations, and organizations, except where these have implications on the choice and position of security services visible in OSI. These latter aspects of security may be standardized but not within the scope of OSI standards. This part of ISO 7498 adds to the concepts and principles defined in ISO 7498; it does not modify them. It is not an implementation specification, nor is it a basis for appraising the conformance of actual implementations.

Information processing systems -- Open Systems Interconnection -- Basic Reference Model -- Part 2: Security Architecture

GSO ISO/IEC 9834-6:2013 信息技术 开放系统互连 OSI 注册机构操作程序：注册和申请应用实体的流程

This Recommendation | International Standard specifies the procedures applicable to the registration of application-processes and application-entities. No requirement for an international registration authority has been identified; therefore these procedures apply to registration at any point in the ASN.1 object identifier tree. This Recommendation | International Standard does not cover the registration of application-process types or application-entity types. No requirement for such registration has been identified.

Information technology -- Open Systems Interconnection -- Procedures for the operation of OSI Registration Authorities: Registration of application processes and application entities

GSO ISO/IEC 10181-7:2013 信息技术 开放系统互连 开放系统的安全框架：安全审计和警报框架

This Recommendation | International Standard addresses the application of security services in an Open Systems environment, where the term "Open Systems" is taken to include areas such as Database, Distributed Applications, Open Distributed Processing and OSI. The Security Frameworks are concerned with defining the means of providing protection for systems and objects within systems, and with the interactions between systems. The Security Frameworks are not concerned with the methodology for constructing systems or mechanisms. The Security Frameworks address both data elements and sequences of operations (but not protocol elements) which are used to obtain specific security services. These security services may apply to the communicating entities of systems as well as to data exchanged between systems, and to data managed by systems. The purpose of security audit and alarms as described in this Recommendation | International Standard is to ensure that open system-security-related events are handled in accordance with the security policy of the applicable security authority. In particular, this framework: a) defines the basic concepts of security audit and alarms; b) provides a general model for security audit and alarms; and c) identifies the relationship of the Security Audit and Alarms service with other security services. As with other security services, a security audit can only be provided within the context of a defined security policy. The Security Audit and Alarms model provided in clause 6 supports a variety of goals not all of which may be necessary or desired in a particular environment. The security audit service provides an audit authority with the ability to specify the events which need to be recorded within a security audit trail. A number of different types of standard can use this framework including: 1) standards that incorporate the concept of audit and alarms; 2) standards that specify abstract services that include audit and alarms; 3) standards that specify uses of audit and alarms; 4) standards that specify the means of providing audit and alarms within an open system architecture; and 5) standards that specify audit and alarms mechanisms. Such standards can use this framework as follows: — standard types 1), 2), 3), 4) and 5) can use the terminology of this framework; — standard types 2), 3), 4) and 5) can use the facilities defined in clause 8; and — standard types 5) can be based upon the characteristics of mechanisms defined in clause 9.

Information technology -- Open Systems Interconnection -- Security frameworks for open systems: Security audit and alarms framework

GSO ISO/IEC 9646-2:2013 信息技术 开放系统互连 兼容性测试方法和框架 第2部分：通用测试套件规范

.1 This part of ISO/IEC 9646 specifies the requirements and gives guidance for the production of system-independent conformance test suites for one or more OSI specifications. In particular, it is applicable to the production of all OSI conformance testing specifications including all draft versions of such conformance testing specifications. 1.2 This part of ISO/IEC 9646 is applicable to the production of abstract test cases which check the conformance of an implementation to the relevant static and/or dynamic conformance requirements by controlling and observing protocol behaviour. The Abstract Test Methods included in this part of ISO/IEC 9646 are, in fact, capable of being used to specify any test case which can be expressed abstractly in terms of control and observation of Protocol Data Units (PDUs) and Abstract Service Primitives (ASPs). Nevertheless, for some protocols, test cases may be needed which cannot be expressed in these terms. The specification of such test cases is outside the scope of this part of ISO/IEC 9646, although the test cases may themselves need to be included in a conformance testing specification. NOTE — For example, some static conformance requirements related to an Application service may require testing techniques which are specific to that particular Application. This part of ISO/IEC 9646 is applicable to the production of test suites for testing implementations of one or more adjacent protocols, whether or not these are embedded under other protocols. 1.3 The following are outside the scope of this part of ISO/IEC 9646: a) the relationship between Abstract Test Suite (ATS) specification and Formal Description Techniques; b) testing by means of test methods which are specific to particular applications, protocols or systems, including testing by means other than PDU exchange. NOTE — This part of ISO/IEC 9646 applies fully to some but not all Physical layer protocols. Nevertheless, many of the concepts apply to all protocols.

Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 2: Abstract Test Suite specification

GSO ISO/IEC 10181-3:2013 信息技术 开放系统互联 开放系统的安全框架：访问控制框架

The Security Frameworks are intended to address the application of security services in an Open Systems environment, where the term Open Systems is taken to include areas such as Database, Distributed Applications, ODP and OSI. The Security Frameworks are concerned with defining the means of providing protection for systems and objects within systems, and with the interactions between systems. The Security Frameworks are not concerned with the methodology for constructing systems or mechanisms. The Security Frameworks address both data elements and sequences of operations (but not protocol elements) that are used to obtain specific security services. These security services may apply to the communicating entities of systems as well as to data exchanged between systems, and to data managed by systems. In the case of Access Control, accesses may either be to a system (i.e. to an entity that is the communicating part of a system) or within a system. The information items that need to be presented to obtain the access, as well as the sequence of operations to request the access and for notification of the results of the access, are considered to be within the scope of the Security Frameworks. However, any information items and operations that are dependent solely on a particular application and that are strictly concerned with local access within a system are considered to be outside the scope of the Security Frameworks. Many applications have requirements for security to protect against threats to resources, including information, resulting from the interconnection of Open Systems. Some commonly known threats, together with the security services and mechanisms that can be used to protect against them, in an OSI environment, are described in CCITT Rec. X.800 | ISO 7498-2. The process of determining which uses of resources within an Open System environment are permitted and, where appropriate, preventing unauthorized access is called access control. This Recommendation | International Standard defines a general framework for the provision of access control services. This Security Framework: a) defines the basic concepts for access control; b) demonstrates the manner in which the basic concepts of access control can be specialized to support some commonly recognized access control services and mechanisms; c) defines these services and corresponding access control mechanisms; d) identifies functional requirements for protocols to support these access control services and mechanisms; e) identifies management requirements to support these access control services and mechanisms; f) addresses the interaction of access control services and mechanisms with other security services and mechanisms. As with other security services, access control can be provided only within the context of a defined security policy for a particular application. The definition of access control policies is outside the scope of this Recommendation | International Standard, however, some characteristics of access control policies are discussed. It is not a matter for this Recommendation | International Standard to specify details of the protocol exchanges which may need to be performed in order to provide access control services. This Recommendation | International Standard does not specify particular mechanisms to support these access control services nor the details of security management services and protocols. A number of different types of standard can use this framework including: a) standards that incorporate the concept of access control; b) standards that specify abstract services that include access control; c) standards that specify uses of an access control service; d) standards that specify the means of providing access control within an Open System environment; and e) standards that specify access control mechanisms. Such standards can use this framework as follows: — standard types a, b, c, d, and e can use the terminology of this framework; — standard types b, c, d, and e can use the facilities defined in clause 7 of this framework; and — standard type e can be based upon the classes of mechanism defined in clause 8.

Information technology -- Open Systems Interconnection -- Security frameworks for open systems: Access control framework

GSO ISO/IEC 9646-5:2013 信息技术 开放系统互连 兼容性测试方法和框架 第5部分：评估过程的要求、测试实验室和客户

Scope 1.1 This part of ISO/IEC 9646 specifies requirements on both the test laboratory and the client, for the conduct of the conformance assessment process. The requirements are those necessary to achieve comparability of results of tests on similar implementations performed by different test laboratories. Implementations could support one base specification only, multiple base specifications or one or more profile(s) based on one or more base specifications. This part of ISO/IEC 9646 also provides some guidance on the conformance assessment process. 1.2 The requirements include a) requirements for the testability of the implementation with respect to Abstract Test Methods; b) general requirements on the test laboratory and the client applicable to any conformance assessment process; c) exchange of technical and administrative information, including a System Conformance Statement, an Implementation Conformance Statement for each relevant base or profile specification, and Implementation eXtra Information for Testing for each Abstract Test Suite (ATS) to be used for testing each base specification, combination of base specifications or component of each profile, as appropriate, plus for profile testing the Profile Test Specification Summary for each profile; d) cooperation between the test laboratory and the client to reach an agreement on the definition of the Implementation Under Test), on the Abstract Test Methods and ATSs to be used and on the conditions under which testing will be performed; e) requirements for the structure and content of the conformance test reports that document the results of the conformance assessment process. 1.3 This part of ISO/IEC 9646 is applicable equally to those test laboratories which are affiliated to suppliers or procurers, and those which are independent. 1.4 This part of ISO/IEC 9646 is applicable to conformance assessment of implementations of — OSI and Integrated Services Digital Network (ISDN) base specifications that comply with the relevant requirements for testability in ISO/IEC 9646-2, and/or — OSI and ISDN profile specifications that comply with the relevant requirements for testability in ISO/IEC 9646-6,based on — conformance testing specifications specified in compliance with ISO/IEC 9646-2, — and if appropriate based on Profile Test Specification Summaries and Profile Specific Test Specifications specified in compliance with ISO/IEC 9646-6, and using Means of Testing (MOT) in compliance with ISO/IEC 9646-4. 1.5 The following are outside the scope of this part of ISO/IEC 9646: a) the production of diagnostic trace information, additional to that in the conformance log, resulting from testing performed by the test laboratory, and the supply to the client; b) aspects of test laboratory operations which are not specific to conformance testing implementations of OSI base specifications and profiles; c) accreditation of test laboratories; d) certification of implementations of OSI protocols.

Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 5: Requirements on test laboratories and clients for the conformance assessment process

GSO ISO/IEC 11586-1:2013 信息技术 开放系统互连 通用高层安全：概述模型和编码

Scope 1.1 This series of Recommendations | International Standards defines a set of generic facilities to assist in the provision of security services in OSI applications. These include: a) a set of notational tools to support the specification of selective field protection requirements in an abstract syntax specification, and to support the specification of security exchanges and security transformations; b) a service definition, protocol specification and PICS proforma for an application-service-element (ASE) to support the provision of security services within the Application Layer of OSI; c) a specification and PICS proforma for a security transfer syntax, associated with Presentation Layer support for security services in the Application Layer. 1.2 This Recommendation | International Standard defines the following: a) general models of security exchange protocol functions and security transformations, based on the concepts described in the OSI Upper Layers Security Model (ITU-T Rec. X.803 | ISO/IEC 10745); b) a set of notational tools to support the specification of selective field protection requirements in an abstract syntax specification, and to support the specification of security exchanges and security transformations; c) a set of informative guidelines as to the application of the generic upper layers security facilities covered by this series of Recommendations | International Standards. 1.3 This Recommendation | International Standard does not define the following: a) a complete set of upper layer security facilities which may be required by other Recommendations | International Standards; b) a complete set of security facilities for specific applications; c) the mechanisms employed to support security services. 1.4 The security exchange model, and supporting notation, are intended both for use as the basis of defining the security exchange service element in subsequent parts of this series of Recommendations | International Standards, and for use by any other ASE which may import security exchanges into its own specification.

Information technology -- Open Systems Interconnection -- Generic upper layers security: Overview, models and notation

GSO ISO/IEC 7498-3:2013 信息技术 开放系统互连 基本参考模型 术语和标题

This Recommendation | International Standard: a) defines general mechanisms for the use of names and addresses to identify and locate objects in the OSIE; and b) defines the use of these mechanisms within the layered structure of the Basic Reference Model. This Recommendation | International Standard extends the concepts and principles defined in ITU-T Rec. X.200 | ISO/IEC 7498-1. This Recommendation | International Standard is not intended to be either an implementation specification or a basis for appraising the conformance of actual implementations. The specific form of names and addresses is not within the scope of this Recommendation | International Standard.

Information technology -- Open Systems Interconnection -- Basic Reference Model: Naming and addressing

GSO ISO/IEC 9646-3:2013 信息技术 开放系统互连 兼容性测试方法和框架 第3部分：树编号和分类编号

Scope 1.1 This part of ISO/IEC 9646 defines an informal test notation, called the Tree and Tabular Combined Notation (TTCN), for OSI conformance test suites, which is independent of test methods, layers and protocols, and which reflects the abstract testing methodology defined in ISO/IEC 9646-1 and ISO/IEC 9646-2. 1.2 It also specifies requirements and provides guidance for using TTCN in the specification of system-independent conform-ance test suites for one or more OSI standards. It specifies two forms of the notation: one, a human-readable form, applicable to the production of conformance test suite standards for OSI protocols; and the other, a machine-processable form, applicable to processing within and between computer systems. 1.3 This part of ISO/IEC 9646 applies to the specification of conformance test cases which can be expressed abstractly in terms of control and observation of protocol data units and abstract service primitives. Nevertheless, for some protocols, test cases may be needed which cannot be expressed in these terms. The specification of such test cases is outside the scope of this part of ISO/IEC 9646, although those test cases may need to be included in a conformance test suite standard. For example, some static conformance requirements related to an application service may require testing techniques which are specific to that particular application. The specification of test cases in which more than one behaviour description is to be run in parallel is dealt with by the concurrency features (particularly involving the definition of Test Components and Test Component Configurations). 1.4 This part of ISO/IEC 9646 specifies requirements on what a test suite standard may specify about a conforming realization of the test suite, including the operational semantics of TTCN test suites. 1.5 This part of ISO/IEC 9646 applies to the specification of conformance test suites for OSI protocols in OSI layers 2 to 7, specifically including Abstract Syntax Notation One (ASN.1) based protocols. The following are outside the scope of this part of ISO/IEC 9646: a) the specification of conformance test suites for Physical layer protocols; b) the relationship between TTCN and formal description techniques; c) the means of realization of executable test suites (ETS) from abstract test suites. 1.6 This part of ISO/IEC 9646 defines mechanisms for using concurrency in the specification of abstract test cases. Concurrency in TTCN is applicable to the specification of test cases: a) in a multi-party testing context; b) which handle multiplexing and demultiplexing in either a single-party or multi-party testing context; c) which handle splitting and recombining in either a single-party or multi-party testing context; d) in a single-party testing context when the complexity of the protocol or set of protocols handled by the IUT is such that concurrency can simplify the specification of the test case. 1.7 TTCN modules are defined to allow sharing of common TTCN specifications between test suites.

Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 3: The Tree and Tabular Combined Notation (TTCN)

GSO ISO/IEC 9646-6:2013 信息技术 开放系统互连 兼容性测试方法和框架 第6部分：协议测试规范

This part of ISO/IEC 9646 specifies the requirements and provides guidance for the production of Profile Test Specifications (PTSs) for conformance testing of OSI protocol profiles. This part of ISO/IEC 9646 also specifies requirements concerning the expression of conformance requirements in protocol profile specifications. This part of ISO/IEC 9646 is applicable to testing the conformance of a profile implementation to the static and dynamic conformance requirements of each protocol and any information objects included in the profile, by controlling and observing Protocol Data Unit (PDU) exchanges. Testing requirements that go beyond conformance are outside the scope of this part of ISO/IEC 9646.

Information technology -- Open Systems Interconnection -- Conformance testing methodology and framework -- Part 6: Protocol profile test specification

GSO ISO/IEC 14766:2013 信息技术 系统之间的通信和信息交换 通过互联网传输控制协议 (OSI TCP) 使用应用程序

This International Standard defines a mechanism which allows OSI upper layers (all session, presentation, and application entities) to operate over the Internet Transmission Control Protocol (TCP) without being aware that they are running on a TCP/IP internetwork. It provides similar functionality to ISO/IEC Transport Protocol Class 4. It does not provide a gateway facility between Internet and OSI applications.

Information technology -- Telecommunications and information exchange between systems -- Use of OSI applications over the Internet Transmission Control Protocol (TCP)

KS X ISO/IEC 9834-1-2013 信息技术 开放系统互连 OSI注册机构的运作程序：一般程序

Information technology－Open Systems Interconnection－Procedures for the operation of OSI Registration Authorities：General procedures

KS X ISO/IEC 22536-2013(2023) 信息技术系统间电信和信息交换近场通信接口和协议（NFCIP-1）射频接口试验方法

Information technology — Telecommunications and information exchange between systems — Near Field Communication Interface and Protocol (NFCIP-1) — RF interface test methods

KS X ISO/IEC 22536-2013(2018) 信息技术 - 系统之间的电信和信息交换 - 近场通信接口和协议（NFCIP-1） - 射频接口测试方法

Information technology — Telecommunications and information exchange between systems — Near Field Communication Interface and Protocol (NFCIP-1) — RF interface test methods

KS X ISO/IEC 22536:2013 信息技术.电气通信系统间信息交换.近场通信(NFC).接口和协议(NFCIP-1)-RF射频接口试验方法.

이 표준은 KS X ISO/IEC 18092에서 규정한 NFCIP-1을 시험하는 방법을 규정하는 일련의 규격 중의하나이며, RF 인터페이스의 시험방법에 대하여 규정한다. 이 표준은 50 mm×40 mm의 직사각형 영역에 들어가는 안테나를 갖춘 NFC 장치의 RF 인터페이스 시험방법을 규정한다.이 표준은 두 부분 중 처음 것으로, KS X ISO/IEC 18092에 규정하는 장치의 RF 인터페이스에 대한적합성 시험을 규정한다. 다른 표준인 KS X ISO/IEC 23917은 KS X ISO/IEC 18092에 대한 프로토콜시험방법을 규정한다.

Information technology — Telecommunications and information exchange between systems — Near Field Communication Interface and Protocol (NFCIP-1) — RF interface test methods