IETF Logo Mail Archive

Re: [regext] TLD Phase Discovery

Thomas Corte <Thomas.Corte@knipp.de> Mon, 14 August 2017 12:34 UTC

Return-Path: <Thomas.Corte@knipp.de>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 571FB1321AF for <regext@ietfa.amsl.com>; Mon, 14 Aug 2017 05:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 uPj_ImEHYwsV for <regext@ietfa.amsl.com>; Mon, 14 Aug 2017 05:34:31 -0700 (PDT)
Received: from kmx10a.knipp.de (clust3c.bbone.knipp.de [195.253.6.130]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27E5A1321A7 for <regext@ietf.org>; Mon, 14 Aug 2017 05:34:31 -0700 (PDT)
Received: from localhost (localhost.bbone.knipp.de [127.0.0.1]) by kmx10a.knipp.de (Postfix) with ESMTP id 23A3897EC; Mon, 14 Aug 2017 14:34:29 +0200 (MESZ)
X-Knipp-VirusScanned: Yes
Received: from kmx10a.knipp.de ([127.0.0.1]) by localhost (kmx10a.knipp.de [127.0.0.1]) (amavisd-new, port 10004) with ESMTP id F9ZynUDQGJ3F; Mon, 14 Aug 2017 14:34:21 +0200 (MESZ)
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx10a.knipp.de (Postfix) with ESMTP id C6EEE97EA; Mon, 14 Aug 2017 14:34:21 +0200 (MESZ)
Received: from [195.253.2.11] (seth.do.knipp.de [195.253.2.11]) by hp9000.do.knipp.de (Postfix) with ESMTP id 35C7226BB1; Mon, 14 Aug 2017 14:34:21 +0200 (MESZ)
To: regext@ietf.org
References: <8CC3F09A-084F-41A1-9BE7-F44A293BA665@verisign.com> <d4945015-3413-68a4-18ea-ebbb5f28e315@knipp.de> <ED032B40-2895-4124-9755-26879D7FE5A6@verisign.com> <98dcc1e4-3bc4-0499-2f13-fdd73cb42aed@knipp.de> <673DD6EE-36B6-496B-BA7F-499DD09371D3@verisign.com> <44f0fdc8-d665-6179-41b7-855fd41f460d@knipp.de> <SN1PR0201MB1792004419E7E4B6047D4F5DBFB50@SN1PR0201MB1792.namprd02.prod.outlook.com> <301b4b49-c836-b107-7e84-d384f5536f6d@knipp.de> <80F5AA8E-EAC3-4FFA-B9C2-665D2B278727@verisign.com> <8ed43988-5b06-1803-2b76-753b531821c5@knipp.de> <71D1C6B2-F9AC-416C-A024-C226B036B52C@verisign.com> <6a57dbc0-28f3-6c8e-75de-a5cfde47aecb@knipp.de> <8E0A2C5B-595E-43C3-A784-5EFB6FEE806A@verisign.com>
Cc: support@tango-rs.com
From: Thomas Corte <Thomas.Corte@knipp.de>
Message-ID: <94959933-39f0-87c8-7970-7c9f2ed9fb8e@knipp.de>
Date: Mon, 14 Aug 2017 14:34:20 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <8E0A2C5B-595E-43C3-A784-5EFB6FEE806A@verisign.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/bkFLYqRX8QSKgUIhpf9jHLBW0o4>
Subject: Re: [regext] TLD Phase Discovery
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Aug 2017 12:34:33 -0000

James,

On 2017-08-11 19:27, Gould, James wrote:

> launch phases are not meant to be a method of grouping domain
> names like premium domain names.

Says who? As I pointed out in previous e-mails, the launch phase
extension spec's wording

  "Domain names may be made available
   only in unique launch phases, whilst remaining unavailable for
   concurrent launch phases."

clearly suggests otherwise.

Aside from premium domain names, there are other examples where such a
grouping may be necessary, such as when phases are used to introduce new
IDN tables, or to make certain names available only to certain eligible
registrants when a TLD is first launched.
Determining the right phase for a name with a single EPP command should
be possible in such scenarios.

> I view overlapping launch phases as
> a corner case that is already handled by
> draft-ietf-regext-launchphase.

It is, but obviously not in a way that's satisfactory for registrars or
registries. Trial-and-error probing for the right phase isn't a solution
I'd deem suitable.

Best regards,

Thomas

-- 
TANGO REGISTRY SERVICES® is a product of:
Knipp Medien und Kommunikation GmbH
Technologiepark                             Phone: +49 231 9703-222
Martin-Schmeisser-Weg 9                       Fax: +49 231 9703-200
D-44227 Dortmund                       E-Mail: support@tango-rs.com
Germany

v2.23.0 | Report a Bug | By Email