References from draft-ietf-secevent-http-poll

This is an experimental product. 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
BCP 14	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
BCP 195	Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Refs Ref'd by	Best Current Practice	normatively references
draft-hunt-scim-notify	SCIM Event Notification Refs Ref'd by		informatively references
draft-ietf-secevent-delivery	SET Token Delivery Using HTTP Refs Ref'd by		informatively references
draft-ietf-secevent-http-push	Push-Based Security Event Token (SET) Delivery Using HTTP Refs Ref'd by	Proposed Standard	normatively references
RFC 2119	Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by	Best Current Practice	normatively references
RFC 3339	Date and Time on the Internet: Timestamps Refs Ref'd by	Proposed Standard	informatively references
RFC 3986	Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by	Internet Standard	normatively references
RFC 5246	The Transport Layer Security (TLS) Protocol Version 1.2 Refs Ref'd 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) Refs Ref'd by	Proposed Standard	normatively references
RFC 6202	Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP Refs Ref'd by	Informational	informatively references
RFC 6749	The OAuth 2.0 Authorization Framework Refs Ref'd by	Proposed Standard	informatively references
RFC 6750	The OAuth 2.0 Authorization Framework: Bearer Token Usage Refs Ref'd by	Proposed Standard	informatively references
RFC 7230	Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing Refs Ref'd by	Proposed Standard	informatively references
RFC 7231	Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content Refs Ref'd by	Proposed Standard	normatively references
RFC 7235	Hypertext Transfer Protocol (HTTP/1.1): Authentication Refs Ref'd by	Proposed Standard	informatively references
RFC 7515	JSON Web Signature (JWS) Refs Ref'd by	Proposed Standard	normatively references
RFC 7516	JSON Web Encryption (JWE) Refs Ref'd by	Proposed Standard	normatively references
RFC 7519	JSON Web Token (JWT) Refs Ref'd by	Proposed Standard	normatively references
RFC 7521	Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants Refs Ref'd by	Proposed Standard	informatively references
RFC 7525	Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS) Refs Ref'd by	Best Current Practice	normatively references
RFC 7617	The 'Basic' HTTP Authentication Scheme Refs Ref'd by	Proposed Standard	informatively references
RFC 8174	Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words Refs Ref'd by	Best Current Practice	normatively references
RFC 8259	The JavaScript Object Notation (JSON) Data Interchange Format Refs Ref'd by	Internet Standard	normatively references
RFC 8417	Security Event Token (SET) Refs Ref'd by	Proposed Standard	normatively references
STD 66	Uniform Resource Identifier (URI): Generic Syntax Refs Ref'd by	Internet Standard	normatively references
STD 90	The JavaScript Object Notation (JSON) Data Interchange Format Refs Ref'd by	Internet Standard	normatively references