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

Gert Doering <gert@space.net> Thu, 23 March 2017 07:50 UTC

Return-Path: <gert@space.net>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4B27131746 for <idr@ietfa.amsl.com>; Thu, 23 Mar 2017 00:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OMWQurooGSQW for <idr@ietfa.amsl.com>; Thu, 23 Mar 2017 00:50:13 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6A95131690 for <idr@ietf.org>; Thu, 23 Mar 2017 00:50:10 -0700 (PDT)
X-Original-To: idr@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 155DE619A5 for <idr@ietf.org>; Thu, 23 Mar 2017 08:50:09 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 9D47D61565; Thu, 23 Mar 2017 08:50:08 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 8EA3B6BACB; Thu, 23 Mar 2017 08:50:08 +0100 (CET)
Date: Thu, 23 Mar 2017 08:50:08 +0100
From: Gert Doering <gert@space.net>
To: Brian Dickson <brian.peter.dickson@gmail.com>
Cc: Gert Doering <gert@space.net>, "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>
Message-ID: <20170323075008.GL2367@Space.Net>
References: <DM2PR09MB044656C168037D0BEF7A78CB843D0@DM2PR09MB0446.namprd09.prod.outlook.com> <20170321205513.GA2367@Space.Net> <CAH1iCirbAnj+Tyn0rs5Zs9-RyY=Qj2onqNh=DehEkDQtPrRSJA@mail.gmail.com> <20170322143302.GG2367@Space.Net> <CAH1iCiotU8OzKLWgz=9Z7YMvbFw1apo_273fqvju3j_Mg4ss1Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="mO1Hs8HP9h3I4vdI"
Content-Disposition: inline
In-Reply-To: <CAH1iCiotU8OzKLWgz=9Z7YMvbFw1apo_273fqvju3j_Mg4ss1Q@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/l2vxVcnkKkqUse8UtLT1_BMwfFQ>
Subject: Re: [Idr] operator inputs -- route leak solution
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2017 07:50:15 -0000

Hi,

On Wed, Mar 22, 2017 at 03:13:02PM -0700, Brian Dickson wrote:
> There is direct benefit to partial (even very sparse) deployment.
> 
> The deployment is self-serving; whoever turns this on protects themselves
> and their downstream customers.

Those that are interested in doing so already do customer route filtering
today.

For those that are not interested, where's the incentive in starting to
do so if you have to do a software upgrade first (*and* the other upstreams
of your customers need to send this attribute)?

> This becomes a differentiator with direct benefits, and creates market
> pressure to deploy.

A-ha.  Right, exactly like "filter customer routes" is working today
to give "market pressure".

I always had the impression that *market* pressure is totally in favour
of "accept everything from the customer, send down the pipe whatever
you can, and then bill the customer for the traffic"...

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