References from draft-ietf-btns-channel-binding-api
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 |
References Referenced by |
normatively references | ||
| draft-bellovin-useipsec |
Guidelines for Specifying the Use of IPsec Version 2
References Referenced by |
Best Current Practice | informatively references | |
| draft-dondeti-useipsec-430x |
Guidelines for using IPsec and IKEv2
References Referenced by |
informatively references | ||
| draft-ietf-btns-abstract-api |
An abstract interface between applications and IPsec
References Referenced by |
normatively references | ||
| draft-ietf-btns-connection-latching |
IPsec Channels: Connection Latching
References Referenced by |
Proposed Standard | normatively references | |
| RFC 2119 |
Key words for use in RFCs to Indicate Requirement Levels
References Referenced by |
Best Current Practice | normatively references | |
| RFC 4301 |
Security Architecture for the Internet Protocol
References Referenced by |
Proposed Standard | normatively references | |
| RFC 4306 |
Internet Key Exchange (IKEv2) Protocol
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5056 |
On the Use of Channel Bindings to Secure Channels
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5386 |
Better-Than-Nothing Security: An Unauthenticated Mode of IPsec
References Referenced by |
Proposed Standard | normatively references | |
| RFC 5387 |
Problem and Applicability Statement for Better-Than-Nothing Security (BTNS)
References Referenced by |
Informational | informatively references |