Re: [sidr] [Idr] operator inputs -- route leak solution

Brian Dickson <brian.peter.dickson@gmail.com> Tue, 21 March 2017 22:19 UTC

MIME-Version: 1.0
In-Reply-To: <20170321205513.GA2367@Space.Net>
References: <DM2PR09MB044656C168037D0BEF7A78CB843D0@DM2PR09MB0446.namprd09.prod.outlook.com> <20170321205513.GA2367@Space.Net>
From: Brian Dickson <brian.peter.dickson@gmail.com>
Date: Tue, 21 Mar 2017 15:19:42 -0700
Message-ID: <CAH1iCirbAnj+Tyn0rs5Zs9-RyY=Qj2onqNh=DehEkDQtPrRSJA@mail.gmail.com>
To: Gert Doering <gert@space.net>
Cc: "Sriram, Kotikalapudi (Fed)" <kotikalapudi.sriram@nist.gov>, "grow@ietf.org" <grow@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>, "draft-ietf-idr-route-leak-detection-mitigation.authors@ietf.org" <draft-ietf-idr-route-leak-detection-mitigation.authors@ietf.org>, "sidr wg list (sidr@ietf.org)" <sidr@ietf.org>
Content-Type: multipart/alternative; boundary="001a11409824696c41054b450a11"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/_aVkbdTTeN3Z63GoKvQTZrWXca0>
Subject: Re: [sidr] [Idr] operator inputs -- route leak solution
Precedence: list

Pre-emptive top-post in case anyone mistakes the technique proposed: This
will NOT be implemented via communities.

The proposal is for a NEW optional transitive attribute.

If any operators can answer the original question, this will be very
helpful. Thank you in advance to any and all operators.

Reminder on optional+transitive logic
- If the attribute is not understood/implemented/enabled, the attribute is
passed unmodified.
- If it is understood & implemented & enabled, behavior is subject to the
applicable standards.
- Thus, optional transitives are "opt-in", by definition.

The proposal itself is an IDR WG I-D, and as such not finalized; input here
is definitely helpful in reaching consensus, understanding requirements,
etc.

Brian

On Tue, Mar 21, 2017 at 1:55 PM, Gert Doering <gert@space.net> wrote:

> Hi,
>
> On Tue, Mar 21, 2017 at 06:00:36PM +0000, Sriram, Kotikalapudi (Fed) wrote:
> > >>From an operator point of view,
> > are you willing to place a piece of relationship info (as stated above)
> > in the BGP update for the significant gain of a route leak solution
> > that works well to detect/stop route leaks that do happen,
> > and prevents single point of failures in incremental/partial
> > deployment scenarios?
>
> I'm not sure it will do any good.
>
> Those ISPs that care about the garbage their customers try to inject
> already do prefix/as-path filtering.
>
> Those ISPs that do not care today will not add bother to add a filter on
> this well-known community value (... and most likely, the customer
> router sending out unfiltered garbage won't have "send-community"
> enabled either).
>
> Gert Doering
>         -- NetMaster
> --
> have you enabled IPv6 on something today...?
>
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
>

[sidr] operator inputs -- route leak solution Sriram, Kotikalapudi (Fed)
Re: [sidr] [Idr] operator inputs -- route leak so… Gert Doering
Re: [sidr] [Idr] operator inputs -- route leak so… Brian Dickson
Re: [sidr] [Idr] operator inputs -- route leak so… Neil J. McRae
Re: [sidr] [Idr] operator inputs -- route leak so… Gert Doering
Re: [sidr] [Idr] operator inputs -- route leak so… Brian Dickson
Re: [sidr] [Sidrops] operator inputs -- route lea… Randy Bush
Re: [sidr] [Sidrops] operator inputs -- route lea… Brian Dickson
Re: [sidr] [Sidrops] operator inputs -- route lea… Randy Bush
Re: [sidr] [Sidrops] operator inputs -- route lea… Sriram, Kotikalapudi (Fed)
Re: [sidr] [Idr] operator inputs -- route leak so… Gert Doering
Re: [sidr] [GROW] [Sidrops] operator inputs -- ro… Susan Hares
Re: [sidr] [Idr] operator inputs -- route leak so… Randy Bush