Architecture and Deployment Considerations for Secure Origin BGP (soBGP)
draft-white-sobgp-architecture-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Russ White | ||
| Last updated | 2006-06-16 | ||
| 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
There is a great deal of concern over the security of internetworks built using the Border Gateway Protocol to provide routing information to autonomous systems connected to the internetwork. This draft provides an architecture for a secure distributed registry of routing information to address these concerns. The draft begins with an overview of the operation of this system, and then follows with various deployment scenarios, starting with what we believe will be the most common deployment option.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)