References from draft-ietf-privacypass-consistency-mirror
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-ohai-ohttp |
Oblivious HTTP
References Referenced by |
Proposed Standard | normatively references | |
| draft-ietf-privacypass-architecture |
The Privacy Pass Architecture
References Referenced by |
Informational | normatively references | |
| draft-ietf-privacypass-key-consistency |
Key Consistency and Discovery
References Referenced by |
normatively references | ||
| draft-ietf-privacypass-protocol |
Privacy Pass Issuance Protocol
References Referenced by |
Proposed Standard | normatively references | |
| draft-pw-privacypass-in-band-consistency |
Privacy Pass In-Band Key Consistency Checks
References Referenced by |
informatively references | ||
| draft-schwartz-ohai-consistency-doublecheck |
Key Consistency by Double-Checking via a Semi-Trusted Proxy
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 6570 |
URI Template
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 | |
| RFC 9292 |
Binary Representation of HTTP Messages
References Referenced by |
Proposed Standard | normatively references | |
| STD 98 |
References Referenced by |
informatively references |