Re: [Sidrops] WGLC - draft-ietf-sidrops-validating-bgp-speaker - ENDS 09/07/2018 - Sept 7th 2018

Nick Hilliard <nick@foobar.org> Fri, 07 September 2018 07:17 UTC

Return-Path: <nick@foobar.org>
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 DF32A129C6A for <sidrops@ietfa.amsl.com>; Fri, 7 Sep 2018 00:17:43 -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 dNN2uqpoZLwZ for <sidrops@ietfa.amsl.com>; Fri, 7 Sep 2018 00:17:41 -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 7DBE11286D9 for <sidrops@ietf.org>; Fri, 7 Sep 2018 00:17:41 -0700 (PDT)
X-Envelope-To: sidrops@ietf.org
Received: from crumpet.local ([194.88.241.230]) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id w876HXht093591 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Sep 2018 07:17:33 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host [194.88.241.230] claimed to be crumpet.local
To: Christopher Morrow <christopher.morrow@gmail.com>
Cc: Randy Bush <randy@psg.com>, sidrops@ietf.org
References: <CAL9jLaYqGt1+f3GaccNwjPOHxM34ifWDu5bhRx24PMYHpqV4XQ@mail.gmail.com> <20180822161549.GA1021@hanna.meerval.net> <42CA116C-4F74-4D31-A58E-3D7528FC529F@de-cix.net> <CAL9jLaaYzZmGVgEPfuDze5D_yN5x_CMKFEnY7XwM2F7EycwEOQ@mail.gmail.com> <m2y3cgo4ta.wl-randy@psg.com> <e6a23568-3c44-0749-fe6d-d9c76df97342@foobar.org> <m24lf4ngc4.wl-randy@psg.com> <CAL9jLaa0ma04X+KpSQioEE_EPRUNM1SUJeWCr0h860qaFkPOOg@mail.gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <db7a3ee8-6ba6-a21f-61b3-a99a31bf2871@foobar.org>
Date: Fri, 7 Sep 2018 08:17:35 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 PostboxApp/6.1.2
MIME-Version: 1.0
In-Reply-To: <CAL9jLaa0ma04X+KpSQioEE_EPRUNM1SUJeWCr0h860qaFkPOOg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/VeyM8JWm3gndZqj03YYBkF1n_uQ>
Subject: Re: [Sidrops] WGLC - draft-ietf-sidrops-validating-bgp-speaker - ENDS 09/07/2018 - Sept 7th 2018
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <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: Fri, 07 Sep 2018 07:17:44 -0000

Christopher Morrow wrote on 05/09/2018 17:39:
> On Wed, Sep 5, 2018 at 10:56 AM Randy Bush <randy@psg.com <mailto:randy@psg.com>> wrote:
> "is pretty much useless" - Needs bug(s) filed and development work in 
> order to rectify this problem.
> I'd caution against: "is useless, never talk to it again" because ... 
> ideally we want all the bgp software folk to do the right thing here, right?
>   so ideally ov-clarify already whacks "popular hardware vendors" on the 
> nose, let's make sure the 'popular software vendors' also have bugs 
> filed against them?

from the bigger picture point of view, buggy rpki implementations are 
irritating but implementation problems like this are not sufficient 
reason for the ietf to create workarounds, particularly when those 
workarounds require new code on router stacks, i.e. have a substantial 
material cost and require debugging.  As an aside, router vendors have 
shown historically that they don't much like supporting cli glue for 
extended communities, so it's difficult to see how they'd write code for 
this.

The ov-clarify draft will probably help deployment in the longer term, 
as it creates a tickbox which will end up on RFPs and compliance testing 
suites.

Nick