RFC 8358 on Update to Digital Signatures on Internet-Draft Documents
rfc-editor@rfc-editor.org Tue, 13 March 2018 00:08 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 706E41250B8 for <ietf-announce@ietfa.amsl.com>; Mon, 12 Mar 2018 17:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 dPSTK0OpmLKa for <ietf-announce@ietfa.amsl.com>; Mon, 12 Mar 2018 17:08:19 -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 345BC124F57 for <ietf-announce@ietf.org>; Mon, 12 Mar 2018 17:08:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 04ECAB81C69; Mon, 12 Mar 2018 17:07:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8358 on Update to Digital Signatures on Internet-Draft Documents
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180313000757.04ECAB81C69@rfc-editor.org>
Date: Mon, 12 Mar 2018 17:07:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/0SJYUIeb24n50Z9Wwxa9LoSndbw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: <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, 13 Mar 2018 00:08:20 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8358
Title: Update to Digital Signatures on
Internet-Draft Documents
Author: R. Housley
Status: Informational
Stream: IETF
Date: March 2018
Mailbox: housley@vigilsec.com
Pages: 9
Characters: 19954
Updates: RFC 5485
I-D Tag: draft-housley-id-sig-update-03.txt
URL: https://www.rfc-editor.org/info/rfc8358
DOI: 10.17487/RFC8358
RFC 5485 specifies the conventions for digital signatures on
Internet-Drafts. The Cryptographic Message Syntax (CMS) is used to
create a detached signature, which is stored in a separate companion
file so that no existing utilities are impacted by the addition of
the digital signature.
The RFC Editor recently published the first RFC that includes non-
ASCII characters in a text file. The conventions specified in RFC
7997 were followed. We assume that non-ASCII characters will soon
start appearing in Internet-Drafts as well. This document updates
the handling of digital signatures on Internet-Drafts that contain
non-ASCII characters in a text file.
This document updates RFC 5485.
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