Symmetric SET Transfer Protocol
draft-hunt-secevent-sstp-00

Document Type Active Internet-Draft (individual)
Last updated 2018-03-22
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. Hunt, Ed.
Internet-Draft                                                    Oracle
Intended status: Standards Track                              A. Nadalin
Expires: September 23, 2018                                    Microsoft
                                                          March 22, 2018

                    Symmetric SET Transfer Protocol
                      draft-hunt-secevent-sstp-00

Abstract

   This specification defines how security event tokens (SETs) may be
   exchanged between a client and service provider using HTTP POST over
   TLS using a symmetric format.  The specification supports three modes
   of operation: "push", "pull", and "push-pull" bi-directional SET
   exchange.  The specification also defines a simple acknowledge
   mechanism allowing parties to confirm delivery.

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 23, 2018.

Copyright Notice

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

Hunt & Nadalin         Expires September 23, 2018               [Page 1]
Internet-Draft          draft-hunt-secevent-sstp              March 2018

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   4
     1.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Simple SET Transfer Protocol  . . . . . . . . . . . . . . . .   5
     2.1.  SSTP Message Format (Content-Type: application/sstp+json)   5
     2.2.  Examples  . . . . . . . . . . . . . . . . . . . . . . . .   7
       2.2.1.  Example Push Transfer . . . . . . . . . . . . . . . .   8
       2.2.2.  Example Pull Transfer . . . . . . . . . . . . . . . .   9
       2.2.3.  Example Push-Pull Bi-directional Transfer . . . . . .  13
     2.3.  Error Response Handling . . . . . . . . . . . . . . . . .  15
   3.  Authentication and Authorization  . . . . . . . . . . . . . .  16
     3.1.  Use of Tokens as Authorizations . . . . . . . . . . . . .  17
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
     4.1.  Authentication Using Signed SETs  . . . . . . . . . . . .  18
     4.2.  HTTP Considerations . . . . . . . . . . . . . . . . . . .  18
     4.3.  TLS Support Considerations  . . . . . . . . . . . . . . .  18
     4.4.  Authorization Token Considerations  . . . . . . . . . . .  19
       4.4.1.  Bearer Token Considerations . . . . . . . . . . . . .  19
   5.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  19
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  20
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  21
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  22
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .  23
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  23

1.  Introduction

   [EDITORS NOTE: This specification is based upon draft-ietf-secevent-
   delivery and attempts to provide a unified single MTI protocol
   solution satisfying all use cases for SECEVENTS.]

   This specification defines how SETs (see [I-D.ietf-secevent-token])
   can be exchanged using HTTP [RFC7231] over TLS using a symmetric
   request/response format.  The specification supports three modes of
   operation: "push", "pull", and "push-pull" bi-directional SET
   exchange.  The specification also defines a simple acknowledge
   mechanism allowing parties to confirm delivery or attempt re-
   delivery.
Show full document text