Negotiation for Keying Pairwise Routing Protocols in IKEv2
draft-mahesh-karp-rkmp-06
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Mahesh Jethanandani , Brian Weis , Keyur Patel , Dacheng Zhang , Sam Hartman , Uma Chunduri , Albert Tian , Dr. Joseph D. Touch | ||
| Last updated | 2019-01-22 (Latest revision 2018-07-21) | ||
| 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 document describes a mechanism to secure the routing protocols which use unicast to transport their signaling messages. Most of such routing protocols are TCP-based (e.g., BGP and LDP), and the TCP Authentication Option (TCP-AO) is primarily employed for securing the signaling messages of these routing protocols. There are also two exceptions: BFD which is over UDP or MPLS, and RSVP-TE which is over IP (but employs an integrated approach to protecting the signaling messages instead of using IPsec). The proposed mechanism secures pairwise TCP-based Routing Protocol (RP) associations, BFD associations and RSVP-TE associations using the IKEv2 Key Management Protocol (KMP) integrated with TCP-AO, BFD, and RSVP-TE respectively. Included are extensions to IKEv2 and its Security Associations to enable its key negotiation to support TCP-AO, BFD, and RSVP-TE.
Authors
Mahesh Jethanandani
Brian Weis
Keyur Patel
Dacheng Zhang
Sam Hartman
Uma Chunduri
Albert Tian
Dr. Joseph D. Touch
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)