IETF Logo Mail Archive

Re: [Add] IESG evaluation of draft-ietf-add-svcb-dns and draft-ietf-add-ddr / draft-ietf-add-dnr

Tommy Pauly <tpauly@apple.com> Tue, 09 August 2022 15:40 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3590AC14CF17; Tue, 9 Aug 2022 08:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.687
X-Spam-Level:
X-Spam-Status: No, score=-2.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.582, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=apple.com
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 1y0Blxxpbt13; Tue, 9 Aug 2022 08:40:37 -0700 (PDT)
Received: from rn-mailsvcp-ppex-lapp44.apple.com (rn-mailsvcp-ppex-lapp44.rno.apple.com [17.179.253.48]) (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 80036C14792A; Tue, 9 Aug 2022 08:40:37 -0700 (PDT)
Received: from pps.filterd (rn-mailsvcp-ppex-lapp44.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp44.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 279FeZ03006631; Tue, 9 Aug 2022 08:40:36 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=u5JVlDj+7EHythyV4e/69BuiDLEb2nzjN+hdwVMxq30=; b=jRy5zoUSBgpqjPwL6/S654+OoQJgjhD5dUs2eTRbZYHbW4u+Se3GGUKR1tWLn7PBhR2X EXZl0kaGST1vW2pp6P+JnbKe/RGQydVOVMdhBZ06825/TMz0QDmbqoO8cx/g5j1tWm9Y ihbioXltOxhExq4q0W/+2bddoEKTJoAx3C3yRsWPNP10P8QLHM/YhmFbK97akdRaxwtv BvE/0DKPtvL5jNjKGl3ZzJM3Bo/sqgx0GG3uaubH7f+bOY8gIMRmhM9RLJiIRCwcQp01 LMI6mJW+aU7EN34r64m7ZtT0fUNE6tw4XMZv7+fsc6Od4R40HeTumiPW29LkUNDY+kHR 8w==
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by rn-mailsvcp-ppex-lapp44.rno.apple.com with ESMTP id 3hskt8q3gk-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 09 Aug 2022 08:40:36 -0700
Received: from rn-mailsvcp-mmp-lapp04.rno.apple.com (rn-mailsvcp-mmp-lapp04.rno.apple.com [17.179.253.17]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPS id <0RGC01183U7MGYB0@rn-mailsvcp-mta-lapp02.rno.apple.com>; Tue, 09 Aug 2022 08:40:35 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp04.rno.apple.com by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) id <0RGC00500TQE1500@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Tue, 09 Aug 2022 08:40:34 -0700 (PDT)
X-Va-A:
X-Va-T-CD: d961ed54a37a0e7c98140a093d4f1762
X-Va-E-CD: 767269b6e5108fbd8f745b0be2cbee2b
X-Va-R-CD: 4ca5ad849499edeb8bd030655825a651
X-Va-CD: 0
X-Va-ID: ef809dfd-d4cd-4fbc-bd48-c64ab7305a0d
X-V-A:
X-V-T-CD: d961ed54a37a0e7c98140a093d4f1762
X-V-E-CD: 767269b6e5108fbd8f745b0be2cbee2b
X-V-R-CD: 4ca5ad849499edeb8bd030655825a651
X-V-CD: 0
X-V-ID: 6b5c64ab-a59c-4b4f-800f-3f4ac0181a54
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517, 18.0.883 definitions=2022-08-09_02:2022-08-09, 2022-08-09 signatures=0
Received: from smtpclient.apple (unknown [17.192.171.223]) by rn-mailsvcp-mmp-lapp04.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPSA id <0RGC008D7U68A000@rn-mailsvcp-mmp-lapp04.rno.apple.com>; Tue, 09 Aug 2022 08:40:33 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <860FC48B-EACB-4B5B-B8ED-60793CAE6A8B@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_0D4C2099-C5BF-46CD-A513-F17E0FA7E1F7"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3696.120.31\))
Date: Tue, 09 Aug 2022 08:40:32 -0700
In-reply-to: <5953F673-1E01-4AB8-B4BD-04AD105C9C5D@cisco.com>
Cc: "add@ietf.org" <add@ietf.org>
To: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>
References: <5953F673-1E01-4AB8-B4BD-04AD105C9C5D@cisco.com>
X-Mailer: Apple Mail (2.3696.120.31)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517, 18.0.883 definitions=2022-08-09_02:2022-08-09, 2022-08-09 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/numFIyGTTDkSXLkY0MC4PL8HPqA>
Subject: Re: [Add] IESG evaluation of draft-ietf-add-svcb-dns and draft-ietf-add-ddr / draft-ietf-add-dnr
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2022 15:40:38 -0000

Hi Eric,

The -10 version of DDR is the latest and contains all of the previously outstanding changes.

Thanks,
Tommy

> On Aug 9, 2022, at 1:55 AM, Eric Vyncke (evyncke) <evyncke=40cisco.com@dmarc.ietf.org> wrote:
> 
> As you probably have seen by now, Paul Wouters has changed his blocking DISCUSS positions on DDR/DNR into a non-blocking ABSTAIN position [2]. This clears the path towards publication.
>  
> Alas, the DNR ballot still lacks a YES/NO OBJECTION position (i.e., the ‘quorum’ was not reached). I have sent an email to the remaining of the IESG asking them to review DNR and ballot. This may happen in the coming days.
>  
> May I also request the authors to confirm that the I-Ds in the data tracker are their latest ones ? I.e., they are ready to go for publication.
>  
> Regards,
>  
> -éric
>  
> [2] https://www.ietf.org/about/groups/iesg/statements/iesg-discuss-criteria/#no <https://www.ietf.org/about/groups/iesg/statements/iesg-discuss-criteria/#no>
>  
> From: Add <add-bounces@ietf.org> on behalf of "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>
> Date: Monday, 8 August 2022 at 10:05
> To: "add@ietf.org" <add@ietf.org>
> Subject: [Add] IESG evaluation of draft-ietf-add-svcb-dns and draft-ietf-add-ddr / draft-ietf-add-dnr
>  
> Dear ADD members,
>  
> As you have probably seen by now, draft-ietf-add-svcb-dns is ready to go to the RFC editor queue, but as the DDR & DNR I-Ds have a normative reference to it and have still a DISCUSS, I prefer to delay the approval of the SVCB document until the DDR & DNR can also be approved.
>  
> My reasoning is that *if* a revised DDR / DNR require a change in the SVCB, then there is still an opportunity to do minor changes in the SVCB document. The probability is low, but the delay is probably harmless[1]. Happy to change my point of view if the authors and the ADD WG think differently.
>  
> Regards
>  
> -éric
>  
> [1] now, if either DDR or DNR are delayed by more than 3 months, then let’s approve the SVCB.
> -- 
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add

v2.23.0 | Report a Bug | By Email