Requirements for an IPsec API
draft-ietf-ipsp-ipsec-apireq-00
| Document | Type |
Expired Internet-Draft
(ipsp WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Bill E. Sommerfeld | ||
| Last updated | 2003-06-19 | ||
| 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
Given the open nature of the Internet today, application protocols require strong security. IPsec's wire protocols appear to meet the requirements of many protocols. The lack of a common model for application-layer interfaces has complicated use of IPsec by upper- layer protocols. This document provides an overview of facilities which a host IPsec implementation should provide to applications to allow them to both observe and influence how IPsec protects their communications.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)