[jose] I-D Action: draft-ietf-jose-jws-signing-input-options-00.txt

internet-drafts@ietf.org Thu, 23 July 2015 14:34 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150723143435.28809.84534.idtracker@ietfa.amsl.com>
Date: Thu, 23 Jul 2015 07:34:35 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/bK74hzx0f4UBjuk_JXPb-LLAqac>
Cc: jose@ietf.org
Subject: [jose] I-D Action: draft-ietf-jose-jws-signing-input-options-00.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Javascript Object Signing and Encryption Working Group of the IETF.

        Title           : JWS Signing Input Options
        Author          : Michael B. Jones
	Filename        : draft-ietf-jose-jws-signing-input-options-00.txt
	Pages           : 11
	Date            : 2015-07-23

Abstract:
   JSON Web Signature (JWS) represents the payload of a JWS as a
   base64url encoded value and uses this value in the JWS Signature
   computation.  While this enables arbitrary payloads to be integrity
   protected, some have described use cases in which the base64url
   encoding is unnecessary and/or an impediment to adoption, especially
   when the payload is large and/or detached.  This specification
   defines a means of accommodating these use cases by defining an
   option to change the JWS Signing Input computation to not base64url-
   encode the payload.

   Also, JWS includes a representation of the JWS Protected Header and a
   period ('.') character in the JWS Signature computation.  While this
   cryptographically binds the protected Header Parameters to the
   integrity protected payload, some have described use cases in which
   this binding is unnecessary and/or an impediment to adoption,
   especially when the payload is large and/or detached.  This
   specification defines a means of accommodating these use cases by
   defining an option to change the JWS Signing Input computation to not
   include a representation of the JWS Protected Header and a period
   ('.') character in the JWS Signing Input.

   These options are intended to broaden the set of use cases for which
   the use of JWS is a good fit.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-jose-jws-signing-input-options/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-jose-jws-signing-input-options-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[jose] I-D Action: draft-ietf-jose-jws-signing-in… internet-drafts