Re: [regext] TLD Phase Discovery
Thomas Corte <Thomas.Corte@knipp.de> Tue, 08 August 2017 15:41 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 E987B1326AD for <regext@ietfa.amsl.com>; Tue, 8 Aug 2017 08:41:43 -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 G8R3uPcY8JCu for <regext@ietfa.amsl.com>; Tue, 8 Aug 2017 08:41:41 -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 A247D132444 for <regext@ietf.org>; Tue, 8 Aug 2017 08:41:41 -0700 (PDT)
Received: from localhost (localhost.bbone.knipp.de [127.0.0.1]) by kmx10a.knipp.de (Postfix) with ESMTP id B051097E9 for <regext@ietf.org>; Tue, 8 Aug 2017 17:41:39 +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 259m5ojRGraO for <regext@ietf.org>; Tue, 8 Aug 2017 17:41:15 +0200 (MESZ)
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx10a.knipp.de (Postfix) with ESMTP id 90A3097E8 for <regext@ietf.org>; Tue, 8 Aug 2017 17:41:14 +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 5E27476CD0 for <regext@ietf.org>; Tue, 8 Aug 2017 17:41:14 +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>
From: Thomas Corte <Thomas.Corte@knipp.de>
Organization: Knipp Medien und Kommunikation
Message-ID: <6a57dbc0-28f3-6c8e-75de-a5cfde47aecb@knipp.de>
Date: Tue, 08 Aug 2017 17:41:16 +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: <71D1C6B2-F9AC-416C-A024-C226B036B52C@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/nShamCcAbgvMiKuLY4qNnpV-EUU>
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 15:41:44 -0000
James, On 2017-08-08 16:25, Gould, James wrote: > Overall, I believe that “phase-agnostic” premium domain names is not > a model that draft-ietf-regext-launchphase is designed for or should > be designed for. I assume you mean "phase-aware". By "phase-agnostic", I meant the opposite, i.e. the model you're proposing - premium domains which are not connected to or dependent on launch phases. > My recommendation is to focus on how > draft-ietf-regext-epp-fees can meet your needs for premium domain > names without coupling it with launch phases as an alternative for > fee classifications. As said in a previous e-mail, a complete refactoring of our premium model seems prohibitively expensive at this juncture, since all our tariff management, promotion infrastructure, registration policy engine code etc. is closely tied to launch phases. We might be able to still retain our use of the fee extension, if only by completely hiding any launch phase related data from it, even if the system still works with launch phases under the hood. If all else fails, we can always use a proprietary extension. Still, and this is going back to the original topic of phase discovery: if it was clearly (as I demonstrated out in a previous e-mail) the intention of the launch phase extension authors to allow multiple phases at the same time, and to make certain domain names only available in certain phases, why should we make it so hard for registrars to discover the right phase for their domain? Why not offer a "phase-avail" check form to discover the phase in which a domain is available, rather than forcing *all* registrars to code their own iteration of <check>s over all known (for some definition of "known") launch phases to discover it? Best regards, Thomas -- ____________________________________________________________________ | | | knipp | Knipp Medien und Kommunikation GmbH ------- Technologiepark Martin-Schmeißer-Weg 9 44227 Dortmund Deutschland Dipl.-Informatiker Tel: +49 231 9703-0 Thomas Corte Fax: +49 231 9703-200 Stellvertretender Leiter SIP: Thomas.Corte@knipp.de Software-Entwicklung E-Mail: Thomas.Corte@knipp.de Registereintrag: Amtsgericht Dortmund, HRB 13728 Geschäftsführer: Dietmar Knipp, Elmar Knipp
- [regext] TLD Phase Discovery Roger D Carney
- Re: [regext] TLD Phase Discovery Gould, James
- Re: [regext] TLD Phase Discovery Patrick Mevzek
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Gould, James
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Gould, James
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Jody Kolker
- Re: [regext] TLD Phase Discovery Jody Kolker
- Re: [regext] TLD Phase Discovery Jody Kolker
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Roger D Carney
- Re: [regext] TLD Phase Discovery Roger D Carney
- Re: [regext] TLD Phase Discovery Jody Kolker
- Re: [regext] TLD Phase Discovery Gould, James
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Gould, James
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Gould, James
- Re: [regext] TLD Phase Discovery Thomas Corte
- Re: [regext] TLD Phase Discovery Gould, James
- Re: [regext] TLD Phase Discovery Gavin Brown
- Re: [regext] TLD Phase Discovery Antoin Verschuren
- Re: [regext] TLD Phase Discovery Gould, James