IPv6 Security API for BSD Sockets
draft-mcdonald-ipv6-sec-api-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Daniel L. McDonald | ||
| Last updated | 1995-01-30 | ||
| 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
Security is a vital new feature in IPv6. Applications should have some control over security, hence the need for API extensions for security. This Internet Draft discusses such extensions, and the open issues associated with security and APIs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)