Update to Digital Signatures on Internet-Draft Documents
draft-housley-id-sig-update-00

Document Type Active Internet-Draft (individual)
Last updated 2017-10-05 (latest revision 2017-10-04)
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd Jim Schaad
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD Alissa Cooper
Send notices to Jim Schaad <jimsch@augustcellars.com>
INTERNET-DRAFT                                                  R. Housley
Intended Status: Informational                              Vigil Security
Updates RFC 5485 (once approved)
Expires: 4 April 2018                                       4 October 2017

        Update to Digital Signatures on Internet-Draft Documents
                  <draft-housley-id-sig-update-00.txt>

Abstract

   RFC 5485 specifies the conventions for digital signatures on
   Internet-Draft documents.  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-Draft document for
   non-ASCII characters in a "text" file.

   This document (once approved) updates RFC 5485.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Housley                                                         [Page 1]
INTERNET-DRAFT                                             February 2016

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

1.  Introduction

   RFC 5485 [IDSIG] specifies the conventions for digital signatures on
   Internet-Draft documents.  The Cryptographic Message Syntax (CMS)
   [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 [RFCED] 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-Draft document
   for non-ASCII characters in a "text" file.

   This document (once approved) updates RFC 5485 [IDSIG], which
   contains the conventions that have been used by IETF Secretariat to
   digitally sign Internet-Drafts for the past few years.  The IETF
   Secretariat generates the digital signature shortly after the
   Internet-Draft is posted in the repository.

   The digital signature allows anyone to confirm that the contents of
   the Internet-Draft have not been altered since the time that the
   document was signed.

   The digital signature is intended to provide a straightforward way
   for anyone to determine whether a particular file contains the
   Internet-Draft that was made available by the IETF Secretariat.  The
   signing-time associated with the signature provides the wall clock
   time at which the signature was generate; it is not intended to
   provide a trusted timestamp.

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [STDWORDS].

Housley                                                         [Page 2]
INTERNET-DRAFT                                             February 2016
Show full document text