Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Understanding CAN CSA ISO IEC ISP 10611-3-04: A Guide to the OSI Distributed Transaction Processing Profile
The Canadian adoption of the ISO/IEC International Standardized Profile for OSI TP Support
International Standardized Profiles (ISPs) provide a framework for implementing complex OSI services in a consistent and interoperable manner. The Canadian standard CAN CSA ISO IEC ISP 10611-3-04 represents the national adoption of the ISO/IEC ISP 10611-3 profile, which specifies the support of OSI Distributed Transaction Processing (OSI TP) services. This article offers a concise technical overview of the standard, covering its scope, key technical requirements, implementation considerations, and compliance pathways.
Scope of CAN CSA ISO IEC ISP 10611-3-04
This standard defines an International Standardized Profile for the OSI TP application service element. It specifies the combination of base OSI standards required to support the transaction processing model defined in ISO/IEC 10026 (OSI TP) and related International Standards. The profile addresses the communication requirements of applications that need distributed transaction coordination, including the ACID properties (atomicity, consistency, isolation, durability).
Specifically, CAN CSA ISO IEC ISP 10611-3-04 covers:
- The required OSI layers and protocol subsets that must be present.
- The TP service provider behavior, including transaction demarcation, recovery, and commitment.
- Conformance requirements for systems claiming to implement this profile.
The profile is intended for use by implementers, procurers, and testers of OSI TP systems that need to ensure a minimum level of interoperability.
Technical Requirements
Mandated OSI Layers and Protocols
The profile mandates specific options and parameters from the underlying OSI layers to guarantee consistent behavior. The following table summarises the required protocol combinations:
| Layer | Required Protocol | Constrained Options |
|---|---|---|
| Application | ISO/IEC 10026 (OSI TP) – TP Service Provider (TP-P) and User (TP-U) | Use of TP Dialogue Service; mandatory support of two-phase commit (2PC) and transaction recovery |
| Presentation | ISO/IEC 8823 (X.226) – Connection-mode Presentation Service | Support of functional units for transfer syntax negotiation |
| Session | ISO/IEC 8327 (X.225) – Connection-mode Session Service | Mandatory use of Session Version 2; support for symmetric and asymmetric synchronization |
| Transport | ISO/IEC 8073 (X.224) – Transport Protocol Class 4 (TP4) | Full error recovery; connection establishment with mandatory TPDU size negotiation |
| Network | ISO/IEC 8473 (X.233) – Connectionless Network Protocol or ISO/IEC 8208 (X.25) for connection-oriented | As per profile selection; quality of service parameters defined |
Transaction Processing Requirements
CAN CSA ISO IEC ISP 10611-3-04 imposes strict rules on the TP protocol machine:
- Transaction IDs – Each transaction must be uniquely identified using a globally unique identifier (TP-Transaction-ID).
- Commitment Protocol – The two-phase commit (2PC) protocol is mandatory, with a defined timeout and recovery procedure for heuristic decisions.
- Recovery – Systems must support the OSI TP recovery dialogue to handle crashes and reconnections.
Tip: When implementing the 2PC protocol, pay close attention to the transaction state machine defined in ISO/IEC 10026-3. The profile uses the same state tables and guarantees that all implementations follow identical commit logic.
Implementation Highlights
Developers integrating CAN CSA ISO IEC ISP 10611-3-04 into a product should note the following:
- Interoperability – The profile restricts many options present in the base standards, thereby reducing negotiation complexity and increasing the likelihood of successful interworking between different vendors.
- Mapping to ASN.1 – All TP APDUs are encoded using ASN.1 as specified in the standard. The profile does not permit alternative transfer syntaxes.
- Performance – Because the profile mandates TP4 (Transport Class 4) for reliable data transfer, implementers can choose appropriate window sizes and TPDU sizes to optimise throughput within the allowed parameters.
- Testing – Conformance testing must be done against the abstract test suites referenced in the profile, typically listed in the ISO/IEC 10165 series for TP testing.
Warning: Implementations that deviate from the allowed protocol alternatives may claim conformance to the underlying base standards but will not be compliant with the profile. Profile conformance is evaluated solely against the options listed in the profile definition.
Compliance Notes
Organisations claiming compliance with CAN CSA ISO IEC ISP 10611-3-04 must:
- Provide a system conformance statement (PICS – Protocol Implementation Conformance Statement) that documents which static and dynamic conformance requirements are met.
- Pass all mandatory tests as defined in the associated conformance test specification (typically based on ISO/IEC 10165-5 for OSI TP).
- Ensure that all layers (Application through Network) adhere to the constrained options listed in the profile.
In Canada, certification is administered by the Standards Council of Canada (SCC) in cooperation with accredited testing laboratories. The profile is identical to the international version ISO/IEC ISP 10611-3:2004, meaning that international conformance is automatically recognised as national conformance.
Successful integration – By following this profile, system integrators can build distributed transaction middleware that seamlessly interoperates with other OSI TP‑compliant systems, both domestically and internationally.
Frequently Asked Questions
Q: How does CAN CSA ISO IEC ISP 10611-3-04 relate to the base ISO/IEC 10026 standard?
A: ISO/IEC 10026 defines the OSI Transaction Processing service and protocol. The ISP (profile) selects a specific combination of options from that standard (and other OSI layers) to guarantee interoperability. Therefore, the profile is a subset of the base standard.
A: ISO/IEC 10026 defines the OSI Transaction Processing service and protocol. The ISP (profile) selects a specific combination of options from that standard (and other OSI layers) to guarantee interoperability. Therefore, the profile is a subset of the base standard.
Q: Is there a difference between the Canadian adoption and the original ISO/IEC ISP 10611-3:2004?
A: No technical difference. The Canadian standard is an identical adoption (by CSA), meaning the text is the same and conformance to one implies conformance to the other.
A: No technical difference. The Canadian standard is an identical adoption (by CSA), meaning the text is the same and conformance to one implies conformance to the other.
Q: What testing tools are recommended for verifying compliance?
A: Abstract test suites based on ISO/IEC 10165 (TTCN) are referenced in the profile. Several commercial test tools exist, such as those from Spirent or EXFO, that can run the required OSI TP conformance tests.
A: Abstract test suites based on ISO/IEC 10165 (TTCN) are referenced in the profile. Several commercial test tools exist, such as those from Spirent or EXFO, that can run the required OSI TP conformance tests.
Q: Is this profile still relevant in modern distributed systems?
A: While many new transaction systems use protocols like WS-AtomicTransaction or XA, OSI TP is still deployed in legacy environments and telecommunication networks (e.g., IN, GSM‑MAP). The profile remains a reference for strict transaction semantics and deterministic recovery.
A: While many new transaction systems use protocols like WS-AtomicTransaction or XA, OSI TP is still deployed in legacy environments and telecommunication networks (e.g., IN, GSM‑MAP). The profile remains a reference for strict transaction semantics and deterministic recovery.
— Article prepared in 2026 —