IETF Logo Mail Archive

Re: [dd] [Ext] starting charter text for the DELEG BOF discussion

Paul Hoffman <paul.hoffman@icann.org> Wed, 06 March 2024 15:27 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: dd@ietfa.amsl.com
Delivered-To: dd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E278AC14F5F5 for <dd@ietfa.amsl.com>; Wed, 6 Mar 2024 07:27:53 -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, 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 zVwU6hmGxuD6 for <dd@ietfa.amsl.com>; Wed, 6 Mar 2024 07:27:53 -0800 (PST)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (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 7F35DC14F5EA for <dd@ietf.org>; Wed, 6 Mar 2024 07:27:53 -0800 (PST)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa2.lax.icann.org (8.17.1.24/8.17.1.24) with ESMTPS id 426FRjaD013287 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 6 Mar 2024 15:27:45 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Wed, 6 Mar 2024 07:27:44 -0800
Received: from MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) by MBX112-W2-CO-1.pexch112.icann.org ([169.254.44.235]) with mapi id 15.02.1258.028; Wed, 6 Mar 2024 07:27:44 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: Peter Thomassen <peter@desec.io>
CC: "dd@ietf.org" <dd@ietf.org>
Thread-Topic: [Ext] [dd] starting charter text for the DELEG BOF discussion
Thread-Index: AQHab9rVXvE2ofi/OkyG4Ll+7g1dUA==
Date: Wed, 06 Mar 2024 15:27:44 +0000
Message-ID: <04269D07-1514-4CA3-9AB6-97D84CFB5A0C@icann.org>
References: <yblbk7wl65k.fsf@wx.hardakers.net> <0a7ab12c-62ce-46bc-9afa-973fe944e7c1@desec.io>
In-Reply-To: <0a7ab12c-62ce-46bc-9afa-973fe944e7c1@desec.io>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.0.32.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AD1BFF2BA000E74CAD37694C3EDACE24@pexch112.icann.org>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.272,Aquarius:18.0.1011,Hydra:6.0.619,FMLib:17.11.176.26 definitions=2024-03-06_10,2024-03-05_01,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/13yft69AmHThYH_l0f_kQsk-6DM>
Subject: Re: [dd] [Ext] starting charter text for the DELEG BOF discussion
X-BeenThere: dd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DNS Delegation <dd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dd>, <mailto:dd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dd/>
List-Post: <mailto:dd@ietf.org>
List-Help: <mailto:dd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dd>, <mailto:dd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2024 15:27:54 -0000

On Mar 5, 2024, at 20:31, Peter Thomassen <peter@desec.io> wrote:
> 
> This sounds like there will be exactly 2 RFCs.
> 

... before rechartering. Yes, that was by design. The IESG sometimes (often?) prefers new WGs to initially have a limited work plan with the possibility of later re-chartering.

People on this list know that the list of delegation extension RFCs is likely to be much longer than just aliasing and transport signaling. The question is how to reflect that in the charter.

If this group wants to go with an open work plan, please propose explicit text about that. 

--Paul Hoffman

v2.40.4 | Report a Bug | By Email | System Status