Re: [regext] TLD Phase Discovery

Thomas Corte <Thomas.Corte@knipp.de> Tue, 08 August 2017 09:11 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 15A0E132194 for <regext@ietfa.amsl.com>; Tue, 8 Aug 2017 02:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] 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 n6nnq6tnrlxm for <regext@ietfa.amsl.com>; Tue, 8 Aug 2017 02:11:43 -0700 (PDT)
Received: from kmx10a.knipp.de (clust3b.bbone.knipp.de [195.253.6.85]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21482132191 for <regext@ietf.org>; Tue, 8 Aug 2017 02:11:42 -0700 (PDT)
Received: from localhost (localhost.bbone.knipp.de [127.0.0.1]) by kmx10a.knipp.de (Postfix) with ESMTP id 25F9997D8; Tue, 8 Aug 2017 11:11:41 +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 0Opzari66ED7; Tue, 8 Aug 2017 11:11:28 +0200 (MESZ)
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx10a.knipp.de (Postfix) with ESMTP id AFEA997D4; Tue, 8 Aug 2017 11:11:22 +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 91DB476C88; Tue, 8 Aug 2017 11:11:22 +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>
Cc: support@tango-rs.com
From: Thomas Corte <Thomas.Corte@knipp.de>
Message-ID: <8ed43988-5b06-1803-2b76-753b531821c5@knipp.de>
Date: Tue, 08 Aug 2017 11:11:24 +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: <80F5AA8E-EAC3-4FFA-B9C2-665D2B278727@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/Auu8jCNYO7Xk0SxZPIeqeEAVunM>
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: Tue, 08 Aug 2017 09:11:45 -0000

Hello James,

On 2017-08-07 20:55, Gould, James wrote:

> Use of the phase and sub-phase as a mechanism for clients to indicate
> fee or domain grouping categories was not the intent in
> draft-ietf-regext-launchphase.  At the IETF-98 REGEXT WG meeting it
> was unclear when there would be overlapping launch phases.

I think that the launch phase draft itself provides a use case. One of
the examples for the availability check form contains the custom phase
name "idn-release", which most likely refers to a registry introducing a
new set of IDN tables (which may happen years after the TLD initially
launched), making new domains available which were previously not
available, potentially at a different price and most likely with a
different registration model, i.e. as applications rather than immediate
registrations. Such an "idn-release" phase would most likely be run in
parallel to a (perpetually running) "open" phase for ordinary domain names.

> The launch
> phase and sub-phase is meant to cover the launch of the TLD itself,
> where your overlapping phases does not apply to the TLD but to groups
> of domains within the TLD.

The IDN rollout depicted above contains a use case (which as obviously
anticipated by the launch phase draft authors) where groups of domains
are available in different phases.

> I believe use of
> draft-ietf-regext-epp-fees is the appropriate path forward for the
> grouping of premium domains and not use of phases and sub-phases in
> draft-ietf-regext-launchphase.  If you fully transition to leverage
> draft-ietf-regext-epp-fees for premium domain grouping, do you have
> any need for overlapping launch phases in
> draft-ietf-regext-launchphase, and if so please describe why?

A need for overlapping launch phases might always arise, see above.
Also, nowhere in the launch phase extension draft has the use of
overlapping launch phases been excluded or forbidden. On the contrary,
at one point it is explicitly mentioned that "Domain names may be made
available only in unique launch phases, whilst remaining unavailable for
 concurrent launch phases.".

Of course, a "phase-agnostic" implementation of premium domain names is
possible and can indeed be accomplished with the fee extension as it is
currently drafted.
That said, the refactoring efforts involved to migrate a registry system
like ours which has been designed in a phase-centric way are
non-negligible. As it currently stands, I'd rather try to stretch the
interpretation of the launch phase/fee extension specs in order to make
them work with our model if need be. That's why I'd rather see the specs
offering a clean solution for our model than forcing us to work around them.

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