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

Brian Dickson <brian.peter.dickson@gmail.com> Tue, 08 January 2019 00:42 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 DF331130E01 for <dnsop@ietfa.amsl.com>; Mon, 7 Jan 2019 16:42:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 CFjl7mSwOtK3 for <dnsop@ietfa.amsl.com>; Mon, 7 Jan 2019 16:42:36 -0800 (PST)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 3C0C312008A for <dnsop@ietf.org>; Mon, 7 Jan 2019 16:42:36 -0800 (PST)
Received: by mail-qk1-x72a.google.com with SMTP id 189so1404728qkj.8 for <dnsop@ietf.org>; Mon, 07 Jan 2019 16:42:36 -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=Q2TkIKA5PhsXy8jWt41ZTLSA1KWXtiPOW4gjuEVZnKI=; b=KOnPpC7wt6rJqmUe9ei1SFFA+XleWAiHogJC9pQkZBlndEsut3F5Pl4TVmrywmmf8e 8h5qEYv393qzPQEOB9OJl7DxcYoKGFpraVueTJbSl1BOskjq6Zs3AD9Z7yvli34m4OEs 8bHnfUi4nVhqOOY31kLZgXZg3QDNmh0IFet9myEus2yFPd6vp7TCCnIQSZ7JNBc0ByEx atvIZbTYYlX8CzujYRBFztcLzjhJjXhTb/BG3dMmTzFC4SxsNRb/21hyZQ9dABohQSRX stXTZZ6sgvxlpEujoGsOzRJtSHm5qFSyKXdURNjdmD/SvOOIMAIf1x4ZLZpzyzfaEICI oXDw==
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=Q2TkIKA5PhsXy8jWt41ZTLSA1KWXtiPOW4gjuEVZnKI=; b=XrwMecOj+Nm+hHevFL6HmhdyQsr188GwMG787LISE7VSmeYQ8MrMrTjeIaA9y+i3av cvpFJU8Kwb46BqlgkhaMtLzW4QIc9S6a7aRPiQ6ln7ao1PL4NeTlYOoxiRsodGi1fHUl Ota5a2OFuZoyrhTSdaW4xpeL5ZujRlECooDebYs8cbRQx2/rSU+XxbSTjGjQZLTSF0cs tkw87+NGF1kQvvt+EKsCWWGYu8yjs2obO7ySFroUT3l5LCgO9zzjk3urmoeX+hzlkOyv j5NXYCTveXkyB4t/VE28JAUrpRzTEWPr381I6Aeb7D/VSFaxao9c7oFaXJXxLVeSGOAx Y1zg==
X-Gm-Message-State: AJcUukc2ZHmV7zem0eqnJV6oZS+GsDu1+z4mf3c390+LiA46e9Zp74LY Qv1w19xCy4fTbSbHJMb++BbWFynI60KwqcociVc=
X-Google-Smtp-Source: ALg8bN6kMXsJz/oxm6CNLy7K78NskgtoRgU5XZG1jWynwEb76iBYFXSkwmi+3T1FD3nV0JMgfcGyptbj7s+HRfJIqGg=
X-Received: by 2002:a37:bcc1:: with SMTP id m184mr57416754qkf.286.1546908150506; Mon, 07 Jan 2019 16:42:30 -0800 (PST)
MIME-Version: 1.0
References: <0A018ACB-9958-4202-9263-00EA864E2C5C@mnot.net>
In-Reply-To: <0A018ACB-9958-4202-9263-00EA864E2C5C@mnot.net>
From: Brian Dickson <brian.peter.dickson@gmail.com>
Date: Mon, 7 Jan 2019 16:42:19 -0800
Message-ID: <CAH1iCipj0pxP+xD_QSy7CCo4KOPBGKr8Qn4aX5YuJw+E1GV0aA@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cfab2b057ee79e7d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/dDJ2Cw0KCNORmSViTzF651er1P8>
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 00:42:39 -0000

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

> The http (and similar) URIs must rely on some name resolution mechanism(s)
> to interpret the "authority" field and ultimately convert it into a
> transport identifier (e.g. IPv4, IPv6, carrier pigeon).

* If/when* DNS is consulted for resolution of the authority field, directly
> or indirectly, strict adherence to the spirit and text of RFC 6761 is
> required.

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


Hope this helps at least a little.

Brian

On Mon, Jan 7, 2019 at 2:43 PM Mark Nottingham <mnot@mnot.net> wrote:

> Hi DNSOP,
>
> In the HTTPWG, we have an open issue about how to account for .onion in
> HTTP URL processing:
>   https://github.com/httpwg/http-core/issues/10
>
> Our discussion led us to believe we'd do better to have a general
> statement about special-use names when dereferencing HTTP URLs.
>
> It's possible such text might end up here:
>
> https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#http.uri
> .... along with the following section on HTTPS, and of course in Security
> Considerations.
>
> Do folks have thoughts about what it should say, and would any one be
> willing to help?
>
> Cheers,
>
> P.S. I haven't CC'd the HTTP WG to avoid issues with cross-posting; I'll
> point the WG at discussion here.
>
> --
> Mark Nottingham   https://www.mnot.net/
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>