Re: Last Call: <draft-melnikov-mmhs-header-fields-04.txt> (Registrationof Military Message Handling System (MMHS) header fields foruse in Internet Mail) to Informational RFC
"t.petch" <daedulus@btconnect.com> Thu, 15 September 2011 08:50 UTC
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90B4A21F8663 for <ietf@ietfa.amsl.com>; Thu, 15 Sep 2011 01:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.318
X-Spam-Level:
X-Spam-Status: No, score=-2.318 tagged_above=-999 required=5 tests=[AWL=0.281, BAYES_00=-2.599]
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 m0ILjL4QmXVr for <ietf@ietfa.amsl.com>; Thu, 15 Sep 2011 01:50:10 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by ietfa.amsl.com (Postfix) with ESMTP id 838A921F862F for <ietf@ietf.org>; Thu, 15 Sep 2011 01:50:08 -0700 (PDT)
Received: from host109-153-79-81.range109-153.btcentralplus.com (HELO pc6) ([109.153.79.81]) by c2beaomr07.btconnect.com with SMTP id EJR90157; Thu, 15 Sep 2011 09:52:18 +0100 (BST)
Message-ID: <00b801cc737b$d11b4a20$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: ietf@ietf.org
References: <20110914195304.6235.35027.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-melnikov-mmhs-header-fields-04.txt> (Registrationof Military Message Handling System (MMHS) header fields foruse in Internet Mail) to Informational RFC
Date: Thu, 15 Sep 2011 09:47:34 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4E71BCC1.0123, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.9.15.75714:17:7.586, ip=109.153.79.81, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, __INT_PROD_LOC, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020D.4E71BCC2.023F, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
Cc: Alexey.Melnikov@isode.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Sep 2011 08:50:10 -0000
I notice that section 3, to which IANA are directed, contains many formulations such as " Specification document(s): [[anchor14: this document]]" Would I be right in thinking that this is what other documents would refer to as " RFCXXXX -- Note to RFC-Editor - replace RFCXXXX by the RFC Number assigned to this document" ? Tom Petch ----- Original Message ----- From: "The IESG" <iesg-secretary@ietf.org> To: "IETF-Announce" <ietf-announce@ietf.org> Sent: Wednesday, September 14, 2011 9:53 PM Subject: Last Call: <draft-melnikov-mmhs-header-fields-04.txt> (Registrationof Military Message Handling System (MMHS) header fields foruse in Internet Mail) to Informational RFC > > The IESG has received a request from an individual submitter to consider > the following document: > - 'Registration of Military Message Handling System (MMHS) header fields > for use in Internet Mail' > <draft-melnikov-mmhs-header-fields-04.txt> as an Informational RFC > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@ietf.org mailing lists by 2011-10-12. Exceptionally, comments may be > sent to iesg@ietf.org instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > Abstract > > > A Miltary 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. This document describes a method for enabling those MMHS > Elements of Service that are defined as Heading Extension to be > encoded as RFC 5322 (Internet Email) message header fields. These > header field definitions support the provision of a STANAG 4406 MMHS > over Internet Email, and also provides for a STANAG 4406 / Internet > Email Gateway supporting message conversion compliant to this > specification. > > > > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-melnikov-mmhs-header-fields/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-melnikov-mmhs-header-fields/ > > > No IPR declarations have been submitted directly on this I-D. > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce
- Re: Last Call: <draft-melnikov-mmhs-header-fields… t.petch
- Re: Last Call: <draft-melnikov-mmhs-header-fields… Alexey Melnikov
- Re: Last Call: <draft-melnikov-mmhs-header-fields… Mykyta Yevstifeyev
- Re: Last Call: <draft-melnikov-mmhs-header-fields… Alexey Melnikov
- Re: Last Call: <draft-melnikov-mmhs-header-fields… Mykyta Yevstifeyev
- Re: Last Call: <draft-melnikov-mmhs-header-fields… Julian Reschke
- Re: Last Call: <draft-melnikov-mmhs-header-fields… Peter Saint-Andre
- Re: Last Call: <draft-melnikov-mmhs-header-fields… ned+ietf
- Re: Last Call: <draft-melnikov-mmhs-header-fields… Alexey Melnikov
- Re: Last Call: <draft-melnikov-mmhs-header-fields… Mykyta Yevstifeyev