From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: "Andrew Sullivan" <ajs@anvilwalrusden.com>
Date: Fri, 06 Nov 2015 07:07:39 +0100
Message-ID: <8A3999F3-3771-42DE-A49F-3BA9801697D6@frobbit.se>
In-Reply-To: <20151105044728.GE4292@mx2.yitter.info>
References: <20151105044728.GE4292@mx2.yitter.info>
MIME-Version: 1.0
Content-Type: multipart/signed;
 boundary="=_MailMate_900EE50C-BFC0-4BB6-A744-7AA49CF79C63_=";
 micalg=pgp-sha1; protocol="application/pgp-signature"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/GMOzH6Vyky6iyOwKLWCtByQitA0>
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] My "toxic" remark at the mic today
Precedence: list

This is an OpenPGP/MIME signed message (RFC 3156 and 4880).

--=_MailMate_900EE50C-BFC0-4BB6-A744-7AA49CF79C63_=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 5 Nov 2015, at 5:47, Andrew Sullivan wrote:

> Is
> there a document that says not to put such a record into the root,
> however?  If not, why should DNSOP say anything about this?  It seems
> like a job for SSAC to me.

SSAC wrote about DNAME in March 2006 in SAC-009 ("Alternative TLD Name Sy=
stems and Roots: Conflict, Control and Consequences"):

> Recommendation (1): ICANN and the community at large should take approp=
riate measures to ensure that a thorough analysis of two candidate method=
s for encoding strings in TLD labels - DNAME Equivalence Mappings and use=
 of IDNA encodings =E2=80=93 is concluded quickly. Based on the conclusio=
ns and recommendations of parties responsible for this analysis, ICANN sh=
ould adopt the preferred method.

Unfortunately I can not remind myself that recommendation has been follow=
ed...

On top of this,  SAC-053 ("SSAC Report on Dotless Domains") where SSAC ha=
ve the following recommendation:

> Recommendation: Dotless domains will not be universally reachable and t=
he SSAC recommends strongly against their use. As a result, the SSAC also=
 recommends that the use of DNS resource records such as A, AAAA, and MX =
in the apex of a Top- Level Domain (TLD) be contractually prohibited wher=
e appropriate and strongly discouraged in all cases.

Let me remind people SSAC recommendations do only have weight based on th=
e quality of the report itself. There is no requirement for anyone to fol=
low the recommendations. That said, ICANN Board must take SSAC (and other=
 ICANN AC) advisories and recommendations into account, i.e. at least exp=
lain why the advice was not followed.

   Patrik F=C3=A4ltstr=C3=B6m
   SSAC Chair

--=_MailMate_900EE50C-BFC0-4BB6-A744-7AA49CF79C63_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlY8Q6sACgkQrMabGguI180YEwCfY8JPzMoOOpJB0RbY68eKSftc
r1sAn0ZvSYh4WZwccJKg3JqbVN5yfGm7
=obOy
-----END PGP SIGNATURE-----

--=_MailMate_900EE50C-BFC0-4BB6-A744-7AA49CF79C63_=--