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)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alexander Azimov , Eugene Bogomazov , Randy Bush , Keyur Patel | ||
| Last updated | 2018-09-19 (Latest revision 2018-03-18) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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
[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
Eugene Bogomazov
Randy Bush
Keyur Patel
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)