Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-alt-tld-21.txt
Paul Hoffman <paul.hoffman@icann.org> Fri, 24 February 2023 23:10 UTC
Return-Path: <paul.hoffman@icann.org>
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 8E718C14CE3D; Fri, 24 Feb 2023 15:10:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 VywEyYDo-1Bb; Fri, 24 Feb 2023 15:10:31 -0800 (PST)
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 62101C14F72F; Fri, 24 Feb 2023 15:10:31 -0800 (PST)
Received: from MBX112-W2-CO-2.pexch112.icann.org (out.mail.icann.org [64.78.33.6]) by ppa3.lax.icann.org (8.17.1.19/8.17.1.19) with ESMTPS id 31ONAUv3016104 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 24 Feb 2023 23:10:30 GMT
Received: from MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) by MBX112-W2-CO-1.pexch112.icann.org (10.226.41.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1118.21; Fri, 24 Feb 2023 15:10:29 -0800
Received: from MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) by MBX112-W2-CO-1.pexch112.icann.org ([10.226.41.128]) with mapi id 15.02.1118.021; Fri, 24 Feb 2023 15:10:29 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: "Wessels, Duane" <dwessels=40verisign.com@dmarc.ietf.org>
CC: dnsop <dnsop@ietf.org>
Thread-Topic: [Ext] [DNSOP] I-D Action: draft-ietf-dnsop-alt-tld-21.txt
Thread-Index: AQHZSKUvgBDFOWpQ2UuDIo8QZVt+uw==
Date: Fri, 24 Feb 2023 23:10:29 +0000
Message-ID: <8B4A7E42-E74A-4A4B-B077-5ABD38B41C12@icann.org>
References: <167726416831.59298.15396594347656317096@ietfa.amsl.com> <77441FD5-FF56-4645-90AC-A97EFC987F8D@verisign.com>
In-Reply-To: <77441FD5-FF56-4645-90AC-A97EFC987F8D@verisign.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="utf-8"
Content-ID: <3466387E68A3634BABB4F8ABFF9AF84A@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.219,Aquarius:18.0.930,Hydra:6.0.562,FMLib:17.11.170.22 definitions=2023-02-24_16,2023-02-24_01,2023-02-09_01
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/JvVQqpU3_H4orf6wRsBr9GouqdU>
Subject: Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-alt-tld-21.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 24 Feb 2023 23:10:33 -0000
On Feb 24, 2023, at 2:41 PM, Wessels, Duane <dwessels=40verisign.com@dmarc.ietf.org> wrote: > > Thank you authors for the update which addressed my concern about formatting of the special use considerations as an enumerated list. You weren't the only one who brow-beat us about that... > Forgive me if I am being difficult, but I feel that the first sentence of the privacy section, which says “... so should not attempt to be resolved using the global DNS” is in contradiction with #4 which says "and SHOULD NOT perform any special handling”, and to some extent #3 which says "Regular DNS resolution APIs and libraries are not expected to recognize or treat names in the .alt pseudo-TLD differently”. > > Given the wording of the considerations in section 3.2, maybe just delete “, and so...” from that sentence in the privacy section? Good catch! Yes, definitely. Will fix in -22. --Paul Hoffman
- [DNSOP] I-D Action: draft-ietf-dnsop-alt-tld-21.t… internet-drafts
- Re: [DNSOP] I-D Action: draft-ietf-dnsop-alt-tld-… Wessels, Duane
- Re: [DNSOP] [Ext] I-D Action: draft-ietf-dnsop-al… Paul Hoffman