[Id-event] RFC 8935 on Push-Based Security Event Token (SET) Delivery Using HTTP
rfc-editor@rfc-editor.org Tue, 01 December 2020 00:44 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC3A63A138D; Mon, 30 Nov 2020 16:44:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8we1PnY_7s9; Mon, 30 Nov 2020 16:44:48 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A94E3A1429; Mon, 30 Nov 2020 16:44:10 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 07408F4076F; Mon, 30 Nov 2020 16:44:09 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, id-event@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201201004409.07408F4076F@rfc-editor.org>
Date: Mon, 30 Nov 2020 16:44:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/LfaeitZYzPxFeSNj_mpr5iNhe9o>
Subject: [Id-event] RFC 8935 on Push-Based Security Event Token (SET) Delivery Using HTTP
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2020 00:44:56 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8935
Title: Push-Based Security Event Token (SET)
Delivery Using HTTP
Author: A. Backman, Ed.,
M. Jones, Ed.,
M. Scurtescu,
M. Ansari,
A. Nadalin
Status: Standards Track
Stream: IETF
Date: November 2020
Mailbox: richanna@amazon.com,
mbj@microsoft.com,
marius.scurtescu@coinbase.com,
morteza@sharppics.com,
nadalin@prodigy.net
Pages: 15
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-secevent-http-push-14.txt
URL: https://www.rfc-editor.org/info/rfc8935
DOI: 10.17487/RFC8935
This specification defines how a Security Event Token (SET) can be
delivered to an intended recipient using HTTP POST over TLS. The SET
is transmitted in the body of an HTTP POST request to an endpoint
operated by the recipient, and the recipient indicates successful or
failed transmission via the HTTP response.
This document is a product of the Security Events Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC