IETF Logo Mail Archive

Re: [DNSOP] IANA Policy for SVCB

Tommy Pauly <tpauly@apple.com> Tue, 22 March 2022 18:29 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD80A3A0F74 for <dnsop@ietfa.amsl.com>; Tue, 22 Mar 2022 11:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HWluV9mfz4zm for <dnsop@ietfa.amsl.com>; Tue, 22 Mar 2022 11:29:51 -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 354473A0F42 for <dnsop@ietf.org>; Tue, 22 Mar 2022 11:29:51 -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 22MIEvhS020328; Tue, 22 Mar 2022 11:29:45 -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=XRnjS7D3JNrqsA/+PFpd58fkUPxvTPhoM4CFXW0ZpaQ=; b=BtPH9/Z+oQpJpRXIm+fOVsG3oS8yU/MDmiwBJJL3ZmC9MtgBjBcLd5zZCKH7CQxZNjz6 ReDN8f2Lf0qrLjSKM7Sy/loRgAfTyRFrH2pf0+CTsRexNRfH7BFLAPGtmTGqBzssG4Po rzSg/DJMG3MVpLs8vQYVwH5wujaNIPjN9XQwNldpfBA8Jfz5Pn3m9f4B69CnK7OdVEI6 ozllUrkxkPfAPkZWkck30nfNTWAQ05fg69xbIKCWFEv4kI6HU8u18DFhsh8QzQia7JrF dRjHlXRG06EV+IjiaFeYw3qh8KtjVxHmX8KSSx5QZ8Pd1tnWBX0IoRm1ustcbBO7rBo5 cw==
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 3ewap77xn0-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 22 Mar 2022 11:29:45 -0700
Received: from rn-mailsvcp-mmp-lapp01.rno.apple.com (rn-mailsvcp-mmp-lapp01.rno.apple.com [17.179.253.14]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) with ESMTPS id <0R9500XQCSPLZB50@rn-mailsvcp-mta-lapp02.rno.apple.com>; Tue, 22 Mar 2022 11:29:45 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp01.rno.apple.com by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) id <0R9500X00SOOHF00@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Tue, 22 Mar 2022 11:29:45 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 9af4f3cab97292f02d929d3c7735f3b4
X-Va-E-CD: fab62b05005cd820e61fe8f6e8b2188d
X-Va-R-CD: 93d5c11e4178a24962737e8618672f89
X-Va-CD: 0
X-Va-ID: e088c3bf-d6bb-4cae-918c-4045f3df7eaf
X-V-A:
X-V-T-CD: 9af4f3cab97292f02d929d3c7735f3b4
X-V-E-CD: fab62b05005cd820e61fe8f6e8b2188d
X-V-R-CD: 93d5c11e4178a24962737e8618672f89
X-V-CD: 0
X-V-ID: 8b1519f7-2987-4d08-b935-ac2abb8ed5fb
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.850 definitions=2022-03-22_07:2022-03-22, 2022-03-22 signatures=0
Received: from smtpclient.apple (unknown [17.11.113.222]) by rn-mailsvcp-mmp-lapp01.rno.apple.com (Oracle Communications Messaging Server 8.1.0.16.20220118 64bit (built Jan 18 2022)) with ESMTPSA id <0R95006DZSPK5400@rn-mailsvcp-mmp-lapp01.rno.apple.com>; Tue, 22 Mar 2022 11:29:44 -0700 (PDT)
From: Tommy Pauly <tpauly@apple.com>
Message-id: <C7035F89-FC37-4EA2-9A79-275E573D789E@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_0AEC22E2-B955-4595-AC00-66FF8624BEE4"
MIME-version: 1.0 (Mac OS X Mail 15.0 \(3691.0.3\))
Date: Tue, 22 Mar 2022 11:29:44 -0700
In-reply-to: <CAL0qLwZoRWwNB-0DjwWjWw7CJ0qmbVk3RkseRxC3BEC3f3t8QA@mail.gmail.com>
Cc: Ray Bellis <ray@bellis.me.uk>, "dnsop@ietf.org WG" <dnsop@ietf.org>
To: "Murray S. Kucherawy" <superuser@gmail.com>
References: <CAHbrMsB5Lhm+cUoEzXwwKn74pBCrAOB+wnJG8ATscxkh7zSvLQ@mail.gmail.com> <CAL0qLwY11Z32q2+Co1Gsn=t7mgZOT6gfx6saXuNQTJ8nhK4nvg@mail.gmail.com> <66256ce9-bb9f-4534-87ff-c589566db395@www.fastmail.com> <CAL0qLwaXuXA9SC4vv8wJ025mSwgq0ontC7ACVFo_APE-fWbN-Q@mail.gmail.com> <79e252e5-6aae-5dca-2d49-3ee6aa85f558@bellis.me.uk> <CAL0qLwZoRWwNB-0DjwWjWw7CJ0qmbVk3RkseRxC3BEC3f3t8QA@mail.gmail.com>
X-Mailer: Apple Mail (2.3691.0.3)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.425, 18.0.850 definitions=2022-03-22_07:2022-03-22, 2022-03-22 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_WGsEzb3hUlPgFJSEjmPH6O5CmM>
Subject: Re: [DNSOP] IANA Policy for SVCB
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2022 18:29:56 -0000

If this space is not extensible from non-IETF RFCs, we’ll have missed the mark. The space is designed to be large (65K) to allow new work to easily use this extensibility. We don’t need to be too conservative with this space.

I disagree that there wouldn’t be good experts — we have authors of the document who have seen it through, and we have more people using this RR and gaining expertise.

Expert review is the right balance here.

Tommy

> On Mar 22, 2022, at 9:24 AM, Murray S. Kucherawy <superuser@gmail.com> wrote:
> 
> On Tue, Mar 22, 2022 at 9:10 AM Ray Bellis <ray@bellis.me.uk <mailto:ray@bellis.me.uk>> wrote:
> I am concerned that the set of Expert Reviewers necessary to handle SVCB 
> needs to have both expert DNS experience *and* detailed knowledge of the 
> SVCB model for this to work.
> 
> I am not sure there's anybody who fits that criteria.
> 
> Specification Required also assumes a community that can produce them, which presumably contains the right experts.
> 
> Are we actually moving toward IETF Review here?
> 
> -MSK
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

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