RFC 7912 on Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure
rfc-editor@rfc-editor.org Tue, 21 June 2016 23:59 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 C54C012DEC4 for <ietf-announce@ietfa.amsl.com>; Tue, 21 Jun 2016 16:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.028
X-Spam-Level:
X-Spam-Status: No, score=-104.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t20tn7nGVXyE for <ietf-announce@ietfa.amsl.com>; Tue, 21 Jun 2016 16:59:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02E1C12DED0 for <ietf-announce@ietf.org>; Tue, 21 Jun 2016 16:58:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EA63BB80D3E; Tue, 21 Jun 2016 16:58:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7912 on Message Authorizing Email Header Field and Its Use for the Draft and Release Procedure
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160621235846.EA63BB80D3E@rfc-editor.org>
Date: Tue, 21 Jun 2016 16:58:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/cv3opsGDMcXrCro4WB7p5nQ9mu0>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Jun 2016 23:59:12 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7912
Title: Message Authorizing Email Header Field
and Its Use for the Draft
and Release Procedure
Author: A. Melnikov
Status: Informational
Stream: Independent
Date: June 2016
Mailbox: alexey.melnikov@isode.com
Pages: 11
Characters: 24086
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-melnikov-mmhs-authorizing-users-14.txt
URL: https://www.rfc-editor.org/info/rfc7912
DOI: http://dx.doi.org/10.17487/RFC7912
This document describes a procedure for when a Military Message
Handling System (MMHS) message is composed by one user and is only
released to the mail transfer system when one or more Authorizing
Users authorize release of the message by adding the
MMHS-Authorizing-Users header field. The resulting message can be
optionally signed by the sender and/or reviewer, allowing recipients
to verify both the original signature (if any) and the review
signatures.
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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
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