The RFC standards are published by the Internet Engineering Task Forum (IETF). They provide commercial standards on which Military Messaging Handling Systems (MMHS) are built.

Further information is available from the FAQS.ORG RFC archives, or you can search for a specific RFC:

The following RFCs are relevant to Nexor.

Instant Messaging RFC 2279 Instant Messaging / Presence Protocol Requirements
RFC 3920 Extensible Messaging and Presence Protocol (XMPP): core
RFC 3921 Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence
RFC 3922 Mapping the Extensible Messaging and Presence Protocol (XMPP) to Common Presence and Instant Messaging (CPIM)
RFC 3923 End to End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP)
RFC 3261 SIP: Session Initiation Protocol
RFC 3856 A Presence Event Package for the Session Initiation Protocol (SIP)
RFC 3857 A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP)
RFC 3858 An Extensible Markup Language (XML) Based Format for Watcher Information
RFC 3994 Indication of Message Composition for Instant Messaging
LDAP/X.500 RFC 1777 Lightweight Directory Access Protocol (LDAPV2)
RFC 1778 The String Representation of Standard Attribute Syntaxes
RFC 1779 A String Representation of Distinguished Names
RFC 2251 Lightweight Directory Access Protocol (LDAPV3)
RFC 2252 Attribute Syntax Definitions
RFC 2253 UTF-8 String Representation of Distinguished Names
RFC 2254 The String Representation of LDAP Search Filters
RFC 2255 The LDAP URL Format
RFC 2256 A Summary of the X.500(96) User Schema for use with LDAPv3
RFC 2829 Authentication methods for LDAP
RFC 2830 LDAP (V3): Extension for Transport Layer Security
RFC 2831 Using Digest Authentication as a SASL Mechanism
RFC 2849 The LDAP Data Interchange Format (LDIF) – Technical Specification
POP3/IMAP RFC 1939 Post Office Protocol Version 3 (POP3)
RFC 2060 Internet Message Access Protocol – Version 4rev1 (IMAP4)
S/MIME v3 RFC 2630 Cryptographic Message Syntax
RFC 2634 Enhanced Security Services for S/MIME
RFC 3114 Implementing the Company Classification Policy with the S/MIME Security Label
RFC 3183 Domain Security Services using S/MIME
RFC 3370 Cryptographic Message Syntax Algorithms
RFC 3850 S/MIME v3.1 Certificate Handling
RFC 3851 S/MIME v3.1 Message Specification (enhances RFC 2633)
RFC 3852 S/MIME v3.1 Cryptographic Message Syntax (CMS) (enhances RFC 3369)
RFC 3854 Securing X.400 Content with S/MIME
RFC 3855 Transporting S/MIME Objects in X.400
SMTP/X.400 RFC 821 Simple Mail Transfer Protocol
RFC 822 Standard for the Format of ARPA Internet Text Messages
RFC 1006 ISO Transport Service on top of the TCP Version: 3
RFC 1521 MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
RFC 1522 MIME (Multipurpose Internet Mail Extensions) Part Two: Message Header Extensions for Non-ASCII Text
RFC 1801 X.400-MHS use of the X.500 Directory to support X.400-MHS Routing
RFC 1869 SMTP Service Extensions
RFC 1870 SMTP Service Extension for Message Size Declaration
RFC 1891 SMTP Service Extension for Delivery Status Notifications
RFC 2156 MIXER (Mime Internet X.400 Enhanced Relay): Mapping between X.400 and RFC 822/MIME
RFC 2197 SMTP Service Extension for Command Pipelining
RFC 2231 MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
RFC 2442 The Batch SMTP Media Type
RFC 2554 SMTP Service Extension for Authentication
SNMP RFC 2248 Network Services Monitoring MIB
RFC 2249 Mail Monitoring MIB
RFC 2605  Directory Server Monitoring MIB
Utilities RFC 1950 ZLIB Compressed Data Format Specification v3.3
RFC 1951 DEFLATE Compressed Data Format Specification v1.3

Find more information on Nexor’s MMHS capability and secure information exchange technology.


Talk To One Of Our Experts

We value your privacy

Military Message Handling Systems: A Reference Architecture White Paper


Military Message Handling Systems: A Reference Architecture – Military Message Handling Systems (MMHS) have become established as the defacto way of exchanging high grade electronic messages within a national military enclave, between military domains and within operational domains. MORE DETAILS
Upgrading an Existing System case study image


Upgrading an Existing System (A European Navy) - When you are using something that works well, you do not want to change it. Sometimes there is no choice – you need to address something as other factors change. MORE DETAILS

Be the first to know about developments in secure information exchange