BGPsec Validation State Signaling
draft-sidrops-bgpsec-validation-signaling-05
Document | Type |
Expired Internet-Draft
(sidrops WG)
Expired & archived
|
|
---|---|---|---|
Authors | Oliver Borchert , Doug Montgomery , Daniel Kopp | ||
Last updated | 2022-09-04 (Latest revision 2020-09-25) | ||
Replaces | draft-borchert-sidrops-bgpsec-validation-signaling | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Dead 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 defines a new BGP non-transitive extended community to carry the BGPsec path validation state. BGP speakers that receive this community string can use the embedded BGPsec validation state in conjunction with configured local policies to influence their decision process. The ability to accept and act on BGPsec path validation state from a neighbor allows for a reduction of path validation processing load and/or increased resilience in the event that a router is temporarily unable to perform local path validation.
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.)