Cryptographic Algorithms, Use, & Implementation Requirments for TCP Authentication Option
draft-lebovitz-ietf-tcpm-tcp-ao-crypto-02
| Document | Type |
Replaced Internet-Draft
(tcpm WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Gregory M. Lebovitz | ||
| Last updated | 2009-09-17 (Latest revision 2009-07-27) | ||
| Replaced by | draft-ietf-tcpm-tcp-ao-crypto | ||
| 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 | Replaced by draft-ietf-tcpm-tcp-ao-crypto | |
| 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 TCP Authentication Option, TCP-AO, relies on security algorithms to provide authentication between two end-points. There are many such algorithms available, and two TCP-AO systems cannot interoperate unless they are using the same algorithm(s). This document specifies the algorithms and attributes that can be used in TCP-AO's current manual keying mechanism.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)