References from draft-blanchet-regext-entityid2rdapserver
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 |
References Referenced by |
normatively references | ||
| BCP 188 |
References Referenced by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 3339 |
Date and Time on the Internet: Timestamps
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5246 |
The Transport Layer Security (TLS) Protocol Version 1.2
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7159 |
The JavaScript Object Notation (JSON) Data Interchange Format
References Referenced by |
Proposed Standard | normatively references | |
| RFC 7258 |
Pervasive Monitoring Is an Attack
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7480 |
HTTP Usage in the Registration Data Access Protocol (RDAP)
References Referenced by |
Internet Standard | informatively references | |
| RFC 7481 |
Security Services for the Registration Data Access Protocol (RDAP)
References Referenced by |
Internet Standard | informatively references | |
| RFC 7482 |
Registration Data Access Protocol (RDAP) Query Format
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7483 |
JSON Responses for the Registration Data Access Protocol (RDAP)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7484 |
Finding the Authoritative Registration Data (RDAP) Service
References Referenced by |
Proposed Standard | informatively references |