References from rfc8977
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 | normatively references | |
draft-loffredo-regext-rdap-sorting-and-paging |
Registration Data Access Protocol (RDAP) Query Parameters for Result Sorting and Paging 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 5234 |
Augmented BNF for Syntax Specifications: ABNF References Referenced by |
Internet Standard | normatively references | |
RFC 5890 |
Internationalized Domain Names for Applications (IDNA): Definitions and Document Framework References Referenced by |
Proposed Standard | normatively references | |
RFC 6350 |
vCard Format Specification References Referenced by |
Proposed Standard | normatively references | |
RFC 6901 |
JavaScript Object Notation (JSON) Pointer References Referenced by |
Proposed Standard | informatively references | |
RFC 7095 |
jCard: The JSON Format for vCard 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 7231 |
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content 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 7942 |
Improving Awareness of Running Code: The Implementation Status Section References Referenced by |
Best Current Practice | normatively 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 8288 |
Web Linking References Referenced by |
Proposed Standard | normatively references | |
RFC 8605 |
vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol (RDAP) References Referenced by |
Informational | normatively references | Downref |
STD 68 |
Augmented BNF for Syntax Specifications: ABNF References Referenced by |
Internet Standard | normatively references | |
STD 90 |
The JavaScript Object Notation (JSON) Data Interchange Format References Referenced by |
Internet Standard | normatively references |