Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAH1iCip3C-4YchDLur3AFSmQhzouVdP-VGcbt0F6Sj9dEse3CQ@mail.gmail.com>
Date: Tue, 5 Feb 2019 11:30:50 +1100
Cc: Tony Finch <dot@dotat.at>,
 "dnsop@ietf.org WG" <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <057BE2A8-2F36-4458-AE7A-8FC06ACF7C11@mnot.net>
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>
 <CAH1iCip3C-4YchDLur3AFSmQhzouVdP-VGcbt0F6Sj9dEse3CQ@mail.gmail.com>
To: Brian Dickson <brian.peter.dickson@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/P4VXnhCx0Br32dS22BZHzYlnk3o>
Subject: Re: [DNSOP] Accounting for Special Use Names in Application Protocols
Precedence: list

I've modified that slightly to come up with this proposal:

"""
HTTP and HTTPS URIs rely on some name resolution mechanism(s) to =
interpret the authority field and ultimately convert it into an =
identifier (typically, IPv4 or IPv6 addresses). Often, this is DNS =
[ref].

When DNS is consulted for resolution of the authority field, this =
specification requires adherence to the requirements that all registered =
special use names [RFC6761] place upon applications; if they are not =
honoured, security, privacy and interoperability issues may be =
encountered.
"""

Make sense?

Thanks,


> On 9 Jan 2019, at 1:23 pm, Brian Dickson =
<brian.peter.dickson@gmail.com> wrote:
>=20
>=20
> On Tue, Jan 8, 2019 at 4:21 AM Tony Finch <dot@dotat.at> wrote:
> Brian Dickson <brian.peter.dickson@gmail.com> wrote:
>=20
> > I think it might be good to scope the 6761 issue, with something =
like the
> > following:
>=20
> [SNIP]
>=20
> > > I.e. it is necessary to recognize all special use names, and =
necessary to
> > > not resolve such names via DNS.
>=20
> 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.
>=20
> 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).
>=20
> Brian
>=20
> =20
> 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.
>=20
> Tony.
> --=20
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> Trafalgar: Northeast 3 or 4, increasing 5 at times. Moderate. Fair. =
Good.

--
Mark Nottingham   https://www.mnot.net/