IETF Logo Mail Archive

Re: [DNSOP] Accounting for Special Use Names in Application Protocols

Tony Finch <dot@dotat.at> Tue, 08 January 2019 12:21 UTC

Return-Path: <dot@dotat.at>
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 5260013110D for <dnsop@ietfa.amsl.com>; Tue, 8 Jan 2019 04:21:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 U-VCwc9V87j9 for <dnsop@ietfa.amsl.com>; Tue, 8 Jan 2019 04:21:52 -0800 (PST)
Received: from ppsw-31.csi.cam.ac.uk (ppsw-31.csi.cam.ac.uk [131.111.8.131]) (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 67B5B130DD1 for <dnsop@ietf.org>; Tue, 8 Jan 2019 04:21:52 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://help.uis.cam.ac.uk/email-scanner-virus
Received: from grey.csi.cam.ac.uk ([131.111.57.57]:47042) by ppsw-31.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) id 1ggqOE-0002yy-JU (Exim 4.91) (return-path <dot@dotat.at>); Tue, 08 Jan 2019 12:21:50 +0000
Date: Tue, 08 Jan 2019 12:21:50 +0000
From: Tony Finch <dot@dotat.at>
To: Brian Dickson <brian.peter.dickson@gmail.com>
cc: Mark Nottingham <mnot@mnot.net>, "dnsop@ietf.org WG" <dnsop@ietf.org>
In-Reply-To: <CAH1iCipj0pxP+xD_QSy7CCo4KOPBGKr8Qn4aX5YuJw+E1GV0aA@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1901081213100.3160@grey.csi.cam.ac.uk>
References: <0A018ACB-9958-4202-9263-00EA864E2C5C@mnot.net> <CAH1iCipj0pxP+xD_QSy7CCo4KOPBGKr8Qn4aX5YuJw+E1GV0aA@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Epb3PKjASyE1Za3fGfDSLacaXHY>
Subject: Re: [DNSOP] Accounting for Special Use Names in Application Protocols
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, 08 Jan 2019 12:21:54 -0000

Brian Dickson <brian.peter.dickson@gmail.com> wrote:

> I think it might be good to scope the 6761 issue, with something like the
> following:

[SNIP]

> > I.e. it is necessary to recognize all special use names, and necessary to
> > not resolve such names via DNS.

That's going too far: special-use domain names must have specific
instructions to application authors, which might say not to use the
DNS or might say to use the DNS as usual.

David Schinazi's comment on the GitHub issue about referring to the IANA
registry is good, and perhaps more useful than referring to RFCs directly.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Trafalgar: Northeast 3 or 4, increasing 5 at times. Moderate. Fair. Good.

v2.23.0 | Report a Bug | By Email