RFC 8935: Push-Based Security Event Token (SET) Delivery Using HTTP
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8935
- Published
- November 2020
- Authors
- A. Backman; M. Jones; M. Scurtescu; M. Ansari; A. Nadalin
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8936Poll-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 9101The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)Current
August 2021
- RFC 8414OAuth 2.0 Authorization Server MetadataCurrent
June 2018
- RFC 9728OAuth 2.0 Protected Resource MetadataCurrent
April 2025
- RFC 7519JSON Web Token (JWT)Updated
May 2015
- RFC 8417Security Event Token (SET)Current
July 2018
- RFC 8725JSON Web Token Best Current PracticesCurrent
February 2020
- RFC 8705OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access TokensCurrent
February 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?