Origin Validation Signaling
draft-ymbk-sidrops-ov-signal-02

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2019-07-02 (latest revision 2018-12-29)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-sidrops-ov-signal-02.txt

Abstract

Within a trust boundary, e.g. an operator's PoP, it may be useful to have only a few central devices do full Origin Validation using the Resource Public Key Infrastructure, and be able to signal to an internal sender that a received route fails Origin Validation. E.g. route reflectors could perform Origin Validation for a cluster and signal back to a sending client that it sent an invalid route. Routers capable of sending and receiving this signal can use the extended community described in [RFC8097]

Authors

Randy Bush (randy@psg.com)
Keyur Patel (keyur@arrcus.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)