Privacy Pass: HTTP API
draft-svaldez-pp-http-api-00

Document Type Active Internet-Draft (individual)
Last updated 2020-03-09
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized 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                                          S. Valdez
Internet-Draft                                                Google LLC
Intended status: Informational                              9 March 2020
Expires: 10 September 2020

                         Privacy Pass: HTTP API
                      draft-svaldez-pp-http-api-00

Abstract

   This document specifies an integration for Privacy Pass over an HTTP
   API, along with recommendations on how key commitments are stored and
   accessed by HTTP-based consumers.

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 https://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 10 September 2020.

Copyright Notice

   Copyright (c) 2020 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 (https://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.

Valdez                  Expires 10 September 2020               [Page 1]
Internet-Draft                 PP http api                    March 2020

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Layout  . . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.3.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Privacy Pass HTTP API Wrapping  . . . . . . . . . . . . . . .   3
   3.  Server Configuration/Commitments  . . . . . . . . . . . . . .   4
     3.1.  Commitment Registry . . . . . . . . . . . . . . . . . . .   4
     3.2.  Server Configuration Retrieval  . . . . . . . . . . . . .   5
   4.  Key Commitment Retrieval  . . . . . . . . . . . . . . . . . .   5
   5.  Privacy Pass Issuance . . . . . . . . . . . . . . . . . . . .   6
   6.  Privacy Pass Redemption . . . . . . . . . . . . . . . . . . .   8
     6.1.  Generic Token Redemption  . . . . . . . . . . . . . . . .   8
     6.2.  Direct Redemption . . . . . . . . . . . . . . . . . . . .   9
     6.3.  Delegated Redemption  . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  Well-Known URI  . . . . . . . . . . . . . . . . . . . . .  11
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   The Privacy Pass protocol as described in
   [draft-davidson-pp-protocol] can be integrated with a number of
   different settings, from server to server communication to browsing
   the internet.

   In this document, we will provide an API to use for integrating
   Privacy Pass with an HTTP framework.  Providing the format of HTTP
   requests and responses needed to implement the Privacy Pass protocol.

1.1.  Terminology

   The following terms are used throughout this document.

   *  Server: A service that provides the server-side functionality
      required by the protocol documented here (typically denoted S).

   *  Client: An entity that seeks authorization from a server that
      supports interactions in the Privacy Pass protocol (typically
      denoted C).

   *  Key: The secret key used by the Server for authorizing client
      data.

Valdez                  Expires 10 September 2020               [Page 2]
Internet-Draft                 PP http api                    March 2020

   *  Commitment: Alternative name for Server's public key corresponding
      to the secret key that they hold.

   We assume that all protocol messages are encoded into raw byte format
   before being sent.  We use the TLS presentation language [RFC8446] to
   describe the structure of protocol messages.

1.2.  Layout

   *  Section 2: Describes the wrapping of messages within HTTP
      requests/responses.

   *  Section 3: Describes how HTTP clients retrieve server
Show full document text