Last Call: <draft-ietf-secevent-http-push-10.txt> (Push-Based Security Event Token (SET) Delivery Using HTTP) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 29 April 2020 23:32 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A2633A0AAF; Wed, 29 Apr 2020 16:32:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-secevent-http-push-10.txt> (Push-Based Security Event Token (SET) Delivery Using HTTP) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.128.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: Yaron Sheffer <yaronf.ietf@gmail.com>, draft-ietf-secevent-http-push@ietf.org, secevent-chairs@ietf.org, kaduk@mit.edu, yaronf.ietf@gmail.com, id-event@ietf.org
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <158820312379.13441.1879321961741360115@ietfa.amsl.com>
Date: Wed, 29 Apr 2020 16:32:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/3L_qIPzvNRz2UmGGFAQXswW33cg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Apr 2020 23:32:10 -0000

The IESG has received a request from the Security Events WG (secevent) to
consider the following document: - 'Push-Based Security Event Token (SET)
Delivery Using HTTP'
  <draft-ietf-secevent-http-push-10.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-05-13. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This specification defines how a Security Event Token (SET) may be
   delivered to an intended recipient using HTTP POST.  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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-secevent-http-push/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-secevent-http-push/ballot/


No IPR declarations have been submitted directly on this I-D.