BGPsec Operational Considerations
draft-ymbk-bgpsec-ops-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Author | Randy Bush | ||
| Last updated | 2012-01-25 (latest revision 2011-03-14) | ||
| Replaced by | RFC 8207 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-sidr-bgpsec-ops | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ymbk-bgpsec-ops-01.txt
https://www.ietf.org/archive/id/draft-ymbk-bgpsec-ops-01.txt
Abstract
Deployment of the BGPsec architecture and protocols has many operational considerations. This document attempts to collect and present them. It is expected to evolve as BGPsec is formalized and initially deployed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)