We've been working on a number of enhancements to EMMA for R11.2. One of these is described here.
M-Switch X.400 has flexible control of both X.400 content, and body part types within messages. Channels can be set up so that only supported content and body parts are transferred.
The X.400 protocols have built in definitions for a number of content types and body parts with integer values. EMMA has built in support for these, using convenient string representations (for example to conjure the X.435 (Pedi) protocol). They are also extensible, so that the infrastructure can be used for transfer of user defined types.
There are a relatively small number of object identifiers representing content types and body parts in common X.400 usage. We've enabled easy use for some of these (the ones that we believe will be useful for Isode customers) by providing convenient string representations and straightforward setup option.
Military messaging uses three main content types. These are:
- P772 (The military messaging format, defined in STANAG 4406)
- Protecting Content Type (PCT) (Usage defined in STANAG 4406 ed 1 v3 and in ed 2, using CMS (Cryptographic Message Syntax) to carry P772)
- A variant of PCT defined in RFC 3855 and used in STANAG 4406 ed 2, where the PCT is wrapped in MIME.
R11.2 provides a military messaging setup option, to allow all of these Content types. It is straightforward to support only a subset of these. We've also extended our X.400 APIs, to make it easy to handle military messages.
AMHS (aviation) specifications define a set of body part types, and text character repertoires within those that are allowed by an AMHS/AFTN Gateway (MTCU). R11.2 provides a setup option so that M-Switch X.400 can be configured to prevent messages not conforming to these restrictions from being passed to the MTCU.
Steve
Comments