JSON Web Service Binding Version 1.0
draft-hallambaker-json-web-service-04

Document Type Active Internet-Draft (individual)
Last updated 2017-05-09
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)
Network Working Group                                    P. Hallam-Baker
Internet-Draft                                         Comodo Group Inc.
Intended status: Standards Track                             May 9, 2017
Expires: November 10, 2017

                  JSON Web Service Binding Version 1.0
                 draft-hallambaker-json-web-service-04

Abstract

   The JSON Web Binding (JWB) describes a standardized approach to
   implementing Web Services.  Services are advertised using the DNS SRV
   and HTTP Well Known Service conventions.  Messages may be
   authenticated or authenticated and encrypted at the message layer in
   addition to any transport and/or network layer security.  Service
   messages are encoded in JSON using Internet time format for Date-Time
   fields and Base64urlencoding for binary objects.

   This document specifies Version 1.0 of JWB which uses HTTP/1.1 for
   transport.  Use of the multiple stream capabilities of HTTP version 2
   is outside the scope of this document.

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 November 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Hallam-Baker            Expires November 10, 2017               [Page 1]
Internet-Draft        JSON Web Service Binding v1.0             May 2017

   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
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   3.  Service Discovery . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Host Identification . . . . . . . . . . . . . . . . . . .   5
       3.1.1.  SRV Host discovery  . . . . . . . . . . . . . . . . .   5
       3.1.2.  DNS Fallback  . . . . . . . . . . . . . . . . . . . .   5
       3.1.3.  TXT Service Description . . . . . . . . . . . . . . .   5
     3.2.  HTTP host processing  . . . . . . . . . . . . . . . . . .   6
       3.2.1.  Use of TLS transport  . . . . . . . . . . . . . . . .   6
       3.2.2.  Fallback Processing Rules . . . . . . . . . . . . . .   6
       3.2.3.  Service Continuation  . . . . . . . . . . . . . . . .   7
     3.3.  Example . . . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  HTTP Messages . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  Request . . . . . . . . . . . . . . . . . . . . . . . . .   9
     4.2.  Response  . . . . . . . . . . . . . . . . . . . . . . . .  10
   5.  Error handling and response codes . . . . . . . . . . . . . .  10
   6.  Content Encoding  . . . . . . . . . . . . . . . . . . . . . .  11
     6.1.  Direct Encoding . . . . . . . . . . . . . . . . . . . . .  11
     6.2.  Content-Encoding: jose-jwb  . . . . . . . . . . . . . . .  11
     6.3.  Authenticated . . . . . . . . . . . . . . . . . . . . . .  12
     6.4.  Authenticated Encryption  . . . . . . . . . . . . . . . .  12
   7.  Content Type  . . . . . . . . . . . . . . . . . . . . . . . .  13
   8.  JSON Data Bindings  . . . . . . . . . . . . . . . . . . . . .  13
     8.1.  Request Message . . . . . . . . . . . . . . . . . . . . .  13
     8.2.  Response Message  . . . . . . . . . . . . . . . . . . . .  13
     8.3.  Data Fields . . . . . . . . . . . . . . . . . . . . . . .  13
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     9.1.  Integrity . . . . . . . . . . . . . . . . . . . . . . . .  14
       9.1.1.  DNS Spoofing  . . . . . . . . . . . . . . . . . . . .  15
       9.1.2.  TLS Downgrade . . . . . . . . . . . . . . . . . . . .  15
Show full document text