Route Leak Detection and Filtering using Roles in Update and Open messages
draft-ymbk-idr-bgp-eotr-policy-02

Document Type Expired Internet-Draft (individual)
Last updated 2018-09-19 (latest revision 2018-03-18)
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-idr-bgp-eotr-policy-02.txt

Abstract

[draft-ietf-idr-bgp-open-policy] defines a BGP OPEN capability and consequent route marking which enforces a valley-free peering relationship. This document defines an eOTC (external Only To Customer) transitive BGP attribute which propagates the specific marking to automatically detect route leaks. The goal is to allow a distant AS to determine a violation of valley-free peering.

Authors

Alexander Azimov (aa@qrator.net)
Eugene Bogomazov (eb@qrator.net)
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.)