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

Brian Dickson <brian.peter.dickson@gmail.com> Wed, 09 January 2019 02:23 UTC

Return-Path: <brian.peter.dickson@gmail.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 41CFA12008A for <dnsop@ietfa.amsl.com>; Tue, 8 Jan 2019 18:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 6npsLQFh6fPd for <dnsop@ietfa.amsl.com>; Tue, 8 Jan 2019 18:23:41 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D42212D7EA for <dnsop@ietf.org>; Tue, 8 Jan 2019 18:23:41 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id y20so6752707qtm.13 for <dnsop@ietf.org>; Tue, 08 Jan 2019 18:23:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nWRnS5MUENM03XhcbHaGwV/1Eok/wwBTVzAunhArF4U=; b=bB2vX4xrCklr2X9T/8evKd3zH8scgq4pgvcSSsRgPUX1UyvxlmZJjKnjreu/baXaom z9mABaJNQiVexdwcsjkR4fON1cj8q0MOwdCvUbUE4gGiJUQbnYPqz57Pjfoqyjs0r8am 7gaB90aPPycPgDbMJOn7HhplAKJobeZK+sbpJjeU1z/sdJjEzByYEMTy5fiSJwhl25x0 /mpKhw7gQJrHyAXOz2GssGO4b87bA17Dlpd1jR2d0t9Em/u4LBWUVIB0EJ32PfvRma+P 6ix+hxWjbWqM4QHrqM5ulHCAjydkd1tSy6oi2L9Exbdd/Kg6xUWUzxSh9X9t7Sa/Q/vr rC/Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nWRnS5MUENM03XhcbHaGwV/1Eok/wwBTVzAunhArF4U=; b=n1CcvkaPNOjWtsJzbis3KJaiMex1OXGaQtsLt/rZkNpqcvkgd08mKDUuJatnmnK8Qk zhCSdRGdVl4DqhMwc8H28DilvesSfn92lmA93IUUxlpaPr39uwoe41WNfiUQOWh0PngF e2+vPWAc+cNZ/0Aq1kgNQIEigpR850ogg2wA0V4d95vZ/FJEYn5IDiq34qdNIcV5FF96 E9GEeOBgdMhymR1VxwTPrjJHcd+HNvgj17Hwn+zkS5z02m3y5OHHZaRGOutTM0yOyDH0 T5/BBknAl+d3oBWCRlBUFgQWpAUDEku9bv0rOtaHRn2lejCuK/b9PPQ82VySDYg/kHMi 4QQw==
X-Gm-Message-State: AJcUukeS5yh/F6wN2ZkH4U6L0FVykmjFZHVxy3mSWnYXBL7i2GadN8kC GSYqzl9/pBotNXKKyc6+PArDzQxJ3jTc7OUKji5/QQ==
X-Google-Smtp-Source: ALg8bN6fvCeAJp5cAkHjarVoj66+Kl6OJ+DWZBvhih9yGj/zeCFqmhnD02x6jedxF1HwfmeYDK2mPhWg0w8Ik637lL4=
X-Received: by 2002:a0c:878d:: with SMTP id 13mr4031579qvj.8.1547000620310; Tue, 08 Jan 2019 18:23:40 -0800 (PST)
MIME-Version: 1.0
References: <0A018ACB-9958-4202-9263-00EA864E2C5C@mnot.net> <CAH1iCipj0pxP+xD_QSy7CCo4KOPBGKr8Qn4aX5YuJw+E1GV0aA@mail.gmail.com> <alpine.DEB.2.20.1901081213100.3160@grey.csi.cam.ac.uk>
In-Reply-To: <alpine.DEB.2.20.1901081213100.3160@grey.csi.cam.ac.uk>
From: Brian Dickson <brian.peter.dickson@gmail.com>
Date: Tue, 8 Jan 2019 18:23:29 -0800
Message-ID: <CAH1iCip3C-4YchDLur3AFSmQhzouVdP-VGcbt0F6Sj9dEse3CQ@mail.gmail.com>
To: Tony Finch <dot@dotat.at>
Cc: Mark Nottingham <mnot@mnot.net>, "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000070e36b057efd26c5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/5ltjav-TNtVdWDfJTPToUQfbQrE>
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: Wed, 09 Jan 2019 02:23:43 -0000

On Tue, Jan 8, 2019 at 4:21 AM Tony Finch <dot@dotat.at>; wrote:

> 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.
>

Hi, Tony,
You are, of course, right. I think what I meant was, for the specific case
of .onion, (what I said),
and for the general case, (what you said). I.e. wherever an RFC for
specific special use name exists,
as linked by the IANA registry, those particular instructions MUST be
followed, especially if not following
those rules might/would break things (like the case of .onion vs DNS).

Brian



> 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.
>