SET Token Delivery Using HTTP
draft-hunt-secevent-distribution-01

Document Type Active Internet-Draft (individual)
Last updated 2017-03-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. Hunt, Ed.
Internet-Draft                                                    Oracle
Intended status: Standards Track                            M. Scurtescu
Expires: September 9, 2017                                        Google
                                                           March 8, 2017

                     SET Token Delivery Using HTTP
                  draft-hunt-secevent-distribution-01

Abstract

   This specification defines how a series of security event tokens
   (SETs) may be delivered to a previously registered receiver using
   HTTP over TLS.  The specification defines the metadata the an Event
   Transmitter uses to describe the Event Receiver's HTTP endpoint and
   the SET token delivery configuration.  The specification defines how
   the Event Receiver may check the current configuration metadata and
   delivery status using HTTP GET over TLS.  The specification also
   defines how delivery can be assured subject to the SET Token
   Receiver's need for assurance.

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 September 9, 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
   publication of this document.  Please review these documents

Hunt & Scurtescu        Expires September 9, 2017               [Page 1]
Internet-Draft      draft-hunt-secevent-distribution          March 2017

   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 and Overview . . . . . . . . . . . . . . . . . .   2
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   4
     1.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Control Plane - Monitoring  . . . . . . . . . . . . . . . . .   6
     2.1.  Event Stream Configuration  . . . . . . . . . . . . . . .   6
     2.2.  Event Stream State Model  . . . . . . . . . . . . . . . .   9
     2.3.  Checking Stream Configuration and Stream State  . . . . .  11
   3.  Data Plane  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     3.1.  Event Delivery Process  . . . . . . . . . . . . . . . . .  13
     3.2.  Event Stream State  . . . . . . . . . . . . . . . . . . .  14
     3.3.  HTTP POST Delivery  . . . . . . . . . . . . . . . . . . .  15
     3.4.  Event Stream Verification . . . . . . . . . . . . . . . .  18
   4.  Control Plane - Management and Provisioning . . . . . . . . .  20
     4.1.  Event Stream Resource Type Definition . . . . . . . . . .  20
     4.2.  Creating A New Event Stream . . . . . . . . . . . . . . .  22
     4.3.  Updating An Event Stream  . . . . . . . . . . . . . . . .  24
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  25
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  25
     6.1.  SCIM Schema Registration  . . . . . . . . . . . . . . . .  26
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  26
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  26
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  27
   Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .  27
   Appendix B.  Change Log . . . . . . . . . . . . . . . . . . . . .  28
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  28

1.  Introduction and Overview

   This specification defines how a stream of SETs (see
   [I-D.ietf-secevent-token]) can be transmitted to a previously
   registered Event Receiver using HTTP POST [RFC7231] over TLS.  The
   specification defines the metadata the Event Transmitter uses to
   describe the Event Receiver's HTTP endpoint and the SET token
Show full document text