References from draft-ietf-rpp-core
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 |
|---|---|---|---|---|
| draft-ietf-rpp-data-objects |
RESTful Provisioning Protocol (RPP) Data Objects
References Referenced by |
normatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 2616 |
Hypertext Transfer Protocol -- HTTP/1.1
References Referenced by |
Draft Standard | normatively references | |
| RFC 2782 |
A DNS RR for specifying the location of services (DNS SRV)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 3553 |
An IETF URN Sub-namespace for Registered Protocol Parameters
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3986 |
Uniform Resource Identifier (URI): Generic Syntax
References Referenced by |
Internet Standard | normatively references | |
| RFC 5730 |
Extensible Provisioning Protocol (EPP)
References Referenced by |
Internet Standard | normatively references | |
| RFC 5731 |
Extensible Provisioning Protocol (EPP) Domain Name Mapping
References Referenced by |
Internet Standard | normatively references | |
| RFC 5733 |
Extensible Provisioning Protocol (EPP) Contact Mapping
References Referenced by |
Internet Standard | normatively references | |
| RFC 6570 |
URI Template
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6648 |
Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
References Referenced by |
Best Current Practice | normatively references | |
| RFC 6749 |
The OAuth 2.0 Authorization Framework
References Referenced by |
Proposed Standard | normatively references | |
| RFC 6838 |
Media Type Specifications and Registration Procedures
References Referenced by |
Best Current Practice | normatively references | |
| RFC 7519 |
JSON Web Token (JWT)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7617 |
The 'Basic' HTTP Authentication Scheme
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8288 |
Web Linking
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 | |
| RFC 8725 |
JSON Web Token Best Current Practices
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8748 |
Registry Fee Extension for the Extensible Provisioning Protocol (EPP)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 8941 |
Structured Field Values for HTTP
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9068 |
JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9110 |
HTTP Semantics
References Referenced by |
Internet Standard | normatively references | |
| RFC 9205 |
Building Protocols with HTTP
References Referenced by |
Best Current Practice | normatively references | |
| RFC 9325 |
Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
References Referenced by |
Best Current Practice | normatively references | |
| RFC 9457 |
Problem Details for HTTP APIs
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9460 |
Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9535 |
JSONPath: Query Expressions for JSON
References Referenced by |
Proposed Standard | normatively references |