IPSEC_API requirements
draft-mglt-btns-ipsec-api-requirements-00
| Document | Type | Expired Internet-Draft (individual) Expired & archived | |
|---|---|---|---|
| Author | Daniel Migault | ||
| Last updated | 2009-03-02 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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 suite has been designed to secure communication between twonodes. Security is performed at the network layer, and there arealmost no interactions between applications and the IPsec layer. Themain motivation of this API is to enable any applications to interactwith the IPsec layer and to take advantage of the security deployedin IPsec suite. This draft lists applications requirements withregard to the IPsec suite, and we tried not to limit the requirementsto today's application requirements, but also to consider futureapplications' requirements. Applications are associated to differentprivileges, and IPsec layer MUST be protected from nasty IPsecmanipulations. This draft is not considering applications privilegesmanagement. This draft lists any possible requirements on the IPseclayer an application might require.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)