Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

JSON Web Signature (JWS) Unencoded Payload Option (RFC7797)

IP.com Disclosure Number: IPCOM000245297D
Original Publication Date: 2016-Feb-01
Included in the Prior Art Database: 2016-Feb-26
Document File: 22 page(s) / 23K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Jones: AUTHOR


The "JSON Web Signature (JWS)" [JWS] specification defines the JWS Signing Input as the input to the digital signature or Message Authentication Code (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 base64url-encoding the payload is unnecessary and/or an impediment to adoption, particularly when the payload is large and/or detached.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Internet Engineering Task Force (IETF)                          M. Jones Request for Comments: 7797                                     Microsoft Updates: 7519                                              February 2016 Category: Standards Track ISSN: 2070-1721

            JSON Web Signature (JWS) Unencoded Payload Option


   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 stating that JSON Web Tokens    (JWTs) MUST NOT use the unencoded payload option defined by this    specification.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7797.

 Jones                        Standards Track                    [Page 1]
 RFC 7797              JWS Unencoded Payload Option         February 2016

 Copyright Notice

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

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