Re: [Sidrops] Call for SIDROPS WG Agenda Items

Tim Bruijnzeels <tim@ripe.net> Tue, 27 February 2018 09:35 UTC

Return-Path: <tim@ripe.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 5A329126BF7 for <sidrops@ietfa.amsl.com>; Tue, 27 Feb 2018 01:35:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01, 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 u6u53goVIw3q for <sidrops@ietfa.amsl.com>; Tue, 27 Feb 2018 01:35:19 -0800 (PST)
Received: from mahimahi.ripe.net (mahimahi.ripe.net [IPv6:2001:67c:2e8:11::c100:1372]) (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 85A5D12778D for <sidrops@ietf.org>; Tue, 27 Feb 2018 01:35:19 -0800 (PST)
Received: from nene.ripe.net ([193.0.23.10]) by mahimahi.ripe.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from <tim@ripe.net>) id 1eqbfH-00093y-Ji; Tue, 27 Feb 2018 10:35:16 +0100
Received: from sslvpn.ripe.net ([193.0.20.230] helo=vpn-236.ripe.net) by nene.ripe.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from <tim@ripe.net>) id 1eqbfH-00039Y-F9; Tue, 27 Feb 2018 10:35:15 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Tim Bruijnzeels <tim@ripe.net>
In-Reply-To: <55A96281-2CCD-4D24-9543-6DCD8B6FEB01@arrcus.com>
Date: Tue, 27 Feb 2018 10:34:56 +0100
Cc: SIDR Operations WG <sidrops@ietf.org>, Chris Morrow <morrowc@ops-netman.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1835218-B131-4804-8D98-B95659D4EBCA@ripe.net>
References: <55A96281-2CCD-4D24-9543-6DCD8B6FEB01@arrcus.com>
To: Keyur Patel <keyur@arrcus.com>
X-Mailer: Apple Mail (2.3445.5.20)
X-ACL-Warn: Delaying message
X-RIPE-Spam-Level: -------
X-RIPE-Spam-Report: Spam Total Points: -7.5 points pts rule name description ---- ---------------------- ------------------------------------ -7.5 ALL_TRUSTED Passed through trusted hosts only via SMTP -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain
X-RIPE-Signature: 784d7acfe6559f2a0b602ec6519a0719d3ccda9ad4a6dc36f418da10a338c678
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/KVx8JRpOPTXFUkQ1rpiPUnQFFr4>
Subject: Re: [Sidrops] Call for SIDROPS WG Agenda Items
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: Tue, 27 Feb 2018 09:35:21 -0000

Hi,

I can talk about the following, time permitting - so I would welcome feedback from the WG on what people would be interested in - can be off list as well of course.

= RIPE NCC RPKI Validator 3 architecture

We will have a beta release ready by the IETF.

I can discuss the architecture and differences with version 2.x. In particular we now have asynchronous retrieval of data, so an offline repository does not block validation. And we separated the RPKI-RTR server for redundancy.

If folk are interested I can walk the group through the architecture and algorithm we use.

= Signed TALs

https://tools.ietf.org/html/draft-ietf-sidrops-signed-tal-00

There was some discussion on the list regarding this. The published document builds on plain old TALs, but:
* It has implicit intent and dates
* It does not support unplanned rolls

On list I suggested an XML structure that would allow us to make things explicit and a possible way to also deal with unplanned rolls. I would value feedback on this, and think presenting and discussing on the mic may help.

= HTTPS in TALs

https://tools.ietf.org/html/draft-tbruijnzeels-sidrops-https-tal-00

(Chairs: Adoption call ended on 9 feb)

I can present on this if desired and time permitting. But, since (to me) it seems to be non-controversial, I am also happy to do this on the list, or just have the chairs ask if anyone wants to comment.



> On 26 Feb 2018, at 18:55, Keyur Patel <keyur@arrcus.com> wrote:
> 
> Hi folks,
>  
> SIDROPS will meet at IETF-101 on Thursday, March 22nd from 3:50 pm - 5:50 pm. Please forward any SIDROPS agenda items you may have to Chris and me. Please also make sure that your slides are available to the chairs by Monday morning (3/19/2018). Slides received after the deadline may not be available for use during the meeting.
>  
> Regards,
> Chris and Keyur
>  
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops