References from draft-mglt-btns-ipsec-api-requirements

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.

Reference type help

Document	Title	Status	Type	Downref
BCP 14	References Referenced by		normatively references
draft-ietf-btns-abstract-api	An abstract interface between applications and IPsec References Referenced by		informatively references
draft-ietf-btns-c-api	C-Bindings for IPsec Application Programming Interfaces References Referenced by		informatively references
draft-ietf-btns-connection-latching	IPsec Channels: Connection Latching References Referenced by	Proposed Standard	informatively references
draft-ietf-btns-ipsec-apireq	Requirements for an IPsec API 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 2367	PF_KEY Key Management API, Version 2 References Referenced by	Informational	informatively references
RFC 4301	Security Architecture for the Internet Protocol References Referenced by	Proposed Standard	normatively references
RFC 4302	IP Authentication Header References Referenced by	Proposed Standard	normatively references
RFC 4306	Internet Key Exchange (IKEv2) Protocol References Referenced by	Proposed Standard	normatively references
RFC 4307	Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2) 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	informatively references