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

Russ Housley <housley@vigilsec.com> Sun, 25 February 2024 17:58 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 5582BC14F60B for <sidrops@ietfa.amsl.com>; Sun, 25 Feb 2024 09:58:41 -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=unavailable 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 0XEfPjwnCgSk for <sidrops@ietfa.amsl.com>; Sun, 25 Feb 2024 09:58:37 -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 163F2C14F600 for <sidrops@ietf.org>; Sun, 25 Feb 2024 09:58:37 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 1950CDE8D7; Sun, 25 Feb 2024 12:58:36 -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 EBEDCDF3C4; Sun, 25 Feb 2024 12:58:35 -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: <ZdsNkkdU3E9fkhWS@snel>
Date: Sun, 25 Feb 2024 12:58:25 -0500
Cc: IETF SIDRops <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C0F5B22-432D-4A4A-9D12-E7A3B2B7FEA3@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> <6DA529FA-9F54-4030-BEEB-F08F9551CFD8@vigilsec.com> <ZdsJjqxhTRC6xiFC@snel> <ZdsNkkdU3E9fkhWS@snel>
To: Job Snijders <job=40fastly.com@dmarc.ietf.org>
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=k6P6xLSgEi4LI4SGwOHAxyN9pedsrtiB3JgTqTSCJsI=; b=DrOgrYDHq7zSzaVx3M8tiM0vDjEo7pqJnC50GGhlNOevtcAkdBRTcr5NaBWI+8IN6GRbe09RKzBfnBrq54SN1IIenOgIr0BFtMAEZP8knHQTyREJpug6b5oh6Ay+psk0DItjHX+XuZjG7AeByeWkMY8cRxhOGn+G67BGi0v3DYRj2uTCvu0zOhSsBvZ3sm7rnJfu9EL2DGzOjmlapHgxV2ykZ5idzPOXuS/UKZvTZRhQE85dY/S0sjapUpjEqjGKKHS+W90fwsRVHqxkauZrl131q/1XFHCTu7tbvVMZI+/fb62p39wqMDzvn2M7EqrEMh5+h2ON5ssYRz4/X2FcSQ==
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/pabR307yXS3CCubhiSQwtbwLz-k>
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: Sun, 25 Feb 2024 17:58:41 -0000

Job:

> On Sun, Feb 25, 2024 at 10:34:06AM +0100, Job Snijders wrote:
>> On Sat, Feb 24, 2024 at 03:34:50PM -0500, Russ Housley wrote:
>>>>> 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.
>> 
>> I did interop testing between the APNIC and rpki-client implementations.
>> Back in 2022, Tom Harrison and myself went back and forth a few times to
>> ensure our respective implementations and the draft were all aligned.
>> 
>> I'm not aware of new Signed TAL developments since September 2023 (I
>> think it was around that time the suggestion was brought forward to
>> start a WGLC), but perhaps the draft authors know more than I do?
> 
> Russ, should the SIDROPS chairs not be entirely convinced enough
> implementation work was done to comply with Standards Track
> implementation requirement, the draft's status could be marked as
> "Waiting for Implementation"
> 
>> From https://datatracker.ietf.org/doc/help/state/draft-stream-ietf/
> 
>    """
>    Waiting for Implementation
> 
>    In some areas, it can be desirable to wait for multiple interoperable
>    implementations before progressing a draft to be an RFC, and in some
>    WGs this is required. This state should be entered after WG Last
>    Call has completed.
>    """
> 
> It might be good to hear back from at least one other implementation
> effort.

That is not the situation.  I just want the latest information so that the shepherd write-up can be accurate and complete.

Russ