BGPsec Validation State Unverified
draft-borchert-sidrops-bgpsec-state-unverified-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Oliver Borchert , Doug Montgomery | ||
| Last updated | 2021-07-26 (Latest revision 2021-01-15) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
|
||
| 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
In case operators decide to delay BGPsec path validation, none of the available states do properly represent this decision. This document introduces "Unverified" as a well-defined validation state which allows to properly identify a non-evaluated BGPsec routes as not verified.
Authors
Oliver Borchert
Doug Montgomery
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)