BGPsec Validation State Signaling
draft-sidrops-bgpsec-validation-signaling-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Oliver Borchert , Doug Montgomery , Daniel Kopp | ||
| Last updated | 2020-05-21 (Latest revision 2019-11-18) | ||
| Replaces | draft-borchert-sidrops-bgpsec-validation-signaling | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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 updates RFC 8097 by adding the BGPsec path validation state to the reserved portion of the extended community in RFC 8097. BGP speakers that receive this community string can use the embedded BGPsec validation state and configure local policies that allow it being used to influence their decision process. This is especially helpful because Section 5 of RFC 8205 specifically allows putting BGPsec path validation temporarily on hold. This allows reducing the load of validation particularly from IBGP learned routes or EBGP learned routes when warranted.
Authors
Oliver Borchert
Doug Montgomery
Daniel Kopp
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)