JWS Unencoded Payload Option
draft-ietf-jose-jws-signing-input-options-06

The information below is for an old version of the document
Document Type Active Internet-Draft (jose WG)
Last updated 2015-12-13 (latest revision 2015-11-24)
Replaces draft-jones-jose-jws-signing-input-options
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jim Schaad
Shepherd write-up Show (last changed 2015-11-19)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Responsible AD Kathleen Moriarty
Send notices to "Jim Schaad" <ietf@augustcellars.com>, mbj@microsoft.com
IANA IANA review state IANA - Not OK
IANA action state None
JOSE Working Group                                              M. Jones
Internet-Draft                                                 Microsoft
Updates: 7519 (if approved)                            November 24, 2015
Intended status: Standards Track
Expires: May 27, 2016

                      JWS Unencoded Payload Option
              draft-ietf-jose-jws-signing-input-options-06

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.  This option is intended to broaden the set of
   use cases for which the use of JWS is a good fit.

   This specification updates RFC 7519 by prohibiting the use of the
   unencoded payload option in JSON Web Tokens (JWTs).

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."

   This Internet-Draft will expire on May 27, 2016.

Copyright Notice

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

Jones                     Expires May 27, 2016                  [Page 1]
Internet-Draft        JWS Unencoded Payload Option         November 2015

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Notational Conventions . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3.  The "b64" Header Parameter . . . . . . . . . . . . . . . . . .  4
   4.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  Example with Header Parameters {"alg":"HS256"} . . . . . .  5
     4.2.  Example with Header Parameters
           {"alg":"HS256","b64":false}  . . . . . . . . . . . . . . .  6
   5.  Unencoded Payload Content Restrictions . . . . . . . . . . . .  6
     5.1.  Unencoded Detached Payload . . . . . . . . . . . . . . . .  7
     5.2.  Unencoded JWS Compact Serialization Payload  . . . . . . .  7
     5.3.  Unencoded JWS JSON Serialization Payload . . . . . . . . .  7
   6.  Intended Use by Applications . . . . . . . . . . . . . . . . .  8
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
     8.1.  JWS and JWE Header Parameter Registration  . . . . . . . .  9
       8.1.1.  Registry Contents  . . . . . . . . . . . . . . . . . .  9
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     9.1.  Normative References . . . . . . . . . . . . . . . . . . .  9
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 10
   Appendix A.  Acknowledgements  . . . . . . . . . . . . . . . . . . 10
   Appendix B.  Document History  . . . . . . . . . . . . . . . . . . 11
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12

Jones                     Expires May 27, 2016                  [Page 2]
Internet-Draft        JWS Unencoded Payload Option         November 2015

1.  Introduction

   The "JSON Web Signature (JWS)" [JWS] specification defines the JWS
   Signing Input as the input to the digital signature or MAC
   computation, with the value ASCII(BASE64URL(UTF8(JWS Protected
   Header)) || '.' || BASE64URL(JWS Payload)).  While this works well in
   practice for many use cases, including those accommodating arbitrary
   payload values, other use cases have been described in which
Show full document text