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

Gert Doering <gert@space.net> Wed, 22 March 2017 14:39 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 ADC19131759 for <idr@ietfa.amsl.com>; Wed, 22 Mar 2017 07:39:33 -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 2DpKDzFhxMu2 for <idr@ietfa.amsl.com>; Wed, 22 Mar 2017 07:39:32 -0700 (PDT)
Received: from mobil.space.net (mobil.space.net [195.30.115.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 5C9E71297AA for <idr@ietf.org>; Wed, 22 Mar 2017 07:39:07 -0700 (PDT)
X-Original-To: idr@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 9EA8161A02 for <idr@ietf.org>; Wed, 22 Mar 2017 15:33:03 +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 231F361637; Wed, 22 Mar 2017 15:33:03 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 14C5F3435E; Wed, 22 Mar 2017 15:33:03 +0100 (CET)
Date: Wed, 22 Mar 2017 15:33:03 +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: <20170322143302.GG2367@Space.Net>
References: <DM2PR09MB044656C168037D0BEF7A78CB843D0@DM2PR09MB0446.namprd09.prod.outlook.com> <20170321205513.GA2367@Space.Net> <CAH1iCirbAnj+Tyn0rs5Zs9-RyY=Qj2onqNh=DehEkDQtPrRSJA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="JjQGvUpjKaxqoY/q"
Content-Disposition: inline
In-Reply-To: <CAH1iCirbAnj+Tyn0rs5Zs9-RyY=Qj2onqNh=DehEkDQtPrRSJA@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/IDBbXo0CPdPFmiVH2Luc5HX8W8U>
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: Wed, 22 Mar 2017 14:39:33 -0000

Hi,

On Tue, Mar 21, 2017 at 03:19:42PM -0700, Brian Dickson wrote:
> 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.

It does not really matter if this is a well-known community or a new
transitive attribute.

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.

So you're adding implementation complexity which will not help anything.

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