Exising Practices for Smooth Key Rollover with Interior Routing Protocols
draft-rja-smooth-rollover-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Ran Atkinson | ||
| Last updated | 2014-08-18 (Latest revision 2014-02-14) | ||
| 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 some existing deployed operational practices that are in use to provide smooth key rollover for IETF interior routing protocols (e.g. IS-IS, OSPFv2, RIPv2). This is intended for eventual publication as an Informational RFC on the Independent Submission track, not via the IETF track.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)