IPv6 Authentication Header
draft-ietf-ipngwg-auth-00
| Document | Type |
Expired Internet-Draft
(ipngwg WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Ran Atkinson | ||
| Last updated | 1995-03-03 | ||
| 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
The Internet community is working on a transition from version 4 of the Internet Protocol (IPv4) to version 6 of the Internet Protocol (IPv6). This memo describes the IPv6 Authentication Header. This optional header provides strong integrity and authentication for IPv6 datagrams. Non-repudiation might be provided by an authentication algorithm used with the Authentication Header, but it is not provided with all authentication algorithms that might be used. Confidentiality, and protection from traffic analysis are not provided by the Authentication Header. Users desiring confidentiality should consider using the IPv6 Encapsulating Security Protocol (ESP) either in lieu of or in conjunction with the Authentication Header. [Atk95b] This document assumes the reader has previously read and understood the related IPv6 Security Architecture document which defines the overall security architecture for IPv6 and provides important background information for this specification. [Atk95a]
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)