References from draft-ietf-regext-rdap-openid
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.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
BCP 14 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
BCP 205 |
Improving Awareness of Running Code: The Implementation Status Section References Referenced by |
Best Current Practice | informatively references | |
draft-hollenbeck-regext-rdap-openid |
Federated Authentication for the Registration Data Access Protocol (RDAP) using OpenID Connect References Referenced by |
informatively references | ||
FYI 36 |
Internet Security Glossary, Version 2 References Referenced by |
Informational | informatively references | |
RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels References Referenced by |
Best Current Practice | normatively references | |
RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax References Referenced by |
Internet Standard | normatively references | |
RFC 4949 |
Internet Security Glossary, Version 2 References Referenced by |
Informational | informatively references | |
RFC 5226 |
Guidelines for Writing an IANA Considerations Section in RFCs References Referenced by |
Best Current Practice | normatively references | |
RFC 6749 |
The OAuth 2.0 Authorization Framework References Referenced by |
Proposed Standard | normatively references | |
RFC 6750 |
The OAuth 2.0 Authorization Framework: Bearer Token Usage References Referenced by |
Proposed Standard | normatively references | |
RFC 7009 |
OAuth 2.0 Token Revocation References Referenced by |
Proposed Standard | normatively references | |
RFC 7230 |
Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing References Referenced by |
Proposed Standard | normatively references | |
RFC 7235 |
Hypertext Transfer Protocol (HTTP/1.1): Authentication References Referenced by |
Proposed Standard | normatively references | |
RFC 7480 |
HTTP Usage in the Registration Data Access Protocol (RDAP) References Referenced by |
Proposed Standard | normatively references | |
RFC 7481 |
Security Services for the Registration Data Access Protocol (RDAP) References Referenced by |
Proposed Standard | normatively references | |
RFC 7482 |
Registration Data Access Protocol (RDAP) Query Format References Referenced by |
Proposed Standard | normatively references | |
RFC 7483 |
JSON Responses for the Registration Data Access Protocol (RDAP) References Referenced by |
Proposed Standard | normatively references | |
RFC 7515 |
JSON Web Signature (JWS) References Referenced by |
Proposed Standard | normatively references | |
RFC 7519 |
JSON Web Token (JWT) References Referenced by |
Proposed Standard | normatively references | |
RFC 7942 |
Improving Awareness of Running Code: The Implementation Status Section References Referenced by |
Best Current Practice | informatively references | |
RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words References Referenced by |
Best Current Practice | normatively references | |
RFC 8628 |
OAuth 2.0 Device Authorization Grant References Referenced by |
Proposed Standard | normatively references | |
RFC 8693 |
OAuth 2.0 Token Exchange References Referenced by |
Proposed Standard | normatively references | |
STD 66 |
Uniform Resource Identifier (URI): Generic Syntax References Referenced by |
Internet Standard | normatively references |