IPsec Application Programming Interfaces
draft-komu-btns-api-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Sasu Tarkoma , Miika Komu | ||
| Last updated | 2007-06-18 (Latest revision 2007-03-08) | ||
| Replaced by | draft-ietf-btns-c-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-c-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
IPsec based security is usually transparent for applications and and they h have no common mechanism for gathering information about protected network connections and being aware of underlying security mechanisms. This document specifies an API that increases the visibility of IPsec to applications. The API allows applications to use the Stand-alone BTNS mode, control the channel bindigs, and control also other network security properties related to IPsec.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)