[dd] IAB BoF report: Deleg
"Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net> Thu, 21 March 2024 21:32 UTC
Return-Path: <ietf@kuehlewind.net>
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 3AC90C14F6BA; Thu, 21 Mar 2024 14:32:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=kuehlewind.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 b7X9iNJcLY0c; Thu, 21 Mar 2024 14:32:44 -0700 (PDT)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [80.237.130.35]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01DA7C14F6B8; Thu, 21 Mar 2024 14:32:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kuehlewind.net; s=he234030; h=To:Cc:Date:Message-Id:Subject:Mime-Version: Content-Type:From:From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc: MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=YVsUxAnRf6MTMcLy5qiSkk1jCDThbhiSu6iLY4wpLJs=; t=1711056764; x=1711488764; b=QkE9RDHK8ySJwnS7/iQU3iDoD7kv0FzWPGrLxXFmsv1NMEV1Jo3nrnHsLyULXm/6871jO0KSWf BrS/+bLC85g3FUOzEfiJkV0Mv7G81w/NrFqcCcvWCmvEKgWnXblQuJebTGAXun6dsgb3BBITCDsSj cYmovfg8zhIJeqBpBqEtAkWnFoCc17/ygDyzZHsHA1VCi2i+xrBqP9fOHakH12wCCZKUm6W1DHoC/ 9L8tvLx7ITBdzcJhw4npi7J3SznJ25eipcVRQoyqgK8nftV5TTfBlCVHgFlgzhDrRuED0JO4XrHSA /9nBVhUKgnYZWNvhgNzLqxjYqT/wfUbsy9B5g==;
Received: from [2001:67c:1232:144:c996:ebf3:3cc9:d0b3] (helo=smtpclient.apple); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1rnQ1h-00023K-GH; Thu, 21 Mar 2024 22:32:42 +0100
From: "Mirja Kuehlewind (IETF)" <ietf@kuehlewind.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F7C91B21-BD54-41D3-BEF5-6E412B4EE9EB"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Message-Id: <20E5939C-7451-4D4A-90E4-681B4CE3766C@kuehlewind.net>
Date: Thu, 21 Mar 2024 22:31:14 +0100
Cc: IAB IAB <iab@iab.org>, dd@ietf.org
To: The IESG <iesg@ietf.org>
X-Mailer: Apple Mail (2.3731.700.6)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1711056764;00dc9ef8;
X-HE-SMSGID: 1rnQ1h-00023K-GH
Archived-At: <https://mailarchive.ietf.org/arch/msg/dd/P6o9uxu836XEiDK-uHFezZ1mVYM>
Subject: [dd] IAB BoF report: Deleg
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 21:32:48 -0000
Hi IESG, hi all,
The delegation BoF went very smoothly and was well prepared and run. It seems, other than potentially expected, that most people in the room were generally positive about the work and there is quite broad interest on contributing to the work.
The session started with some short statements on reasons why better delegation is needed. While people were generally positive about doing work in this space, a couple of people however also raised concerns about unintended consequences of the deployment as potentially performance degradation. Therefore it was seen, at least by some people in the room, as critical to reach out to registrars and other people in the ecosystem that are interested in deploying or may be impacted by the deployment. Another concern raised was about backward compatibility.
The largest part of the session was spend on discussing the proposed charter text and scope. This led to a couple of needed changes and there might still be some open questions mostly about the broadness of the scope. While some people in the group thought this work would create a new model for DNS, others see the proposed work rather as a small extension and preferred a tight focus. DBOUND was discussed as a failure, that should not be repeated, as the scope was too broad. Specifically, the charter proposes to focus on one use case first, however, it was not fully clear if everybody in the room agreed to which one should be picked first, however there is quite broad interest in singling protocol support especially for encrypted protocol (but not potentially not only). The discussion was a bit mixed between high-level considerations, like the notion of a new model with broad impact on DNS, and very detailed word-smithing level comments.
The discussion about deliverables indicated that the documents and question of which document should be published with consensus needs further clarification. Specifically there was discussion about the requirements, as well as if use cases, the new model and deployment consideration should be included and worked on first. Potentially additional technical deliverables might be needed as well or at least the scope and split of the proposed deliverables wasn’t fully clear in the proposed charter text. Some people will send proposals to the list but it is not fully clear if there is a common view between those interested in the work (yet).
At their end there was some time to discuss the BoF questions. Rather can asking the question, there were comments at the mic line that summarised that it became clear from the room discussion that there is a problem to solve and there is interest. Given there was more time, based on my request, the BoF question "Is the scope discussed today clear enough to ask the IESG for a WG?" was asked and let to a non-conclusive result (28 Yes, 21 No, 10 No Opinion). Therefore the chairs ask second question talking into account that more work on the proposed charter is needed which was answered positively ("Do you think we can work on the ML to get a scope that is clear enough?" 45 Yes, 1 No, 2 no opinion). My conclusion from that is that most/all people in the room were interested and positive about the work but there are different views about how broad the work should be chartered, from developing a new model for DNS to focus on one use case only with a small extension. However, given the very constructive and well guided discussion in the room, I believe this can be resolved by mailing list discussion.
Mirja
- [dd] IAB BoF report: Deleg Mirja Kuehlewind (IETF)