[Openid-specs-risc] FW: [Id-event] Last Call: <draft-ietf-secevent-http-poll-09.txt> (Poll-Based Security Event Token (SET) Delivery Using HTTP) to Proposed Standard

[Tim Cappalli]

FYI CAEP folks.

From: Id-event <id-event-bounces at ietf.org>
Date: Wednesday, April 29, 2020 at 19:35
To: IETF-Announce <ietf-announce at ietf.org>
Cc: secevent-chairs at ietf.org <secevent-chairs at ietf.org>, yaronf.ietf at gmail.com <yaronf.ietf at gmail.com>, draft-ietf-secevent-http-poll at ietf.org <draft-ietf-secevent-http-poll at ietf.org>, id-event at ietf.org <id-event at ietf.org>, kaduk at mit.edu <kaduk at mit.edu>
Subject: [Id-event] Last Call: <draft-ietf-secevent-http-poll-09.txt> (Poll-Based Security Event Token (SET) Delivery Using HTTP) to Proposed Standard

The IESG has received a request from the Security Events WG (secevent) to
consider the following document: - 'Poll-Based Security Event Token (SET)
Delivery Using HTTP'
  <draft-ietf-secevent-http-poll-09.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 at ietf.org mailing lists by 2020-05-13. Exceptionally, comments may
be sent to iesg at ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This specification defines how a series of Security Event Tokens
   (SETs) may be delivered to an intended recipient using HTTP POST over
   TLS initiated as a poll by the recipient.  The specification also
   defines how delivery can be assured, subject to the SET Recipient's
   need for assurance.




The file can be obtained via
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-secevent-http-poll%2F&data=02%7C01%7Ctim.cappalli%40microsoft.com%7Ccb40a6c969a341dee8ab08d7ec95f381%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238001092564449&sdata=7AgQEsPdpeab%2Fc3ZAO4XnIB%2FedmH7TC7k8aOMWedU7M%3D&reserved=0

IESG discussion can be tracked via
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-secevent-http-poll%2Fballot%2F&data=02%7C01%7Ctim.cappalli%40microsoft.com%7Ccb40a6c969a341dee8ab08d7ec95f381%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238001092564449&sdata=NLl%2FgDIJUGyisJZ%2FWD9ReeVOkl3Gg1LkYTFy1O%2Fa%2FaI%3D&reserved=0


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





_______________________________________________
Id-event mailing list
Id-event at ietf.org
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fid-event&data=02%7C01%7Ctim.cappalli%40microsoft.com%7Ccb40a6c969a341dee8ab08d7ec95f381%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637238001092564449&sdata=itT4Wb3yymPosxG59853Jmk%2F7PmN%2B28iuFYBBJAL6Fw%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20200430/73e5af09/attachment.html>