Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Understanding CAN/CSA-ISO/IEC-ISP 12062-1-04: OSI Transport Service Over Connectionless Network Service Profiles
Technical Overview of the Canadian Adoption of ISO/IEC International Standardized Profile for Subnetwork-Independent Transport Requirements
Introduction and Scope
CAN/CSA-ISO/IEC-ISP 12062-1-04 is the Canadian adoption (by the CSA Group) of ISO/IEC ISP 12062-1, part of the OSI International Standardized Profile (ISP) family. This standard specifies the subnetwork-independent requirements for the support of the OSI Transport Service (TS) using the Connectionless Network Service (CLNS). It is the foundational document for a series of profiles that define interoperable implementations of the Transport Protocol Class 4 (TP4) over CLNP, independent of the underlying subnetwork technology. The standard applies to end systems and intermediate systems that wish to offer a reliable transport service over connectionless network infrastructures such as IP or native OSI CLNS networks.
Originally published by ISO/IEC as ISP 12062-1:2003, the Canadian adoption carries the designation CAN/CSA-ISO/IEC-ISP 12062-1-04, reflecting its endorsement by the Standards Council of Canada. This profile is essential for organizations deploying OSI-based networking in government, defense, or industrial settings where international interoperability is mandatory.
Note: This standard is a key building block for OSI transport profiles and is referenced by many procurement specifications requiring conformance to the OSI stack.
Technical Architecture and Profile Structure
Protocol Stack
The profile defines a precise stack of OSI protocols to ensure consistent transport service delivery. The mandatory protocols include:
- Network Layer: ISO/IEC 8473 (CLNP) for connectionless network service
- Transport Layer: ISO/IEC 8073 (TP4) operating in class 4 (error recovery and flow control)
- Session and Presentation Layers: Implementations may use ISO/IEC 8327 and ISO/IEC 8823, respectively, if needed
The profile does not mandate specific subnetwork technologies but defines the interface requirements between the network and subnetwork layers.
Profile Identification
ISP 12062-1 introduces a naming scheme for the transport profiles. The common prefix is “A/” followed by modifiers indicating subnetwork type. Part 1 covers subnetwork-independent requirements common to all A‑profile variants.
| Profile Designation | Transport Protocol | Network Service | Subnetwork Dependency |
|---|---|---|---|
| A/1111 | TP4 | CLNS | Independent (base profile) |
| A/1211 | TP4 | CLNS over X.25 | X.25 Packet Layer |
| A/1221 | TP4 | CLNS over LAN | MAC (e.g., CSMA/CD) |
The subnetwork-independent part (Part 1) defines the common elements that all these profiles must fulfill, such as addressing architecture, quality of service parameters, and timer values.
Tip: When designing systems, always refer to CAN/CSA-ISO/IEC-ISP 12062-1-04 for the generic transport/network interface before selecting the appropriate subnetwork profile (e.g., ISP 12062-3 for LAN).
Implementation Highlights
Key Technical Requirements
Implementers must satisfy the following core requirements specified in the standard:
- Transport Service Mapping: The profile defines how Transport Service primitives (T-Connect, T-Data, T-Disconnect, etc.) are mapped onto Network Service primitives (N-Connect, N-Data, N-Disconnect) for connectionless mode.
- Quality of Service (QoS) Negotiation: Mechanisms for selecting and downgrading QoS parameters after the T-Connect request are mandatory, with specific values for throughput, transit delay, and residual error rate.
- Addressing: NSAP (Network Service Access Point) addresses must conform to ISO/IEC 8348. The profile requires support for both global and local NSAP formats.
- Timer and Parameter Values: Specific values for transport protocol timers (e.g., retransmission time, inactivity time, etc.) are mandated to ensure interoperability. Deviations are allowed only if documented in the PICS.
Warning: The 2004 version supersedes the 1998 edition. Implementations based on the earlier version may not interoperate correctly without careful review of changes in timer and QoS parameter ranges.
Conformance Requirements
All implementations claiming conformance to CAN/CSA-ISO/IEC-ISP 12062-1-04 must provide a Protocol Implementation Conformance Statement (PICS) proforma as defined in Annex A of the standard. The PICS documents which options are supported and any limitations. Conformance testing typically involves verification of the transport protocol behavior over CLNP using abstract test suites referenced in the standard.
Important: This profile is optimized for reliable data transport over networks that may lose, duplicate, or reorder packets. It is not designed for real-time multimedia or low-latency applications. Using it for such purposes may lead to unacceptable performance.
Success Criterion: A system that fully implements the mandatory features of this standard and correctly fills the PICS will achieve interoperability with any other conformance system operating the same profile (e.g., A/1111).
Compliance and Conformance: Key Considerations
Related Standards
Compliance cannot be achieved without addressing the following related documents:
- ISO/IEC 8473-1 (CLNP)
- ISO/IEC 8073 (Transport Protocol)
- ISO/IEC ISP 12062 parts 2, 3, and 4 (subnetwork-specific requirements)
- PICS proforma: ISO/IEC ISP 12062-1/Amd1
Testing and Certification
Organizations seeking CSA certification or mutual recognition should contact accredited testing laboratories that offer conformance testing for OSI profiles. The standard specifies abstract test cases but does not provide executable scripts; vendors must develop or acquire suitable test tools. For Canadian accreditation, CSA Group may require evidence of testing against both the national adoption and the underlying ISO/IEC part.
Frequently Asked Questions
Q: What is the difference between CAN/CSA-ISO/IEC-ISP 12062-1-04 and the original ISO/IEC ISP 12062-1:2003?
A: The Canadian adoption is technically identical to the ISO/IEC version. The “04” in the designation indicates the year of adoption by CSA Group (2004). Some editorial changes (such as bilingual notes) may be present, but the technical content remains unchanged. For regulatory purposes, this adoption carries the weight of a National Standard of Canada.
A: The Canadian adoption is technically identical to the ISO/IEC version. The “04” in the designation indicates the year of adoption by CSA Group (2004). Some editorial changes (such as bilingual notes) may be present, but the technical content remains unchanged. For regulatory purposes, this adoption carries the weight of a National Standard of Canada.
Q: Can I use this profile over an IP network instead of CLNP?
A: No, this profile specifically relies on ISO/IEC 8473 (CLNP) as the network layer protocol. For use over IP, the appropriate ISP is ISO/IEC ISP 12062-5 (or its Canadian adoption) which specifies the mapping of TP4 over IP. However, this part (Part 1) still provides the transport service interface definitions that apply across all subnetwork types, including IP.
A: No, this profile specifically relies on ISO/IEC 8473 (CLNP) as the network layer protocol. For use over IP, the appropriate ISP is ISO/IEC ISP 12062-5 (or its Canadian adoption) which specifies the mapping of TP4 over IP. However, this part (Part 1) still provides the transport service interface definitions that apply across all subnetwork types, including IP.
Q: Do I need to implement all options listed in the PICS to claim conformance?
A: No, the PICS allows selection of supported features. However, the mandatory core elements (such as TP4 class 4 with full error recovery and default timer values) must always be present. Optional items may be omitted provided the PICS clearly states the omission. The important requirement is that the implementation’s behavior matches the profile’s specification for the selected options.
A: No, the PICS allows selection of supported features. However, the mandatory core elements (such as TP4 class 4 with full error recovery and default timer values) must always be present. Optional items may be omitted provided the PICS clearly states the omission. The important requirement is that the implementation’s behavior matches the profile’s specification for the selected options.
Q: Where can I obtain a copy of this standard for technical review?
A: The official version is available from the CSA Group online store (shop.csa.group) or through the ISO/IEC national member bodies. Technical committees may access earlier drafts or amendment documents through the Canadian mirror committee (SCC/ISO/IEC JTC 1/SC 6).
A: The official version is available from the CSA Group online store (shop.csa.group) or through the ISO/IEC national member bodies. Technical committees may access earlier drafts or amendment documents through the Canadian mirror committee (SCC/ISO/IEC JTC 1/SC 6).
— Published: 2026 —