CAN/CSA-ISO/IEC ISP 12062-2-04: Technical Overview of OSI Transport Service Profiles

The standard CAN/CSA-ISO/IEC ISP 12062-2-04 is the Canadian adoption of the international standard ISO/IEC ISP 12062-2:2004, titled “Information technology — International Standardized Profiles — OSI Transport Layers over Connection-mode Network Service — Part 2: Transport Service Definition.” This document is part of a family of International Standardized Profiles (ISPs) that specify interoperable implementations of the OSI transport layer in Wide Area Network (WAN) environments. It provides the definitive reference for the OSI connection-mode transport service as used by profiles A, B, and C, and ensures consistent behaviour across heterogeneous systems.

The standard aligns with the core OSI service definitions (ISO/IEC 8072) and protocol specifications (ISO/IEC 8073), refining them into a concrete, testable profile. Its adoption by the Standards Council of Canada under the CAN/CSA number ensures that Canadian implementations meet globally recognized interoperability criteria.

Scope

CAN/CSA-ISO/IEC ISP 12062-2-04 specifies the OSI connection-mode transport service as it is applied within the ISP framework for WAN environments. The scope encompasses:

• The definition of transport service primitives (T-CONNECT, T-DATA, T-EXPEDITED-DATA, T-DISCONNECT) and their associated parameters.
• The mapping of transport service elements onto the underlying network service (connection-mode, as defined in ISO/IEC 8348).
• Constraints on transport protocol classes and options that are permissible for profiles covered by the ISP 12062 series.
• Quality of Service (QoS) parameters and their negotiation during connection establishment.

This part is intended for implementers of OSI transport layers, particularly those targeting interworking over X.25, ISDN, or other connection-mode network technologies. It does not define new services, but rather selects and constrains existing standards to guarantee interoperability.

Technical Requirements

Transport Service Definition

The transport service is defined in terms of abstract primitives that represent interactions between the transport service user (session layer) and the transport service provider. The mandatory primitives and their direction are listed in the table below, as derived from ISO/IEC 8072 and constrained by this ISP.

Note: User Data in T-CONNECT and T-DISCONNECT is limited to 32 octets in this profile; implementations must adhere to this limit.

Protocol Classes and Profile Constraints

The ISP 12062 series applies to three major network environments (A, B, C) which differ in network service quality. For each environment, the permissible transport protocol classes (per ISO/IEC 8073) are constrained as follows:

• Profile A: Network service with minimal residual errors → Class 0 (simple class) or Class 2 (multiplexing class) may be used.
• Profile B: Network service with moderate error rates → Class 1 (basic error recovery class) or Class 3 (error recovery and multiplexing).
• Profile C: Network service with high error rates/unreliable service → Class 4 (detection and recovery class) is mandatory.

This part of the ISP defines the transport service interface common to all profiles; specific protocol selection and parameter values are provided in subsequent parts (ISP 12062-3, ISP 12062-4).

Implementation Highlights

Interoperability Criteria

The primary goal of CAN/CSA-ISO/IEC ISP 12062-2-04 is to ensure that two independently developed transport entities can communicate correctly when both claim conformance to the same profile. Key implementation considerations include:

• Addressing: Transport Service Access Point (TSAP) addresses must be structured according to ISO/IEC 8348 Annex A. The profile mandates that called and calling address parameters be present in T-CONNECT primitives and be globally unambiguous.
• Quality of Service: Throughput, transit delay, and residual error rate are negotiated within the constraints defined by the profile. Implementations must support at least the minimum QoS classes listed in the standard’s Tables 2–4.
• Segmentation and Reassembly: When the transport protocol data unit size exceeds the network service data unit size, segmentation is performed automatically by the transport protocol. The maximum TPDU size is negotiated during connection establishment; the profile requires support for at least 128 octets, with 2048 octets recommended.

Network Service Dependencies

The profile assumes a connection-mode network service conforming to ISO/IEC 8348. It does not specify how the network service is realized (X.25, ISDN, etc.), but it does prescribe the mapping of transport primitives onto network service primitives (N-CONNECT, N-DATA, N-DISCONNECT). For example, a T-CONNECT.request triggers an N-CONNECT.request to the remote system; the transport service user is unaware of the underlying network complexity.

Compliance Notes

Conformance Requirements

A system claiming conformance to CAN/CSA-ISO/IEC ISP 12062-2-04 must satisfy the following:

• Support all mandatory transport service primitives exactly as specified in Clause 8 of the standard.
• Implement the correct protocol class(es) for the claimed profile (A, B, or C) as detailed in the profile taxonomy.
• Adhere to the parameter value ranges (e.g., maximum user data lengths, QoS parameter limits) defined in the normative annexes.
• Include a static conformance statement (PICS) conforming to ISO/IEC 9646-1 that documents all implemented options and limitations.

Certification and Testing

While conformance to an ISP is not mandatory in many jurisdictions, the CAN/CSA adoption implies that products intended for Canadian government or enterprise procurement may require third-party testing. Test methods follow the ISO/IEC 9646 series (OSI conformance testing methodology). Key test purposes for this profile include:

• Successful connection establishment with minimal QoS negotiation.
• Rejection of illegal primitive sequences (e.g., T-DATA without active connection).
• Correct handling of expedited data flow (if claimed).
• Graceful disconnection from either side.

Frequently Asked Questions

Article reviewed and updated: 2026. This content is for informational purposes and does not substitute the official standard text. Always refer to the published standard for conformance requirements.