Protocol Action: 'Security Event Token (SET)' to Proposed Standard (draft-ietf-secevent-token-13.txt)

The IESG <iesg-secretary@ietf.org> Mon, 14 May 2018 19:39 UTC

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: Protocol Action: 'Security Event Token (SET)' to Proposed Standard (draft-ietf-secevent-token-13.txt)
Auto-Submitted: auto-generated
Precedence: bulk
Cc: The IESG <iesg@ietf.org>, secevent-chairs@ietf.org, Yaron Sheffer <yaronf.ietf@gmail.com>, yaronf.ietf@gmail.com, draft-ietf-secevent-token@ietf.org, kaduk@mit.edu, id-event@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <152632679268.10065.5765822960974885303.idtracker@ietfa.amsl.com>
Date: Mon, 14 May 2018 12:39:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Rj6gbFxQYDW7_acEekdeb7PMW0Q>

The IESG has approved the following document:
- 'Security Event Token (SET)'
  (draft-ietf-secevent-token-13.txt) as Proposed Standard

This document is the product of the Security Events Working Group.

The IESG contact persons are Benjamin Kaduk and Eric Rescorla.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-secevent-token/





Technical Summary

The document defines the format of Security Event Tokens (SETs), which allow multiple entities to communicate about identity-related events. The format is intended to be common to multiple higher-level profiling specifications, at leas some of which are expected to be defined outside the IETF.

Working Group Summary

The working group had to go through a second last call, after we failed to reach consensus in the first LC. The second last call did result in consensus that the draft is ready and usable for our "customers", i.e. the specifications that will be profiling it.

Document Quality

We are not aware of current implementations, other than those that implement a trivial subset of the format. A large number of major vendors took part in discussions, and multiple industry groups are expected to use this format.

Personnel

Yaron Sheffer is the document shepherd. Benjamin Kaduk is the responsible AD.

Protocol Action: 'Security Event Token (SET)' to … The IESG