JSON Web Document (JWD)
draft-smith-oauth-json-web-document-00

Document Type Active Internet-Draft (individual)
Last updated 2017-02-06
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
OAuth Working Group                                             C. Smith
Internet-Draft                                               T. Hardjono
Intended status: Standards Track                                     MIT
Expires: August 10, 2017                                February 6, 2017

                        JSON Web Document (JWD)
                 draft-smith-oauth-json-web-document-00

Abstract

   JSON Web Document (JWD) is a means of representing optionally signed
   and/or encrypted JSON content suitable for storage, retrieval,
   transmission, and display in a graphical user interface.  The content
   of a JWD is used as the payload of a JSON Web Signature (JWS)
   structure or as the plaintext of a JSON Web Encryption (JWE)
   structure.

Requirements Language

   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 [RFC2119].

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 August 10, 2017.

Copyright Notice

   Copyright (c) 2017 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

Smith & Hardjono         Expires August 10, 2017                [Page 1]
Internet-Draft                     JWD                     February 2017

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  JWS Document Serialization  . . . . . . . . . . . . . . . . .   3
   4.  JWS Flattened Document Serialization  . . . . . . . . . . . .   3
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   Appendix A.  Example Signed JWD . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   JWD introduces a new set of serializations to JWS and JWE called the
   Document Serializations.  These serializations follow the form of the
   JSON Serialization and Flattened JSON Serialization described in JWS
   Section 7.2 [1], except that the payload, integrity-protected header,
   and non-integrity-protected header contents are all represented as
   unencoded JSON values and MUST NOT be base64url-encoded.

   Signatures present in the data structure MUST be base64url-encoded.
   Signatures are computed using base64url-encoded JSON values for the
   payload and integrity-protected headers as in JWS.  For a given
   payload and JOSE Header, the signature(s) of a JWD MUST be identical
   to signatures computed for semantically equivalent JWT
   serializations.

2.  Terminology

   This specification uses terms defined in the JSON Web Token [JWT],
   JSON Web Signature [JWS], and JSON Web Encryption [JWE]
   specifications.

   These terms are defined by this specification:

      JSON Web Document (JWD)

Smith & Hardjono         Expires August 10, 2017                [Page 2]
Internet-Draft                     JWD                     February 2017
Show full document text