References from draft-ietf-opsawg-mud-acceptable-urls
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-opsawg-mud-tls |
Manufacturer Usage Description (MUD) (D)TLS Profiles for IoT Devices
References Referenced by |
Proposed Standard | informatively references | |
| draft-jimenez-t2trg-mud-coap |
Using MUD on CoAP environments
References Referenced by |
informatively references | ||
| draft-richardson-mud-qrcode |
Loading Manufacturer Usage Description (MUD) URLs from QR Codes
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 7232 |
Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7234 |
Hypertext Transfer Protocol (HTTP/1.1): Caching
References Referenced by |
Proposed Standard | informatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references | |
| RFC 8520 |
Manufacturer Usage Description Specification
References Referenced by |
Proposed Standard | normatively references | |
| RFC 9111 |
HTTP Caching
References Referenced by |
Internet Standard | informatively references |