References from draft-card-drip-arch
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 160 |
An Architecture for Location and Location Privacy in Internet Applications
References Referenced by |
Best Current Practice | informatively references | |
| draft-moskowitz-hip-hierarchical-hit |
Hierarchical HITs for HIPv2
References Referenced by |
informatively references | ||
| draft-moskowitz-hip-new-crypto |
New Cryptographic Algorithms for HIP
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 4122 |
A Universally Unique IDentifier (UUID) URN Namespace
References Referenced by |
Proposed Standard | informatively references | |
| RFC 6280 |
An Architecture for Location and Location Privacy in Internet Applications
References Referenced by |
Best Current Practice | informatively references | |
| RFC 7401 |
Host Identity Protocol Version 2 (HIPv2)
References Referenced by |
Proposed Standard | informatively references | |
| RFC 7484 |
Finding the Authoritative Registration Data (RDAP) Service
References Referenced by |
Proposed Standard | normatively references | |
| RFC 8174 |
Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
References Referenced by |
Best Current Practice | normatively references |