[dd] Charter - objectives and scope
Edward Lewis <edward.lewis@icann.org> Thu, 21 March 2024 13:56 UTC
Return-Path: <edward.lewis@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 BFAC5C14F702 for <dd@ietfa.amsl.com>; Thu, 21 Mar 2024 06:56:42 -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 rHsequ6ZKRCu for <dd@ietfa.amsl.com>; Thu, 21 Mar 2024 06:56:37 -0700 (PDT)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.78]) (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 91110C15152D for <dd@ietf.org>; Thu, 21 Mar 2024 06:56:37 -0700 (PDT)
Received: from MBX112-W2-VA-1.pexch112.icann.org (out.mail.icann.org [64.78.48.207]) by ppa3.lax.icann.org (8.17.1.24/8.17.1.24) with ESMTPS id 42LDua6N022505 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <dd@ietf.org>; Thu, 21 Mar 2024 13:56:37 GMT
Received: from MBX112-E2-VA-1.pexch112.icann.org (10.217.41.128) by MBX112-E2-VA-1.pexch112.icann.org (10.217.41.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.28; Thu, 21 Mar 2024 09:56:35 -0400
Received: from MBX112-E2-VA-1.pexch112.icann.org ([10.217.41.128]) by MBX112-E2-VA-1.pexch112.icann.org ([10.217.41.128]) with mapi id 15.02.1258.028; Thu, 21 Mar 2024 09:56:35 -0400
From: Edward Lewis <edward.lewis@icann.org>
To: "dd@ietf.org" <dd@ietf.org>
Thread-Topic: Charter - objectives and scope
Thread-Index: AQHae5eWY4wTAFYBpkST3fUIMuWr9Q==
Date: Thu, 21 Mar 2024 13:56:35 +0000
Message-ID: <0521FB45-FC12-4297-8B17-41053137FF2E@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.65.22091101
x-originating-ip: [192.0.47.234]
x-source-routing-agent: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <07C2D54BB1DF8E4493FF6622C3C025D7@pexch112.icann.org>
Content-Transfer-Encoding: base64
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-21_10,2024-03-18_03,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/hZcAIIvFPYHVhlEvbSi51vknYis>
Subject: [dd] Charter - objectives and scope
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: Thu, 21 Mar 2024 13:56:42 -0000
This time, in-line comments
>To address these challenges, the working group will first develop the requirements for adding a new signaling mechanism that allows parents to return additional DNS delegation information about their children.
>
>The working group will also list the other types of information not available today that might be provided over a designed signaling mechanism.
I would think that the latter item is part of the requirements deliverable.
"The working group will develop a requirements document, documenting the information sufficiently defining a delegation."
>The potential first use cases for the working group will be new DNS authoritative signaling mechanisms for alternative DNS transports, and delegation aliasing (where the parent returns a pointer to the service provider that will then return the needed delegation information). The working group should also consider the how well different solutions can be deployed, and should study possible negative consequences of deploying alternative delegation mechanisms.
"Initial use cases will focus on DNS over transport layers other than the UDP and TCP transports defined in STD 13, as well as accommodation for out-sourced DNS operations. The focus will define alternative delegation mechanisms, plans for deployment of the mechanisms, and consider trade-offs related to the mechanisms."
....I'd keep "negative consequences" out of the charter, as well as undefined terms ("delegation aliasing") and parenthesized comments to define them. It's a charter, not a technical discussion....
>The working group will then define the semantics of a new signaling mechanism, taking future extensibility into account.
From "alternative delegation mechanisms" to " the semantics of a new signaling mechanism"...the terminology seems inconsistent; is this implying the group will study multiple then hammer them in to one consensus pick?
That comment makes me wonder: Is this charter to cover the experimental phase, standardization phase, maintenance phase of this work?
>The working group will specify extensions to the DNS, EPP, and other protocols that relate to delegation. The working group will coordinate with other working groups as appropriate.
- [dd] Charter - objectives and scope Edward Lewis
- Re: [dd] Charter - objectives and scope (long tai… Paul Vixie
- Re: [dd] [Ext] Charter - objectives and scope (lo… Paul Hoffman
- Re: [dd] Charter - objectives and scope Jim Reid
- Re: [dd] Charter - objectives and scope Wes Hardaker
- Re: [dd] Charter - objectives and scope Tim Wicinski
- Re: [dd] Charter - objectives and scope Tim Wicinski
- Re: [dd] Charter - objectives and scope Geoff Huston
- Re: [dd] Charter - objectives and scope Jim Reid
- Re: [dd] Charter - objectives and scope tjw ietf
- Re: [dd] Charter - objectives and scope Wes Hardaker
- Re: [dd] [Ext] Charter - objectives and scope (lo… Paul Vixie
- Re: [dd] [Ext] Charter - objectives and scope (lo… Wes Hardaker