|
M-Switch X.400 is a high performance, highly flexible and robust X.400 Message Transfer Agent (MTA). M-Switch X.400 includes two full featured and conformant X.400 protocol implementations:
This page gives a brief overview of X.400 conformance, and sets out the conformance of M-Switch X.400. The X.400 Standards and ISPsThe base X.400 standards and ISPs (International Standard Profiles) are set by two bodies.
The ITU and ISO documents are technically aligned. There are some small differences because the ITU documents relate only to interconnection with public services, whereas the ISO/IEC documents also cover "local" issues. Isode supports these differences, which relate to different deployment situations, and do not affect interoperability. The ISO documents generally have later publication dates, which vary between different documents in the series series and can be as much as five years later than the equivalent ITU numbers. The ITU documents have more consistent dating, which more clearly reflects when the specifications were developed. This difference reflects the different publication procedures of the organizations. Because of this, the dates referred to here are the ITU dates. The following versions of X.400 have been issued.
X.400 specifies a number of components, including MTA, Message Store and User Agent. X.400(88) is the most important specification for a modern X.400 system. The MTA related updates since this specification are relatively minor. Optionality and ExtensibilityX.400 contains many optional elements. Some of these elements are only applicable to certain special situations and types of configuration (e.g., the mappings from X.400 to paper postal service). Conformance needs to be viewed in the context of the elements that are actually needed, rather than a simple implementation of all features. An important change in X.400(1988) was the addition of a series of extensibility mechanisms for various parts of the protocol. This means that most changes to X.400 subsequent to the 1988 version have been introduced in a manner which is compatible with X.400(1988) implementations, in that an implementation can be aware of an extension it does not support and whether or not support of the extension is critical. Functional Groups and ISPsIn order to deal with specification of an X.400 system, there are a series of ISPs (International Standard Profiles) published in conjunction with the base X.400 specifications. "ISO/IEC 10611-1: Common Messaging Part 1: MHS Service Support (1999)" sets out a core framework for the X.400 ISPs. In particular it defines a set of functional groups, to which an implementation can claim conformance. For each functional group, there is a list of mandatory features (which may be optional in the base standard) and a list of optional features. Each of the ISPs is structures as a PICS (Protocol Implementation Conformance Statement) proforma. The PICS Proforma can be completed for a specific implementation to form a PICS for that implementation. The PICS is a key document that specifies which features are implemented. To claim conformance for a functional group, all of the mandatory features for that functional group must be implemented. X.400 Functional Groups in M-Switch X.400This section lists all of the X.400 functional groups, and which ones are supported by M-Switch X.400.
Message Transfer ConformanceAn MTA must support Message Transfer, using the X.400 P1 protocol. M-Switch is conformant to the core ISP requirements for the 1984, 1988, and 1996, 1999 and 2003 versions of X.400. Detailed specification of the Message Transfer Conformance of M-Switch X.400 is provided in two PICS statements:
Message Access ConformanceMessage Access refers to submission and delivery using the X.400 P3 protocol. There are two versions of the X.400 P3 protocol:
Extensions from X.400(1994) and X.400(1999) can be used with both of these protocols. Isode supports P3(1988) only. Details of M-Switch X.400 P3 conformance is defined in "AMH12 and AMH14 - MTS Access (P3) and MTS 94 Access (P3)" ISO/IEC ISP 10611-4. This is aligned to ITU X.483 "P3 PICS". Isode is conformant to the mandatory elements of the ISP for P3(1988), with two exceptions:
Lower Layers: X.400 and RTSEThe X.400 channels support the 1984, 1988 and 1992 recommendations including the mts-transfer (P1-1988, RTSE normal-mode), mts-transfer-protocol (P1-1988, RTSE X.410(1984)-mode) and mts-transfer-protocol-1984 (P1-1984, RTSE X.410(1984)-mode) application contexts. Full RTSE recovery is supported for both inbound and outbound transfers. There is full support for Two Way Alternate. All three application contexts can be supported by a receiving channel on a single Session address. Lower Layers: TransportX.400 is usually operated over TCP/IP using ITOT (ISO Transport over TCP). Full details on ISO Transport support, including options for working to ISO TP4 (Transport Protocol Class 4) or over X.25 are given in ISO Transport Protocols. X.400 Base Standards
Other Conformance
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Copyright © 2008 Isode | privacy feedback
|