Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 10021-7-04 / CAN CSA ISO IEC 10021-7-04: Message Handling Systems — Interpersonal Messaging Protocol Analysis
Technical Architecture, Mandatory Compliance Requirements, and Security Mechanisms for the X.400 P2 Protocol
Scope and Evolution of IEC 10021-7-04
The ISO/IEC 10021 series defines the global architecture for enterprise-grade Message Handling Systems (MHS), directly aligned with the ITU-T X.400 series. **Part 7** specifically governs the **Interpersonal Messaging System (IPMS)**. The edition designated as IEC 10021-7-04 (adopted in Canada as **CAN CSA ISO IEC 10021-7-04**) represents the consolidated text from the 2003 version and its pivotal 2004 Amendment. This edition primarily introduced enhanced security services, stricter handling of notification procedures, and better alignment with defence messaging standards.
IEC 10021-7-04 is technically identical to ITU-T X.420. Implementers should always consult both for the latest defect reports and formal interpretation decisions.
The core scope of this standard includes:
- Defining the **Abstract Syntax** for Interpersonal Messages (IPMs) and Interpersonal Notifications (IPNs).
- Specifying the **P2 protocol procedures** for transferring IPMs between User Agents (UAs) over the Message Transfer System (MTS).
- Codifying **Security features** integral to the IPMS heading and body structure.
- Establishing rules for **Message Forwarding**, **Body Part extension**, and **Multi-part Content Types**.
Technical Architecture and Protocol Structure
The P2 protocol is an application layer protocol built on ASN.1 (Abstract Syntax Notation One, defined in ISO/IEC 8824/8825). It relies on the underlying P1 (MTS) or P7 (MS Retrieval) protocols for transport.
IPM Heading Fields
An Interpersonal Message is structured as a Heading followed by a Body. The heading contains the control information and routing semantics familiar to email users but with rigorous formal definitions.
| Field Name | ASN.1 Identifier | Mandate | Description |
|---|---|---|---|
| IPM Identifier | ipmIdentifier | MAND | Globally unique message reference across all MHS domains. |
| Originator | originator | MAND | ORName of the message sender (complete X.400 address). |
| Authorizing Users | authorizingUsers | OPT | Secondary approvers or signatories of the message. |
| Primary Recipients | primaryRecipients | OPT | To: recipients list. |
| Copy Recipients | copyRecipients | OPT | Cc: recipients list. |
| Blind Copy Recipients | blindCopyRecipients | OPT | Bcc: recipients list (strict disclosure rules apply). |
| Subject | subject | OPT | Subject line of the message, typically IAS (IA5) Text. |
| Obsoleted IPMs | obsoletedIPMs | OPT | References to earlier messages that this message supersedes. |
| Expiry Time | expiryTime | OPT | Date/time after which the message is considered invalid. |
| Importance | importance | MAND | Urgency indication (low, normal, high). Defaults to low if not set. |
| Sensitivity | sensitivity | OPT | Organizational security classification. |
| Reply Requestors | replyRequestors | OPT | Explicitly requests a reply from specific parties. |
| Incomplete Copy | incompleteCopy | OPT | Indicates truncation, specifically utilized in Bcc handling mechanisms. |
The handling of Blind Copy Recipients (Bcc) is a critical implementation detail. The standard mandates that the
blindCopyRecipients field must be completely stripped from the heading of copies delivered to primary and copy recipients. The `incompleteCopy` flag signals this truncation.Body Parts and Content Types
The IPMS Body is a sequence of Body Parts. Defined body parts include IA5TextBodyPart (plain text), TeletexBodyPart (formatted text), ForwardedIPMBodyPart (inclusion of an entire IPM), and the versatile ExternalBodyPart (which references content defined by external OIDs or File Transfer Body Parts). The 2004 amendment clarified the use of EncryptedBodyPart and IntegrityCheckBodyPart for secure content delivery.
IPM Notifications (IPNs)
P2 defines a rich set of notifications independent of the MTS delivery notifications (P1). These IPNs travel as regular IPMs but carry specific heading indicators:
- IPMPendingDeliveryNotification: UA is deferring delivery (e.g., auto-forward).
- IPMReceiptNotification: Message has been opened (read receipt).
- IPMNonReceiptNotification: Message was processed but not read (e.g., discarded by auto-action).
- IPMDeliveryNotification: Confirms delivery to the recipient UA (distinct from MTS delivery).
Implementation Strategy and Interoperability
ASN.1 and Encoding Rules
Implementations of IEC 10021-7-04 must handle ASN.1 constructs using BER (Basic Encoding Rules) or DER (Distinguished Encoding Rules) for secure tokens. The P2 protocol is layered over either the P3 (Submission and Delivery) or P7 (Message Retrieval) protocols. The content type for IPMS is universally registered as 0x22C20C.
Boundary Conditions and Extensions
The standard defines specific lower bounds for extensibility. All implementations are required to support at least the following:
| Parameter | Minimum Lower Bound | Notes |
|---|---|---|
| Subject Length | 128 characters | IAS (IA5) / PrintableString encoding. |
| Number of Recipients | 128 per category | To, Cc, Bcc fields must each handle this many. |
| Forwarding Depth | 2 levels | Nested ForwardedIPMBodyPart handling. |
| IA5 Body Part Length | 4,096 octets | Minimum supported body part size. |
| IPN Extensions | 32 concurrent extensions | Extensibility field handling. |
Adoption of the CAN CSA ISO IEC 10021-7-04 version ensures technical compliance with Canadian federal messaging infrastructure (GDMS/SCEME). Implementers using this standard can expect robust interoperability with NATO and allied defence messaging networks.
SMTP/MIME Gatewaying (MIXER)
Interoperability with the broader Internet email network is achieved through RFC 2156 (MIXER – MIME Internet X.400 Enhanced Relay). This protocol maps IPM heading fields to SMTP headers (e.g., IPMIdentifier to Message-ID, ObsoletedIPMs to In-Reply-To/References). Body parts are mapped to MIME content types, though security tokens and Bcc semantics often require careful gateway policy configuration to avoid data leakage.
Compliance, Security, and Validation Considerations
Conformance Testing
Conformance testing against the ISO/IEC 10021-7 Abstract Test Suite (ATS) is a prerequisite for formal certification. The ATS validates the abstract syntax machine, state transitions for notifications, and the handling of mandatory vs. optional fields. A product claiming compliance with IEC 10021-7-04 must pass all mandatory tests regarding IPM construction, IPN generation, and extension field processing.
Failing to register or negotiate the correct IPMS Content Type (0x22C20C) in the MTS transfer envelope will cause strict MTAs to reject all P2 messages outright. Ensure the MTS binding (P3/P7) explicitly supports this content type.
Security Considerations
The 2004 amendment formalized several security enhancements. Specific focus is placed on:
- Message Token: The
messageTokenfield in the heading carries message level origin authentication and integrity checks. - Content Confidentiality: Used in conjunction with MHS Security Services (ISO/IEC 10021-4) to support encrypted body parts.
- Proof of Delivery / Submission: The integration of P2 notifications with P1 proof mechanisms creates a robust non-repudiation framework.
- Security Labels: The
Sensitivityfield in the heading conveys the organizational security policy (Unclassified, Confidential, Secret) within the P2 protocol boundary.
Implementers should ensure that cryptographic modules handling the messageToken meet relevant national security standards (e.g., FIPS 140-2 for US/Canada, or national equivalents for secure military messaging).
Frequently Asked Questions
Q: What is the relationship between IEC 10021-7-04 and ITU-T X.420?
A: They are identical twin texts. IEC 10021-7-04 is the ISO version of the ITU-T Recommendation X.420. The Canadian adoption, CAN CSA ISO IEC 10021-7-04, mirrors the ISO text exactly for regulatory use and standardization within Canada.
A: They are identical twin texts. IEC 10021-7-04 is the ISO version of the ITU-T Recommendation X.420. The Canadian adoption, CAN CSA ISO IEC 10021-7-04, mirrors the ISO text exactly for regulatory use and standardization within Canada.
Q: Can IEC 10021-7-04 (X.400 P2) interoperate with modern SMTP email?
A: Yes, through gateways implementing RFC 2156 (MIXER). This maps the P2 IPM heading fields (Originator, Primary Recipients, Subject) to SMTP headers (From, To, Subject). Not all IPM features translate cleanly, particularly message tokens and complex Bcc handling, which may require policy-based gateways.
A: Yes, through gateways implementing RFC 2156 (MIXER). This maps the P2 IPM heading fields (Originator, Primary Recipients, Subject) to SMTP headers (From, To, Subject). Not all IPM features translate cleanly, particularly message tokens and complex Bcc handling, which may require policy-based gateways.
Q: What are the key security enhancements in the 2004 amendment (version 04)?
A: The 2004 amendment clarified the use of message tokens for secure message labeling, provided rigorous formal definitions for encrypted body parts and integrity checks, and enhanced the integration of the Message Security Protocol (MSP) elements into the P2 heading. It provides a comprehensive framework for non-repudiation of origin and submission.
A: The 2004 amendment clarified the use of message tokens for secure message labeling, provided rigorous formal definitions for encrypted body parts and integrity checks, and enhanced the integration of the Message Security Protocol (MSP) elements into the P2 heading. It provides a comprehensive framework for non-repudiation of origin and submission.
Q: Is implementing the P2 protocol without the full MTS (P1) stack feasible?
A: Technically, P2 assumes the P1 delivery infrastructure. However, in closed networks or specific DMS (Defence Message System) implementations, P2 can run directly over a reliable transport layer. For full conformance to CAN CSA ISO IEC 10021-7-04, the complete MHS stack (P1, P3, P7) must be supported for the full message lifecycle.
A: Technically, P2 assumes the P1 delivery infrastructure. However, in closed networks or specific DMS (Defence Message System) implementations, P2 can run directly over a reliable transport layer. For full conformance to CAN CSA ISO IEC 10021-7-04, the complete MHS stack (P1, P3, P7) must be supported for the full message lifecycle.
Published: 2026