Re: [Sidrops] WG Last Call for draft-ietf-sidrops-signed-tal-14

Russ Housley <housley@vigilsec.com> Sat, 24 February 2024 20:35 UTC

Return-Path: <housley@vigilsec.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 E6C22C14F6A7 for <sidrops@ietfa.amsl.com>; Sat, 24 Feb 2024 12:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=vigilsec.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MTt1DUyWsjn2 for <sidrops@ietfa.amsl.com>; Sat, 24 Feb 2024 12:35:01 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 922BFC14F6A5 for <sidrops@ietf.org>; Sat, 24 Feb 2024 12:35:01 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id E70321764FD; Sat, 24 Feb 2024 15:35:00 -0500 (EST)
Received: from smtpclient.apple (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id C924C176AA8; Sat, 24 Feb 2024 15:35:00 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <197F876A-4E55-47DE-9D88-D15D73829F2E@vigilsec.com>
Date: Sat, 24 Feb 2024 15:34:50 -0500
Cc: IETF SIDRops <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DA529FA-9F54-4030-BEEB-F08F9551CFD8@vigilsec.com>
References: <C61AE8CA-3692-43E0-ACE4-8BB0DEDB6D8B@vigilsec.com> <FBBB194A-4173-4BA1-90B4-300E3F2BD01C@vigilsec.com> <ZckQPu8XZIeQV0lT@snel> <197F876A-4E55-47DE-9D88-D15D73829F2E@vigilsec.com>
To: Job Snijders <job@fastly.com>
X-Mailer: Apple Mail (2.3731.700.6)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vigilsec.com; h=content-type:mime-version:subject:from:in-reply-to:date:cc:content-transfer-encoding:message-id:references:to; s=pair-202402141609; bh=jVQ5gZj92exURO0MQgf1O2NN8OkOyo53sVUiF28c9mU=; b=LOYAb9yCpBDnUHP6Hb2cu37YtOUvHxfLy4tpZfXLcwoutsgK36frgUD6AjVu9oL7/GF/U1SMMsu6aFpyoYd+nOt3vV3bmjFJl5CGoBZm7pcvyyEgR0WqUQ/8cRRSFxIDIojN1xSqY2cv0KpfIPZt1r9eNGUmG1mJ9Pxt9yW0oBkvrWB6+ImRrPo4V/k6VMKL0mXyD9RGdjGeI9bU5jpS9N/rlt8D/0iBOoNhb6025i4+zq1PCS2KeBFtGEGIzs98AwKZo0e5MZTNWn64EWox9QQ782zNh+LJmnGzUTNLjldeKp8yWAvaXfCVOr5oR4w1s6ZYjTzCIlqI5xjsPCCkzw==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/5W9-xNxycg4mVBx6OdJ4kmagIOM>
Subject: Re: [Sidrops] WG Last Call for draft-ietf-sidrops-signed-tal-14
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 24 Feb 2024 20:35:06 -0000

Job:

>>> Title: RPKI Signed Object for Trust Anchor Key
>>> 
>>> Authors: C. Martinez, G. Michaelson, T. Harrison, T. Bruijnzeels, and R. Austein
>>> 
>>> Datatracker: https://datatracker.ietf.org/doc/draft-ietf-sidrops-signed-tal/
>>> 
>>> Should the SIDRops WG ask the IESG to publish this document as a
>>> Standards-Track RFC?  Please respond to this WG Last Call by 23
>>> February 2024.
>> 
>> I support progressing this document to the IESG.
>> 
>> Through implementation of the concept in this internet-draft, Trust
>> Anchor Operators and Relying Parties have a standardized way to
>> communicate and receive information about new TALs in a signed fashion.
>> This seems useful.
>> 
>> Some time ago I implemented support for validating Signed TAL (.tak)
>> objects in OpenBSD's rpki-client validator. I found the availability of
>> a testbed as provided by the authors of this document very helpful. 
> 
> Are you aware of any other implementations?  Did you do interoperability testing.  This information will be useful for the shepherd write-up.

I should have also said that I am aware of the information of Section 13 of the draft.  I am asking whether there is anything additional since the draft was published in September 2023.

Russ