RFC 6477 on Registration of Military Message Handling System (MMHS) Header Fields for Use in Internet Mail
rfc-editor@rfc-editor.org Tue, 17 January 2012 19:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C71F11E80B6 for <ietf-announce@ietfa.amsl.com>; Tue, 17 Jan 2012 11:17:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.998
X-Spam-Level:
X-Spam-Status: No, score=-103.998 tagged_above=-999 required=5 tests=[AWL=1.679, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NiHLW5sCVgvs for <ietf-announce@ietfa.amsl.com>; Tue, 17 Jan 2012 11:17:22 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id AD7B411E80B4 for <ietf-announce@ietf.org>; Tue, 17 Jan 2012 11:17:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C178E72E039; Tue, 17 Jan 2012 11:14:21 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6477 on Registration of Military Message Handling System (MMHS) Header Fields for Use in Internet Mail
From: rfc-editor@rfc-editor.org
Message-Id: <20120117191421.C178E72E039@rfc-editor.org>
Date: Tue, 17 Jan 2012 11:14:21 -0800
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 19:17:24 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6477 Title: Registration of Military Message Handling System (MMHS) Header Fields for Use in Internet Mail Author: A. Melnikov, G. Lunt Status: Informational Stream: IETF Date: January 2012 Mailbox: Alexey.Melnikov@isode.com, graeme.lunt@smhs.co.uk Pages: 21 Characters: 43492 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-melnikov-mmhs-header-fields-08.txt URL: http://www.rfc-editor.org/rfc/rfc6477.txt A Military Message Handling System (MMHS) processes formal messages ensuring release, distribution, security, and timely delivery across national and international strategic and tactical networks. The MMHS Elements of Service are defined as a set of extensions to the ITU-T X.400 (1992) international standards and are specified in STANAG 4406 Edition 2 and ACP 123. This document specifies message header fields and associated processing for RFC 5322 (Internet Message Format) to provide a comparable messaging service. In addition, this document provides for a STANAG 4406 / Internet Email Gateway that supports message conversion. This document is not an Internet Standards Track specification; it is published for informational purposes. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC