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

Nick Hilliard <nick@foobar.org> Wed, 22 March 2017 22:08 UTC

Return-Path: <nick@foobar.org>
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 207B11292D3; Wed, 22 Mar 2017 15:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 Wwh3v6O4CsWL; Wed, 22 Mar 2017 15:08:45 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD4CB1293DA; Wed, 22 Mar 2017 15:08:44 -0700 (PDT)
X-Envelope-To: grow@ietf.org
Received: from cupcake.local ([194.88.241.232]) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v2MM8eLH069326 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Mar 2017 22:08:41 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host [194.88.241.232] claimed to be cupcake.local
Message-ID: <58D2F5E7.80205@foobar.org>
Date: Thu, 23 Mar 2017 00:08:39 +0200
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.11 (Macintosh/20170302)
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
CC: "idr@ietf.org" <idr@ietf.org>, "grow@ietf.org" <grow@ietf.org>
References: <DM2PR09MB044656C168037D0BEF7A78CB843D0@DM2PR09MB0446.namprd09.prod.outlook.com> <20170321205513.GA2367@Space.Net> <CAH1iCirbAnj+Tyn0rs5Zs9-RyY=Qj2onqNh=DehEkDQtPrRSJA@mail.gmail.com> <20170322143302.GG2367@Space.Net>
In-Reply-To: <20170322143302.GG2367@Space.Net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/voZI1_8Q13xJCnO7_0NEqmtOZDw>
Subject: Re: [Idr] [GROW] 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: Wed, 22 Mar 2017 22:08:48 -0000

[cc: trimmed]

Gert Doering wrote:
> If ISPs do not turn this *on* on their customer connections, it will not
> do anything - and given that those ISPs that *need* to turn this on are
> the ones that are not caring today, I'm still not seeing why they would
> turn this on tomorrow.

the asns unlikely to turn on a feature like this are leaf customers,
which is intentional.

Nick