References from draft-hallambaker-mesh-schema
This is an experimental product. 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 Refs Ref'd by |
Best Current Practice | normatively references | |
| draft-hallambaker-mesh-architecture |
Mathematical Mesh 3.0 Part I: Architecture Guide Refs Ref'd by |
normatively references | ||
| draft-hallambaker-mesh-cryptography |
Mathematical Mesh 3.0 Part VIII: Cryptographic Algorithms Refs Ref'd by |
normatively references | ||
| draft-hallambaker-mesh-developer |
Mathematical Mesh: Reference Implementation Refs Ref'd by |
informatively references | ||
| draft-hallambaker-mesh-protocol |
Mathematical Mesh 3.0 Part V: Protocol Reference Refs Ref'd by |
normatively references | ||
| draft-hallambaker-mesh-security |
Mathematical Mesh Part VII: Security Considerations Refs Ref'd by |
normatively references | ||
| draft-hallambaker-mesh-trust |
Mathematical Mesh Part VI: The Trust Mesh Refs Ref'd by |
informatively references | ||
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels Refs Ref'd by |
Best Current Practice | normatively references | |
| RFC 2426 |
vCard MIME Directory Profile Refs Ref'd by |
Proposed Standard | informatively references | |
| RFC 5545 |
Internet Calendaring and Scheduling Core Object Specification (iCalendar) Refs Ref'd by |
Proposed Standard | informatively references |