Authentication-Key Rollover mechanism for Routing and Management Protocols
draft-viswanathan-keyrollover-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Sriram Viswanathan | ||
| Last updated | 2006-10-12 | ||
| 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 memo discusses the authentication for routing and management protocols based on preconfigured keys,the need and basis for key rollover, and an mechanism to seamlessly rollover the authentication keys. It is intended for an application where secure administrative access to all the end-points of the protocol connection is normally available. The strategy described herein improves upon the current practice where a key is preconifigured at all endpoints and the key rollover is done manually within a short synchronized window to avoid connection drops due to key mismatch.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)