datatracker.ietf.org
Sign in
Version 5.12.0.p2, 2015-03-02
Report a bug

BGPSEC router key rollover as an alternative to beaconing
draft-rogaglia-sidr-bgpsec-rollover-01

Document type: Replaced Internet-Draft (sidr WG)
Document stream: IETF
Last updated: 2012-08-14 (latest revision 2012-06-05)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

IETF State: Adopted by a WG
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-sidr-bgpsec-rollover
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:
http://www.ietf.org/archive/id/draft-rogaglia-sidr-bgpsec-rollover-01.txt

Abstract

The current BGPSEC draft documents do not specifies a key rollover process for routers. This document describes a possible key rollover process and explores its impact to mitigate replay attacks and eliminate the need for beaconing in BGPSEC.

Authors

Roque Gagliano <rogaglia@cisco.com>
Keyur Patel <keyupate@cisco.com>
Brian Weis <bew@cisco.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)