An abstract interface between applications and IPsec
draft-ietf-btns-abstract-api-02
| Document | Type |
Expired Internet-Draft
(btns WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Michael Richardson | ||
| Last updated | 2008-11-02 | ||
| Replaces | draft-richardson-btns-abstract-api | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document explains in the abstract (no language bindings are provided) how an application may learn that IPsec has been applied to a conversation or specify that IPsec should be used. Though this is useful in general it is particularly useful for applications that wish to use BTNS (Better Than Nothing Security -- a mode of IPsec keying), either in conjunction with channel binding or otherwise.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)