Re: [DNSOP] Suffix? (Was: I-D Action: draft-hoffman-dns-terminology-01.txt

"John Levine" <johnl@taugh.com> Fri, 06 March 2015 19:00 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3A011A1BE5 for <dnsop@ietfa.amsl.com>; Fri, 6 Mar 2015 11:00:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.363
X-Spam-Level:
X-Spam-Status: No, score=0.363 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 i3DF0wE1eCLb for <dnsop@ietfa.amsl.com>; Fri, 6 Mar 2015 11:00:16 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61DF31A1BE3 for <dnsop@ietf.org>; Fri, 6 Mar 2015 11:00:16 -0800 (PST)
Received: (qmail 17350 invoked from network); 6 Mar 2015 19:00:11 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 6 Mar 2015 19:00:11 -0000
Date: Fri, 06 Mar 2015 18:59:49 -0000
Message-ID: <20150306185949.21756.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: dnsop@ietf.org
In-Reply-To: <20150306133013.GA29880@nic.fr>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/rSrIesCnO-vQlKqqlrn3mIC9TOE>
Subject: Re: [DNSOP] Suffix? (Was: I-D Action: draft-hoffman-dns-terminology-01.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 06 Mar 2015 19:00:19 -0000

>What about adding a definition of "public suffix"? I suggest the text
>from
><https://code.google.com/p/guava-libraries/wiki/InternetDomainNameExplained>:
>
>> Public suffix: A domain under which people can register subdomains,
>> and on which cookies should not be set. [with good examples
>> afterwards]
>
>This terme seems actually used, unlike the strange FLD
><http://domainnamewire.com/2015/02/18/domain-definitions-fld-for-free-level-domain/>

It's definitely used.  We're spinning up the DBOUND WG to figure out what it actually means
and if there's any way to describe it within the DNS.

The current implementation of public suffixes is a text file one can download from
https://publicsuffix.org/

We all agree that's awful, but there's no agreement about what would be less awful.

I also agree with Vixie that the name is unfortunate, but it's well
established and if we invented some other name, nobody would know what
we were talking about.