Re: [Sidrops] Talk: RPKI Deployment: Status, Challenges and the Learning-Validator

"Carlos M. Martinez" <carlosm3011@gmail.com> Thu, 20 July 2017 15:41 UTC

Return-Path: <carlosm3011@gmail.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 0E6521252BA for <sidrops@ietfa.amsl.com>; Thu, 20 Jul 2017 08:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 LzJ8s87QIkb1 for <sidrops@ietfa.amsl.com>; Thu, 20 Jul 2017 08:41:28 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 C513312EC46 for <sidrops@ietf.org>; Thu, 20 Jul 2017 08:41:27 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id g127so30651087wmd.0 for <sidrops@ietf.org>; Thu, 20 Jul 2017 08:41:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=kFqwKlmUG8sHrTo3k9Zy2jkqNJxnQQAoEiZslLNAqZc=; b=QCHZqxFKOdLc/hECcXO7YT6E6HO2ZFdFH0GrTPp5eprvw9BF+9A4vxtLY2mjowYB1s iwnTxxgdsBLl5qwT2gwDuLHMUdvvfqtPaMPbIM0hS8LmNOuyEESPJxormCgcXkAquKMH cEFC7DnvAAb0DNTA/Ouo29P+wSSs1EBD4687cioP7sl8RlK6w9uNDNOtwXTHI8RbkyKL +vc6hU1JZB630C+YcmL4+b4+z0xDYPKzC+ScRH6HHfIsRYN0LlxFA/+/elFOU5JzuuXq v25bnwqO1/5+kq3RljXFFUmFNUOd1B4YsaPcjBNVW0WFgpz4I/5XX2YCyZvh/y3oYxJL 41eg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=kFqwKlmUG8sHrTo3k9Zy2jkqNJxnQQAoEiZslLNAqZc=; b=KCEchaHm3BLsQzFsgMJ8OxPVMCCMfCB/K9ZDape+u57oElSw/AcsMvKHsGBwVohx3m gDv5eGkdAq9PryZvcXCzHe0eT9h177LYjkcqw2DJm61DGblA7a5sSMjL1wNEjCnGWXKX RdXMPE28d35W6S7SLyozHq8JJorJK+rPieMEwQ+xe8k1CCKaA+B5+vPuoYusdNLgaKPO 5o4XXqzfTeiLJrqKpWStDp8sTvdSPA26CaHP4Rv5P3EYmtmIcsSu04Kmxgy3ViQHUZs/ Bhs+KE0cDpw9aVDDMHRmZNNazeGd6wr5vipxZb9A5mbq20xAmuz181aUtb6ljT8mi7Z9 uzNA==
X-Gm-Message-State: AIVw113fVlpwWEIrBS9ioCTC3HFk4oeSLGAcP9HjNWHfFDTTQ7+6ZeZD 18jHcUhwpIUXQTpf/cE=
X-Received: by 10.28.12.195 with SMTP id 186mr2640712wmm.5.1500565286172; Thu, 20 Jul 2017 08:41:26 -0700 (PDT)
Received: from [31.133.150.35] ([2001:67c:1232:144:c921:6563:e075:70bb]) by smtp.gmail.com with ESMTPSA id 2sm5921886wrn.24.2017.07.20.08.41.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jul 2017 08:41:24 -0700 (PDT)
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
To: Matthias Waehlisch <m.waehlisch@fu-berlin.de>
Cc: sidrops@ietf.org
Date: Thu, 20 Jul 2017 17:41:24 +0200
Message-ID: <5ED572DF-AC77-4F54-92DC-F65C86F4E022@gmail.com>
In-Reply-To: <alpine.WNT.2.00.1707171628150.10844@mw-x1>
References: <alpine.WNT.2.00.1707171628150.10844@mw-x1>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_11533BFC-E6B9-4BC5-9F25-DE1595AD5317_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5383)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/U_oC8tcX45JcFX0pRFR_Dldtgd0>
Subject: Re: [Sidrops] Talk: RPKI Deployment: Status, Challenges and the Learning-Validator
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 20 Jul 2017 15:41:30 -0000

I was about to ask a question on the mic but was late to the line. Maybe 
it’s worth sharing it here:

- How we define a ROA to be “wrong” ? One that invalidates routes or 
one that causes legitimate traffic to be dropped ?

Why? because we’ve seen in many cases ROAs that create lots of 
invalids but validate a less-specific route that covers those invalids

In a way, this even a positive side-effect, sort of vacuum-cleaning your 
routing tables.

I believe analyzing what ROAs are wrong is quite important, but i’d 
believe this particular case should not count as wrong.

thanks!

/Carlos

On 17 Jul 2017, at 16:36, Matthias Waehlisch wrote:

> two comments via the list because we run out of time:
>
> (1) I'm wondering about the statement that the quality of ROAs 
> decreases
> over time. My impression is that the quality improved because of
> excellent training by RIRs and others.
>
> Slide 4 shows absolute values, which is not helpful in this context.
>
>
> (2) Regarding ROV measurements: "Similar results apparently from
> measurements by Randy Bush and others (didn't yet see details)"
>
> Details are available, easy to find using Google:
>
> * "Towards a Rigorous Methodology for Measuring Adoption of RPKI Route
> Validation and Filtering", https://arxiv.org/abs/1706.04263. Some of
> this work was also presented at the last RIPE meeting:
> https://ripe74.ripe.net/archives/video/46/
>
>
>
>
> Cheers
>   matthias
>
> -- 
> Matthias Waehlisch
> .  Freie Universitaet Berlin, Computer Science
> .. http://www.cs.fu-berlin.de/~waehl
>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops