HTTP State Tokens
draft-west-http-state-tokens-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-28
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                                            M. West
Internet-Draft                                                    Google
Intended status: Standards Track                          March 28, 2019
Expires: September 29, 2019

                           HTTP State Tokens
                    draft-west-http-state-tokens-00

Abstract

   This document describes a mechanism which allows HTTP servers to
   maintain stateful sessions with HTTP user agents.  It aims to address
   some of the security and privacy considerations which have been
   identified in existing state management mechanisms, providing
   developers with a well-lit path towards our current understanding of
   best practice.

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 September 29, 2019.

Copyright Notice

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

West                   Expires September 29, 2019               [Page 1]
Internet-Draft              HTTP State Tokens                 March 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Wait. Don't we have cookies?  . . . . . . . . . . . . . .   3
     1.2.  No. Really. We have cookies already. Why do we need this
           new thing?  . . . . . . . . . . . . . . . . . . . . . . .   4
     1.3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Conventions . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Conformance . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  Infrastructure  . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  HTTP State Tokens . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Requests and Responses  . . . . . . . . . . . . . . . . .   6
     3.3.  Token Storage . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Syntax  . . . . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.1.  The 'Sec-Http-State' HTTP Header Field  . . . . . . . . .   8
     4.2.  The 'Sec-Http-State-Options' HTTP Header Field  . . . . .   9
   5.  Delivering HTTP State Tokens  . . . . . . . . . . . . . . . .  11
     5.1.  Attach HTTP State Tokens to a request . . . . . . . . . .  11
     5.2.  Generate a request's signature  . . . . . . . . . . . . .  12
   6.  Configuring HTTP State Tokens . . . . . . . . . . . . . . . .  13
   7.  Security and Privacy Considerations . . . . . . . . . . . . .  15
     7.1.  Confidentiality and Integrity . . . . . . . . . . . . . .  15
     7.2.  Signed Sessions . . . . . . . . . . . . . . . . . . . . .  16
     7.3.  User Control  . . . . . . . . . . . . . . . . . . . . . .  16
     7.4.  Lifetime  . . . . . . . . . . . . . . . . . . . . . . . .  16
     7.5.  Ambient Authority and Cross-Site Delivery . . . . . . . .  16
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  17
     8.1.  Header Field Registry . . . . . . . . . . . . . . . . . .  17
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  18
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  19
     9.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .  19
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .  19
   Appendix B.  Changes  . . . . . . . . . . . . . . . . . . . . . .  20
     B.1.  Since the beginning of time . . . . . . . . . . . . . . .  20
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   This document defines a state-management mechanism for HTTP that
   allows clients to create and persist origin-bound session identifiers
Show full document text