The Use of DSS within ESP and AH
draft-moskowitz-auth-dss-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robert Moskowitz | ||
| Last updated | 1999-06-28 | ||
| 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
This memo describes the use of DSS [FIPS-186] in as an authentication mechanism within the IPSEC Encapsulating Security Payload [ESP] and the IPSEC Authentication Header [AH]. DSS provides data origin authentication and integrity protection. DSS authenticated ESP or AH can be used with the Host Identity Payload [HIP99]. Further information on the other components necessary for ESP and AH implementations is provided by [Thayer97a].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)