Protection of BGP Sessions via the TCP MD5 Signature Option
draft-ietf-idr-rfc2385bis-01
| Document | Type |
Expired Internet-Draft
(idr WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Andy Heffernan | ||
| Last updated | 2002-03-05 | ||
| 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
This memo describes a TCP extension to enhance security for BGP. It defines a new TCP option for carrying an MD5 [RFC1321] digest in a TCP segment. This digest acts like a signature for that segment, incorporating information known only to the connection end points. Since BGP uses TCP as its transport, using this option in the way described in this paper significantly reduces the danger from certain security attacks on BGP
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)