IETF Logo Mail Archive

Re: [Sidrops] WG Adoption call for draft-harrison-sidrops-manifest-numbers-01 - ENDS 04/15/2024 (April 15 2024)

Tim Bruijnzeels <tbruijnzeels@ripe.net> Tue, 02 April 2024 11:46 UTC

Return-Path: <tbruijnzeels@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 8072EC14F6A3 for <sidrops@ietfa.amsl.com>; Tue, 2 Apr 2024 04:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.096
X-Spam-Level:
X-Spam-Status: No, score=-7.096 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=ripe.net
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 FsITXsIYBWYD for <sidrops@ietfa.amsl.com>; Tue, 2 Apr 2024 04:46:12 -0700 (PDT)
Received: from pikapika.ripe.net (pikapika.ripe.net [IPv6:2001:67c:2e8:11::c100:1315]) (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 DCE4BC14F6A4 for <sidrops@ietf.org>; Tue, 2 Apr 2024 04:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ripe.net; s=massmailer20240129; h=To:References:Message-Id:Content-Transfer-Encoding:Cc :Date:In-Reply-To:From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive:List-Unsubscribe-Post; bh=ln3JozJJD7pae1YEj1hJCbILeS10FCqDQYnKddJy0m8=; b=tteUh0VMjc4N8vFp6ikTd7IEBx bDOr+qLK6IbDLqIz4BFsibsVFFe4x0rlxBankr+6YChSWntEmyA6X4GwAUgqqWe/gXjEwiho+jpvr Ox18G1OYJa1qleu5MzwWIHicoHuQyKmVb2vHeQ846DLcY2JXl18JKC0hmSS5aQNzFUPvvyQ170Kz9 w70q0+rTFfxGL6ahi4JINdJmzABx5YujAxF7sqeZljW+/xZzpKizhewb6Vf6sSjiM4whJU7GXAc7P wM2THZzPTaSv3UkSeNmbuF3sqcMPQw7Lr2Wkx9j0VzZG5HNtl0C/IgrY7mRZw+bvz68crn5ZbITSg hMnb7pjA==;
Received: from [2001:67c:2e8:9::c100:14e6] (helo=smtpclient.apple) by pikapika.ripe.net with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from <tbruijnzeels@ripe.net>) id 1rrcag-000000006cc-0cbc; Tue, 02 Apr 2024 11:46:10 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Tim Bruijnzeels <tbruijnzeels@ripe.net>
In-Reply-To: <4744462D-78D9-45EE-B3A2-06FF329EA87C@arrcus.com>
Date: Tue, 02 Apr 2024 13:45:59 +0200
Cc: "sidrops@ietf.org" <sidrops@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A77D691F-57BD-4A00-90E6-E61F257B43EB@ripe.net>
References: <4744462D-78D9-45EE-B3A2-06FF329EA87C@arrcus.com>
To: Keyur Patel <keyur=40arrcus.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/9lhcKzYhWpmcJBSPHe4G9mEttvA>
Subject: Re: [Sidrops] WG Adoption call for draft-harrison-sidrops-manifest-numbers-01 - ENDS 04/15/2024 (April 15 2024)
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: Tue, 02 Apr 2024 11:46:16 -0000

Hi,

I support adoption and discussion.

I understand the issue this seeks to address for TA manifests. I am not 100% convinced yet that the name change is the most desirable way to achieve this. Perhaps it is. An alternative thought would be to allow resetting the manifest number to a low value (or well: 1, but RPs may not see it if another update follows shortly after) in case the number has exceeded some extremely large value (like 2 to the power of 159 ~ 19 octets and 8 bits…). I am not sure yet that this is better either but I am just putting it out here as a thought.

Tim




> On 2 Apr 2024, at 06:31, Keyur Patel <keyur=40arrcus.com@dmarc.ietf.org> wrote:
> 
> Hi Folks,
>  The authors have requested SIDROPS working group adoption call of  “RPKI Manifest Number Handling” https://datatracker.ietf.org/doc/draft-harrison-sidrops-manifest-numbers/.
>  Please send your comments to the list. The adoption call will end on April 15th, 2024.
>  Best Regards,
> Chris, Russ & Keyur
>  _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops

v2.23.0 | Report a Bug | By Email