References from draft-hallambaker-mesh-protocol
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 | |
| draft-hallambaker-mesh-architecture |
Mathematical Mesh 3.0 Part I: Architecture Guide References Referenced by |
normatively references | ||
| draft-hallambaker-mesh-developer |
Mathematical Mesh: Reference Implementation References Referenced by |
informatively references | ||
| draft-hallambaker-mesh-schema |
Mathematical Mesh 3.0 Part IV: Schema Reference References Referenced by |
normatively references | ||
| draft-hallambaker-mesh-security |
Mathematical Mesh 3.0 Part VII: Security Considerations References Referenced by |
normatively references | ||
| draft-hallambaker-mesh-udf |
Mathematical Mesh 3.0 Part II: Uniform Data Fingerprint. 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 3339 |
Date and Time on the Internet: Timestamps References Referenced by |
Proposed Standard | normatively references | |
| RFC 4648 |
The Base16, Base32, and Base64 Data Encodings 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 8446 |
The Transport Layer Security (TLS) Protocol Version 1.3 References Referenced by |
Proposed Standard | normatively references |