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

Job Snijders <job@ntt.net> Wed, 05 September 2018 15:06 UTC

Return-Path: <job@ntt.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 236C2130E3C for <sidrops@ietfa.amsl.com>; Wed, 5 Sep 2018 08:06:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 swJye8bf85Hm for <sidrops@ietfa.amsl.com>; Wed, 5 Sep 2018 08:06:52 -0700 (PDT)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 06777130DF4 for <sidrops@ietf.org>; Wed, 5 Sep 2018 08:06:51 -0700 (PDT)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.90_1) (envelope-from <job@ntt.net>) id 1fxZOL-0009TC-AD (job@us.ntt.net) for sidrops@ietf.org; Wed, 05 Sep 2018 15:06:51 +0000
Received: by mail-oi0-f50.google.com with SMTP id x197-v6so14236186oix.5 for <sidrops@ietf.org>; Wed, 05 Sep 2018 08:06:49 -0700 (PDT)
X-Gm-Message-State: APzg51AMHmtCV4xepSRD5u962nAi/a7AqhZC9YRafAcEHuv6CZXCLP3c oOXJefuw48BO8D68NB5sKVilEjBjrLUGw4qa9HeozQ==
X-Google-Smtp-Source: ANB0VdY1JH6pb2u7b3MQU6USQYeKUtwIIXfShv5A+5byIQ2NrPut5kw+A7p1zAqYjLGvo0BIwAHzoEiAT+GRJEEzNfs=
X-Received: by 2002:aca:bbc4:: with SMTP id l187-v6mr27893561oif.278.1536160008915; Wed, 05 Sep 2018 08:06:48 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <m24lf4ngc4.wl-randy@psg.com>
From: Job Snijders <job@ntt.net>
Date: Wed, 5 Sep 2018 17:06:38 +0200
X-Gmail-Original-Message-ID: <CACWOCC-kSDoxjZyFi6X8JXdga7NdkqWEDvPZKzmHp8q7AnwpPw@mail.gmail.com>
Message-ID: <CACWOCC-kSDoxjZyFi6X8JXdga7NdkqWEDvPZKzmHp8q7AnwpPw@mail.gmail.com>
To: Randy Bush <randy@psg.com>
Cc: Christopher Morrow <christopher.morrow@gmail.com>, Nick Hilliard <nick@foobar.org>, SIDR Operations WG <sidrops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a67b890575211f1d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/evNILarhRrj5N1DmqTgGE7CI_N4>
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: Wed, 05 Sep 2018 15:06:55 -0000

Hi,

As an experiment, can FranceIX and DE-CIX propagate a more-specific of the
AMS-IX peering LAN prefix via their route servers (but clearly mark it with
an extended community). This way, all the authors’ organizations, can make
observations on customer feedback.

In the hours that follow we can perhaps learn of the consequences of
willingly propagating RPKI invalid route announcements.

This would be a repeat of the incident that happenend at DE-CIX on December
5th, 2017. I hope people still remember.

Kind regards,

Job


On Wed, 5 Sep 2018 at 16:56, Randy Bush <randy@psg.com> wrote:

> > As Job suggested, the majority of ixp route servers run BIRD, and
> > taking the example you mention, one of BIRD's known limitations is
> > that it does not handle revalidation.
>
> then it is pretty much useless.
>
> > Another limitation would be that it doesn't handle aggregators as the
> > last element in the as path.
>
> don't care.  they're irrelevant.
>
> randy
>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>