Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
CAN CSA ISO IEC ISP 12062-4-04: A Technical Guide to the IPM-MTS Access Gateway Profile
Scope, Technical Requirements, and Compliance for the Canadian Adoption of ISO/IEC ISP 12062-4
CAN CSA ISO IEC ISP 12062-4-04 is the Canadian adoption of ISO/IEC ISP 12062-4, a key component of the International Standardized Profile (ISP) series for Message Handling Systems (MHS). This standard specifies the AMH24 profile, which defines the functionality and protocol requirements for an Interpersonal Messaging (IPM) — Message Transfer System (MTS) Access Gateway. As part of the broader X.400-based messaging infrastructure, this profile enables IPM user agents to submit and receive messages via the MTS while maintaining interoperability across different implementations.
Scope of the Standard
CAN CSA ISO IEC ISP 12062-4-04 addresses the gateway between the IPM service and the MTS access service. Specifically, it defines the behavior, protocol stack, and conformance requirements for the IPM-MTS Access Gateway, which translates between IPM user agent input/output and MTS submission/delivery primitives. The scope includes:
- Protocol mappings between IPM service elements (e.g., IA5 body parts, forwarded messages, receipt notifications) and MTS primitives (e.g.,
mts-submit,mts-deliver,mts-probe). - Use of the P3 (Submission and Delivery) and P7 (Remote User Agent Access) protocols as defined in the ITU-T X.400 series.
- Support for optional MTS features such as delivery reports, security labels, and content type negotiation.
- Interworking with directory services (X.500) for name resolution and address translation.
- Conformance testing and certification requirements for implementations seeking CSA compliance.
Tip: When implementing the gateway, ensure that both P3 and P7 protocol implementations align with the mandatory profiles listed in the ISO/IEC ISP 12062 series. Particular attention should be paid to the AMH22 and AMH23 profiles, as they specify underlying MTS access and IPM service requirements.
Technical Requirements
Protocol Stack and Gateway Architecture
The gateway defined in CAN CSA ISO IEC ISP 12062-4-04 must implement the following protocol stack:
- Application Layer: X.400 Message Handling System (MHS), with specific support for the IPM user agent (X.420) and Message Transfer Agent (X.411) services.
- Presentation Layer: ASN.1 encoding as per X.409 and X.208.
- Session Layer: OSI Session layer (X.225) with support for session synchronization and resynchronization.
- Transport: OSI Transport layer (X.224) or TCP/IP convergence as specified in the ISP profiles.
The gateway acts as a relay between the IPM realm (using P7 for user agent access) and the MTS realm (using P3 for message submission and delivery). It must maintain state across sessions and correctly map service elements as specified in the profile.
Mapping of IPM Service Elements to MTS Primitives
The core technical challenge addressed by this standard is the accurate mapping between IPM-specific constructs and the generic MTS operations. The following table summarizes the mandatory mappings defined in the profile:
| IPM Service Element | MTS Primitive | Protocol Reference |
|---|---|---|
| Original IPM (IA5 or G3 fax body parts) | mts-submit | X.411 § 9.2 |
| Forwarded IPM | mts-submit (with content type indication) | X.420 Annex C |
| Delivery Notification (IPM delivery report) | mts-deliver | X.411 § 9.3 |
| Receipt Notification (IPN) | mts-submit (as IPM return-content) | X.420 § 15 |
| Probe (to check deliverability) | mts-probe | X.411 § 9.4 |
Quality of Service (QoS) and Security
The profile requires the gateway to support the following QoS parameters:
- Priority: Submission with normal, urgent, or non-urgent markers, mapped to the MTS priority field.
- Delivery confirmation: Request for notification types (non-delivery, delivery, or both).
- Security labels: Support for content integrity, message origin authentication, and security classification as per X.411 security extensions.
Warning: The CAN CSA adoption includes a Canadian National Deviation that requires the gateway to support enhanced security label granularity for government messaging. Implementers must verify that their security policy configuration meets the additional requirements detailed in Annex A of the standard.
Directory Integration
To resolve IPM names (e.g., givenname.surname@domain) into MTS O/R addresses, the gateway must integrate with an X.500 directory service. The standard mandates support for the Directory User Agent (DUA) interface defined in ISO/IEC ISP 12062-5 (AMH25). Directory lookups are used for:
- Mapping IPM user identifiers to MTS originator/recipient attributes.
- Retrieving required security certificates.
- Resolving distribution lists defined within the directory.
Implementation Highlights
Implementing CAN CSA ISO IEC ISP 12062-4-04 requires careful attention to protocol conformance and interworking. The following highlights are derived from the profile’s requirements and industry best practices.
Gateway Configuration and Operation
Deploying the IPM-MTS Access Gateway involves configuring the following components:
- P3 Transport Layer: The gateway must establish and manage associations with an MTS (e.g., a Message Transfer Agent) using the P3 protocol over either OSI Session or RFC 1006. Successful binding requires authentication credentials that match the MTS’s security policy.
- P7 Server Interface: The gateway exposes a P7 remote user agent interface for IPM clients. This interface should support both synchronous and asynchronous notification modes as defined in the profile.
- Content Conversion: While the profile does not mandate conversion services, the gateway should gracefully handle unsupported body part types by either returning an appropriate error or applying a conversion that is transparent to the user.
- Logging and Auditing: The Canadian deviation may require detailed logging of each submission and delivery event for compliance with national security regulations.
Conformance Testing
Testing a gateway against CAN CSA ISO IEC ISP 12062-4-04 involves verifying both static and dynamic conformance:
- Static Conformance: Check that the implementation supports the mandatory elements (e.g., all prescribed protocol versions, mandatory body part types, and mandatory MTS primitive mappings). Any claimed options must be listed in the Implementation Conformance Statement (ICS).
- Dynamic Conformance: Use a test harness that simulates IPM clients and MTS peers to verify correct behavior for both normal and error scenarios. The standard references the abstract test suites from the ISO/IEC 9646 series for OSI conformance testing.
Non‑compliance Risk: Gateways that fail to implement the mandatory mapping for receipt notifications (IPN) will not pass conformance certification in Canada. This requirement is often overlooked by products originally designed for regional markets that do not enforce receipt handling.
Compliance and Certification
Organizations deploying a gateway that claims conformance to CAN CSA ISO IEC ISP 12062-4-04 should be aware of the compliance framework:
- Certification Body: The Canadian Standards Association (CSA) oversees certification of MHS products under the CSA ISO/IEC ISP 12062 Series scheme.
- Relationship to ISO/IEC ISP 12062-4 (2003): The Canadian adoption introduces national deviations (defined in an Annex) that must be met for compliance within Canada. These deviations primarily affect security label handling and optional support for certain content types.
- Interoperability Testing: CSA recommends participating in multi-vendor interoperability events (e.g., those organized by the X.400 Interoperability Forum) to validate gateway behavior across different implementations.
- Maintenance and Updates: The standard is maintained by the CSA Technical Committee on Information Technology. Revisions may incorporate amendments from ISO/IEC JTC 1/SC 6.
Success: Adhering to CAN CSA ISO IEC ISP 12062-4-04 streamlines the procurement and deployment of MHS components in Canadian government and enterprise networks. Products that carry CSA certification mark meet the high reliability and security requirements expected in the national messaging infrastructure.
Frequently Asked Questions
Q: What is the relationship between CAN CSA ISO IEC ISP 12062-4-04 and the ITU-T X.400 standards?
A: CAN CSA ISO IEC ISP 12062-4-04 is a profile (implementation specification) that selects and constrains features from the X.400 series (specifically X.411, X.420, X.225, etc.) to define an interoperable IPM-MTS access gateway. It does not replace X.400; rather, it specifies which options must be used to achieve consistent behavior across different vendors’ products in a Canadian context.
A: CAN CSA ISO IEC ISP 12062-4-04 is a profile (implementation specification) that selects and constrains features from the X.400 series (specifically X.411, X.420, X.225, etc.) to define an interoperable IPM-MTS access gateway. It does not replace X.400; rather, it specifies which options must be used to achieve consistent behavior across different vendors’ products in a Canadian context.
Q: How does the Canadian adoption differ from the base ISO/IEC ISP 12062-4:2003?
A: The main differences are documented in the national deviation annex. For Canada, the standard mandates additional security label granularity for government messaging, requires support for a specific form of receipt notification, and introduces stricter performance requirements for directory lookups during address resolution.
A: The main differences are documented in the national deviation annex. For Canada, the standard mandates additional security label granularity for government messaging, requires support for a specific form of receipt notification, and introduces stricter performance requirements for directory lookups during address resolution.
Q: Is conformance to CAN CSA ISO IEC ISP 12062-4-04 mandatory for Canadian federal agencies?
A: While it is not mandatory by law, most Canadian federal networks require MHS gateways to be certified against this standard as part of their security and interoperability policies. Certification is often a precondition for procurement of messaging infrastructure.
A: While it is not mandatory by law, most Canadian federal networks require MHS gateways to be certified against this standard as part of their security and interoperability policies. Certification is often a precondition for procurement of messaging infrastructure.
Q: What testing tools are available for verifying a gateway implementation?
A: CSA provides a conformance testing service that uses a reference implementation of both an IPM User Agent and an MTS. Industry tools such as the MHS Conformance Tester (MCT) and X.400 Profile Verifier are also available. For dynamic testing, tools based on the TTCN language (ISO/IEC 9646) are recommended.
A: CSA provides a conformance testing service that uses a reference implementation of both an IPM User Agent and an MTS. Industry tools such as the MHS Conformance Tester (MCT) and X.400 Profile Verifier are also available. For dynamic testing, tools based on the TTCN language (ISO/IEC 9646) are recommended.