Requirements for an IPsec API
draft-ietf-btns-ipsec-apireq-00

Document Type Expired Internet-Draft (btns WG)
Last updated 2006-04-14
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-btns-ipsec-apireq-00.txt

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

Michael Richardson (mcr@sandelman.ottawa.on.ca)
Bill Sommerfeld (sommerfeld@sun.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)