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@xxxxxxxx> To: "IETF-Announce" <ietf-announce@xxxxxxxx> 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@xxxxxxxx mailing lists by 2011-10-12. Exceptionally, comments may be > sent to iesg@xxxxxxxx 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@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf