IETF Logo Mail Archive

[core] Early allocation expiry/renewal (Re: Lars Eggert's Discuss on draft-ietf-core-sid-22: (with DISCUSS and COMMENT))

Carsten Bormann <cabo@tzi.org> Fri, 27 October 2023 21:40 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A004C14CE45; Fri, 27 Oct 2023 14:40:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 PiRb393Xho_N; Fri, 27 Oct 2023 14:40:30 -0700 (PDT)
Received: from smtp.zfn.uni-bremen.de (smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::21]) (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 D5F6FC14F74E; Fri, 27 Oct 2023 14:40:23 -0700 (PDT)
Received: from eduroam-pool10-182.wlan.uni-bremen.de (eduroam-pool10-182.wlan.uni-bremen.de [134.102.90.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4SHGKx31KfzDCds; Fri, 27 Oct 2023 23:40:21 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <169832632311.59761.11389369756506251047@ietfa.amsl.com>
Date: Fri, 27 Oct 2023 23:40:20 +0200
Cc: The IESG <iesg@ietf.org>, draft-ietf-core-sid@ietf.org, core-chairs@ietf.org, core@ietf.org, jaime@iki.fi
X-Mao-Original-Outgoing-Id: 720135620.8910151-2ac122c8bef5734d2239a13d47609ec8
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2330796-E1FB-4BAE-A950-D04472EA4811@tzi.org>
References: <169832632311.59761.11389369756506251047@ietfa.amsl.com>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/CVP0puJDvrlwiok34on9Q-8oKyk>
Subject: [core] Early allocation expiry/renewal (Re: Lars Eggert's Discuss on draft-ietf-core-sid-22: (with DISCUSS and COMMENT))
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2023 21:40:33 -0000

On 2023-10-26, at 15:18, Lars Eggert via Datatracker <noreply@ietf.org> wrote:
> 
> 
> ### Section 6.5.3, paragraph 9
> ```
>     Early Allocations are made with a one-year period, after which they
>     need to be renewed or will expire.
> ```
> In practice, that one year is too short

+1

At most one renewal also is too short.

> and is already creating
> frequent IESG management items for extension approvals. Given the
> many more early allocations, this process will require, this will be
> disruptive for the IESG.

Right, how do we get this fixed?

(The sentence is just a restatement of how BCP100 deals with the timing.)

Grüße, Carsten

v2.23.0 | Report a Bug | By Email