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

Daniel Kopp <daniel.kopp@de-cix.net> Tue, 29 October 2019 15:29 UTC

Return-Path: <daniel.kopp@de-cix.net>
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 676F9120018 for <sidrops@ietfa.amsl.com>; Tue, 29 Oct 2019 08:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 RiitwnyYTDOI for <sidrops@ietfa.amsl.com>; Tue, 29 Oct 2019 08:29:02 -0700 (PDT)
Received: from de-cix.net (relay4.de-cix.net [46.31.121.24]) (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 DEBD212006A for <sidrops@ietf.org>; Tue, 29 Oct 2019 08:29:01 -0700 (PDT)
IronPort-SDR: SIkD/6VYpHZxFTT9+IQ4GJPidow3SZ0E3actCnriAGSPaX2SpKRGeATi77a8cdAc4Ak+wwSKJL agPkW+SbEZ/fYNS9AokNQyjG6DZdy443nMjv4WpsZfbPKmB0hn3x37+YjLwtvRpIJWkfD/mJdG EFbFxr3QVQODZKHAbQ7CkEl13q3WprOFpedS9SaXiUKm+ZBu29es2qiEpslTyM0f+qNFL+9mba BymBLa4tQ75TC5WL3q2xisj2ie3bskAU83TDb9LGfZ2B9SE1oqnXG/b+rQXgXVEJpvvEl8V6rf twM=
X-IronPort-AV: E=Sophos;i="5.68,244,1569276000"; d="scan'208";a="12913909"
Received: from unknown (HELO smtp.de-cix.net) ([192.168.65.10]) by mailgw014.de-cix.net with ESMTP; 29 Oct 2019 16:25:56 +0100
Received: from EX02.for-the-inter.net (ex02.for-the-inter.net [192.168.49.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.de-cix.net (Postfix) with ESMTPS id 369E0B00B8; Tue, 29 Oct 2019 16:29:00 +0100 (CET)
Received: from EX02.for-the-inter.net (192.168.49.20) by EX02.for-the-inter.net (192.168.49.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Tue, 29 Oct 2019 16:28:59 +0100
Received: from EX02.for-the-inter.net ([fe80::1cb2:801e:f870:7df9]) by EX02.for-the-inter.net ([fe80::1cb2:801e:f870:7df9%4]) with mapi id 15.01.1779.005; Tue, 29 Oct 2019 16:28:59 +0100
From: Daniel Kopp <daniel.kopp@de-cix.net>
To: Christopher Morrow <christopher.morrow@gmail.com>
CC: SIDR Operations WG <sidrops@ietf.org>
Thread-Topic: [Sidrops] WGLC - draft-ietf-sidrops-validating-bgp-speaker - ENDS 09/07/2018 - Sept 7th 2018
Thread-Index: AQHUOie94b+qhBJXv0aVQvhLDzuGmaTL0PCAgAMH8YCAEWE/gIAA7XyAgAAYbQCAAfNFgIAABTEAgAGYyQCCjg8OgIABdcKA
Date: Tue, 29 Oct 2019 15:28:59 +0000
Message-ID: <BAC844E2-16B3-4F80-89DB-E3E88067A20E@de-cix.net>
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> <20180905073454.GU3097@hanna.meerval.net> <16AB499B-D859-48D2-9C36-AAF4C6F29B1C@de-cix.net> <20180906134026.GC3097@hanna.meerval.net> <F812E3F2-8882-410F-82A2-942BA3B3096C@de-cix.net> <CAL9jLaZrVYDyUEWVqn992wxGMurGsjrmDeu-jjR6Rp6smCv+1g@mail.gmail.com>
In-Reply-To: <CAL9jLaZrVYDyUEWVqn992wxGMurGsjrmDeu-jjR6Rp6smCv+1g@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.6.18)
x-originating-ip: [192.168.140.236]
Content-Type: text/plain; charset="utf-8"
Content-ID: <120114722B8D7A488196AC8592C1130E@for-the-inter.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/lPvG1sRrJoUOyKiWFivZDazo8i8>
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: Tue, 29 Oct 2019 15:29:05 -0000

Many thanks Chris for brining this up again. The authors would really like to progress with this draft.
From beginning of this year (and already last year) it seems that RPKI adoption is on a steep ascent.
But I think this doesn’t affect the idea of this draft (tagging RPKI validation results onto BGP announcements, especially at IXPs) in a very negative way.

I appreciate Randy’s and Nick's feedback and looking forward to further comments and opinions.
Hope we can have a consensus about the draft soon.

Thanks again!

Best
Daniel


> On 28. Oct 2019, at 18:11, Christopher Morrow <christopher.morrow@gmail.com> wrote:
> 
> This WGLC ... has dragged on very much too long :(
> 
> I think there's not consensus to move this forward at this time.
> I think I should have said this ~8 months ago, but was hopeful that
> either we might reach consensus OR the draft would be move to match
> expectations of the working group.
> 
> At this point, I think a clear signal from the WG would help the
> authors change their draft OR abandon it.
> 
> -chris
> 
> 
> On Fri, Sep 7, 2018 at 10:03 AM Daniel Kopp <daniel.kopp@de-cix.net> wrote:
>> 
>> 
>>> On 6. Sep 2018, at 15:40, Job Snijders <job@ntt.net> wrote:
>>> 
>>> In that case, it appears the draft has been taken over by current
>>> events?  From what I understood from your organisation's communications
>>> related to deploying RPKI origin validation there has been a commitment
>>> to deploy this fall.
>> 
>> No, the draft hasn’t been taken over by other events.
>> The idea was to adjust the implementation according to the draft.
>> So I don’t see that this draft is outdated in that sense.
>> 
>>> This puzzles me - AMS-IX already implemented this, some documentation
>>> can be found here: https://ams-ix.net/technical/specifications-descriptions/ams-ix-route-servers/route-server-filtering
>>> (note the 6777:65012, 6777:65022, and 6777:65023) communities.
>> 
>> Yes, AMS-IX has already some flavour of implementation for that… and one goal of the draft is to have a common and well defined way how to implement this.
>> 
>> Kind regards
>> Daniel
>> 
>> 
>> _______________________________________________
>> Sidrops mailing list
>> Sidrops@ietf.org
>> https://www.ietf.org/mailman/listinfo/sidrops