[dd] Charter issue: authority models
Paul Hoffman <paul.hoffman@icann.org> Thu, 21 March 2024 08:28 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 26EEEC1519B8 for <dd@ietfa.amsl.com>; Thu, 21 Mar 2024 01:28:28 -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 dKHyMqleHWgv for <dd@ietfa.amsl.com>; Thu, 21 Mar 2024 01:28:26 -0700 (PDT)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.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 E0B95C1CAF3D for <dd@ietf.org>; Thu, 21 Mar 2024 01:28:25 -0700 (PDT)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa4.dc.icann.org (8.17.1.24/8.17.1.24) with ESMTPS id 42L8SOdH027534 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Mar 2024 01:28:24 -0700
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; Thu, 21 Mar 2024 01:28:23 -0700
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; Thu, 21 Mar 2024 01:28:23 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: Geoff Huston <gih902@gmail.com>
CC: "dd@ietf.org" <dd@ietf.org>
Thread-Topic: Charter issue: authority models
Thread-Index: AQHae2m83ouuKZtUkkS6imI1iqN3Cw==
Date: Thu, 21 Mar 2024 08:28:23 +0000
Message-ID: <5FC2022A-993E-4A42-94DA-F4E62441A28C@icann.org>
References: <49CC837E-4D8E-45CF-A0B5-7A28A82B1939@icann.org> <2CD3FF34-28B7-4A40-A68B-1E20EF4CB6C9@gmail.com>
In-Reply-To: <2CD3FF34-28B7-4A40-A68B-1E20EF4CB6C9@gmail.com>
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: <4A1F7ACD6D7596499B002EA1D8101B33@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-21_05,2024-03-18_03,2023-05-22_02
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/MocFIHHxmUrlW7jo-h4qIZB1Xys>
Subject: [dd] Charter issue: authority models
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 08:28:28 -0000
On Mar 21, 2024, at 18:16, Geoff Huston <gih902@gmail.com> wrote: > 2. The Objectives mention "DNS authoritative signaling mechanisms" and appears to indirectly refer to the first sentence that its the role of the parent to respond with this additional delegation information. So it appears that the charter want to work on _authoritative_ information provided by the parent. I mentioned in the BOF that I thought that the scope should include a study of the nature of authority models that would permit the parnet to provide authoritative information, but I cannot see this in the new wording. Please send text. Would this study be an informational document or standards track? Would it have to be finished before specification work can be started; if so, where would this appear in the ordered list in the Objective and Scope section? --Paul Hoffman
- [dd] Back to the charter Paul Hoffman
- Re: [dd] Back to the charter George Michaelson
- [dd] likely charter issues Geoff Huston
- [dd] Charter issue: resource records Paul Hoffman
- [dd] Charter issue: synchronization between paren… Paul Hoffman
- [dd] Charter issue: authority models Paul Hoffman
- [dd] Charter issue: Introduction of new signaling Paul Hoffman
- Re: [dd] Back to the charter Wes Hardaker
- Re: [dd] Back to the charter George Michaelson
- Re: [dd] Charter issue: Introduction of new signa… Geoff Huston
- Re: [dd] Back to the charter Havard Eidnes
- Re: [dd] Charter issue: synchronization between p… Wes Hardaker
- Re: [dd] Back to the charter Wes Hardaker