IETF Logo Mail Archive

Re: [DNSOP] Alternative Special-Use TLD problem statement draft

Ted Lemon <Ted.Lemon@nominum.com> Wed, 06 April 2016 13:07 UTC

Return-Path: <Ted.Lemon@nominum.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 233CA12D1B3 for <dnsop@ietfa.amsl.com>; Wed, 6 Apr 2016 06:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=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 6yUK9GNK45Cr for <dnsop@ietfa.amsl.com>; Wed, 6 Apr 2016 06:07:28 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 847E812D50E for <dnsop@ietf.org>; Wed, 6 Apr 2016 06:06:33 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 641D6740058; Wed, 6 Apr 2016 13:06:33 +0000 (UTC)
Received: from mbx-03.WIN.NOMINUM.COM ([169.254.4.19]) by CAS-04.WIN.NOMINUM.COM ([64.89.235.67]) with mapi id 14.03.0224.002; Wed, 6 Apr 2016 06:06:33 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Philip Homburg <pch-dnsop@u-1.phicoh.com>
Thread-Topic: Alternative Special-Use TLD problem statement draft
Thread-Index: AQHRj/uAKDq/juejLUiQAkvVROj43J99UxWA//+WlNY=
Date: Wed, 06 Apr 2016 13:06:32 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630797A445CC@mbx-03.WIN.NOMINUM.COM>
References: <8D23D4052ABE7A4490E77B1A012B630797A44227@mbx-03.WIN.NOMINUM.COM> <m1anlSH-0000IqC@stereo.hq.phicoh.net> <20160406115243.GA14413@laperouse.bortzmeyer.org>, <20160406122131.GA15698@laperouse.bortzmeyer.org>
In-Reply-To: <20160406122131.GA15698@laperouse.bortzmeyer.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [31.130.238.165]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/id5K9Km9FO-baN3hrnkEvUIoyf8>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] Alternative Special-Use TLD problem statement draft
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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, 06 Apr 2016 13:07:34 -0000

> Also, it would make very difficult to DNS programmers to keep track of
> all these "special but not special" domain names. Some people
> complained that it was difficult enough with RFC 6761 (because there
> is no machine-readable version of the special-use registry) but it
> would be worse with scattered domain names in many TLDs.

Yes.  This could be addressed on a protocol level if we used DNS as the resolution protocol of last resort, but if so we need to say how that works.   Again, this would be in a solutions document, not a problem statement document. :)

v2.23.0 | Report a Bug | By Email