IETF Logo Mail Archive

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

Randy Bush <randy@psg.com> Thu, 23 March 2017 15:48 UTC

Return-Path: <randy@psg.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BD1C129495; Thu, 23 Mar 2017 08:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, 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 D9dHF6x3duA6; Thu, 23 Mar 2017 08:48:19 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2194D129405; Thu, 23 Mar 2017 08:48:19 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cr4yG-0005uC-7t; Thu, 23 Mar 2017 15:48:16 +0000
Date: Thu, 23 Mar 2017 10:48:15 -0500
Message-ID: <m2o9ws9eps.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Gert Doering <gert@space.net>
Cc: Interminable Discussion Room <idr@ietf.org>, sidrops@ietf.org, GMO Crops <grow@ietf.org>
In-Reply-To: <20170322143302.GG2367@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>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/DVj-LDrn08qZav4EMghVyanObMM>
Subject: Re: [Sidrops] [Idr] operator inputs -- route leak solution
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2017 15:48:25 -0000

> 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.

not quite.  if ntt and l3 told fiber@home "on or befofe next jan 1st,
have draft-ymbk-idr-bgp-open-policy enabled," (as they do with route:
object reg); beyond that, l3, ntt, and fiber@home need to do no more.
it's all in the open.  the leak does not happen.

imiho, the other draft with the transitive eOTR attribute
(draft-ymbk-idr-bgp-eotr-policy) is not needed.  it is a way to diagnose
at a distance, and i prefer to stop at the source.

randy

v2.23.0 | Report a Bug | By Email