Skip to main content

References from draft-ietf-secevent-http-poll

These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.

Reference type help

Document Title Status Type Downref
BCP 14
References Referenced by
normatively references
BCP 195
References Referenced by
normatively references
draft-hunt-scim-notify SCIM Event Notification
References Referenced by
informatively references
draft-ietf-secevent-delivery SET Token Delivery Using HTTP
References Referenced by
informatively references
draft-ietf-secevent-http-push Push-Based Security Event Token (SET) Delivery Using HTTP
References Referenced by
Proposed Standard normatively references
RFC 2119 Key words for use in RFCs to Indicate Requirement Levels
References Referenced by
Best Current Practice normatively references
RFC 2818 HTTP Over TLS
References Referenced by
Informational normatively references Downref
RFC 5246 The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by
Proposed Standard normatively references
RFC 6125 Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
References Referenced by
Proposed Standard normatively references
RFC 6202 Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
References Referenced by
Informational informatively references
RFC 6698 The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA
References Referenced by
Proposed Standard normatively references
RFC 6749 The OAuth 2.0 Authorization Framework
References Referenced by
Proposed Standard informatively references
RFC 6750 The OAuth 2.0 Authorization Framework: Bearer Token Usage
References Referenced by
Proposed Standard informatively references
RFC 7230 Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing
References Referenced by
Proposed Standard informatively references
RFC 7231 Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
References Referenced by
Proposed Standard normatively references
RFC 7235 Hypertext Transfer Protocol (HTTP/1.1): Authentication
References Referenced by
Proposed Standard informatively references
RFC 7515 JSON Web Signature (JWS)
References Referenced by
Proposed Standard normatively references
RFC 7516 JSON Web Encryption (JWE)
References Referenced by
Proposed Standard normatively references
RFC 7519 JSON Web Token (JWT)
References Referenced by
Proposed Standard normatively references
RFC 7521 Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants
References Referenced by
Proposed Standard normatively references
RFC 7525 Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by
Best Current Practice normatively references
RFC 7617 The 'Basic' HTTP Authentication Scheme
References Referenced by
Proposed Standard informatively references
RFC 8174 Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by
Best Current Practice normatively references
RFC 8259 The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by
Internet Standard normatively references
RFC 8417 Security Event Token (SET)
References Referenced by
Proposed Standard normatively references
RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3
References Referenced by
Proposed Standard normatively references
STD 90
References Referenced by
normatively references