An interface between applications and keying systems
draft-richardson-btns-abstract-api-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Michael Richardson | ||
| Last updated | 2007-06-29 (Latest revision 2007-05-16) | ||
| Replaced by | draft-ietf-btns-abstract-api | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-btns-abstract-api | |
| 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
The "BTNS" (Better Than Nothing Security) protocols specifies how to use IKEv1 and IKEv2 to do unauthenticated IPsec. This document explains in the abstract (no language bindings are provided) how an application may learn that BTNS IPsec has been applied to a conversation, such that the application can plan to do it's own authentication using a channel binding. In addition, applications can use this API (Application Programming Interface) to request BTNS treatment of the applications' connections.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)