Re: [eppext] launchphase + domain check

"Gould, James" <JGould@verisign.com> Tue, 14 July 2015 12:49 UTC

Return-Path: <JGould@verisign.com>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F8C51AC44A for <eppext@ietfa.amsl.com>; Tue, 14 Jul 2015 05:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 nKJVMvTHBl0z for <eppext@ietfa.amsl.com>; Tue, 14 Jul 2015 05:49:09 -0700 (PDT)
Received: from mail-qg0-f99.google.com (mail-qg0-f99.google.com [209.85.192.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E73E1AC447 for <eppext@ietf.org>; Tue, 14 Jul 2015 05:49:09 -0700 (PDT)
Received: by qgef3 with SMTP id f3so337689qge.0 for <eppext@ietf.org>; Tue, 14 Jul 2015 05:49:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=6o5PFyyTLiCzDuORA4Nrz8xn60r6opx3L5rb0VEI0eQ=; b=DWp5nERD0FtZHou17/ua0XamJUZxNGHyFtihp5IIE+p84+NRacFkXWGlJlGMwg8AWB GK2W+sG+mNFybtSDneSjkQak+tnR844w3mY0CptCn4MsTMgs3/eAG7Zx8W6OmqXgy3J3 1ZgpXUjLw5CEqclzALFeMhBj6es+U72HhCjRkwCmb7+jQ4bW8UJvjzZkOS63yX55aVtB Z8nam+pqQnPjoQFLRIebtyET41q05DIcDXYQul9XpBKmwZsiKTXOd41uVwA3atbOVR59 x1V/pkT1yRf+nQzHrs+w3fcKL3LNGQ5I2+5rY9zABfvkzRVVqcLhy01qaTj1jO4r2jg3 2cjg==
X-Gm-Message-State: ALoCoQnIslbUPQXUvFSjlopxZyb3OaA8gcCdKZ/oAyoughjh7NwNdy8GiIE1wmg8/GTtQQkKCGJhDJARHAWhjf/BLixE8syKMg==
X-Received: by 10.55.41.70 with SMTP id p67mr59660047qkh.25.1436878148444; Tue, 14 Jul 2015 05:49:08 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id r28sm305539qkh.0.2015.07.14.05.49.08 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 14 Jul 2015 05:49:08 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t6ECn68C000336 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Jul 2015 08:49:06 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Tue, 14 Jul 2015 08:49:06 -0400
From: "Gould, James" <JGould@verisign.com>
To: Alexander Mayrhofer <alexander.mayrhofer@nic.at>
Thread-Topic: [eppext] launchphase + domain check
Thread-Index: AdC9f4yDmUkuuNROTTS4w2NzOYoMcQAglH6QABTIAIA=
Date: Tue, 14 Jul 2015 12:49:05 +0000
Message-ID: <A8FAC580-FF73-44C1-9FAA-FA46E86EEFAC@verisign.com>
References: <C80127C588F8F2409E2B535AF968B768BA1E963F@kambx2.SIDN.local> <19F54F2956911544A32543B8A9BDE07546868665@NICS-EXCH2.sbg.nic.at>
In-Reply-To: <19F54F2956911544A32543B8A9BDE07546868665@NICS-EXCH2.sbg.nic.at>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/related; boundary="_004_A8FAC580FF7344C19FAAFA46E86EEFACverisigncom_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/uFAkm8HsumOmN6SOMOFNSJg3s5o>
Cc: Rik Ribbers <rik.ribbers@sidn.nl>, "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] launchphase + domain check
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jul 2015 12:49:12 -0000

We also support the standard check form for all launch phases.  The launchphase draft extends the domain mapping to define new forms of checks targeted for the launch phases, but there is no intent to disallow the use of the standard availability check defined in the domain mapping.


—


JG


[cid:77031CC3-BE7A-4188-A95F-D23115A30A4D@vcorp.ad.vrsn.com]

James Gould
Distinguished Engineer
jgould@Verisign.com

703-948-3271
12061 Bluemont Way
Reston, VA 20190

VerisignInc.com<http://VerisignInc.com>

On Jul 14, 2015, at 2:56 AM, Alexander Mayrhofer <alexander.mayrhofer@nic.at<mailto:alexander.mayrhofer@nic.at>> wrote:

Hello Rik,

We understand that the element MUST only be included by the client when one of the „special“ check forms is used. Therefore, we do allow „vanilla“ EPP domain checks for the whole runtime of the registry, including all “launch phases”.

This also seems what registrars are expecting even during the Claims period, because they usually perform a “normal” check before they attempt a create, and only when that fails, they re-query with the Claims check form..

Alex



Von: EppExt [mailto:eppext-bounces@ietf.org] Im Auftrag von Rik Ribbers
Gesendet: Montag, 13. Juli 2015 17:26
An: eppext@ietf.org<mailto:eppext@ietf.org>
Betreff: [eppext] launchphase + domain check

All,

I've had a very interesting discussion regarding the launchphase draft. The discussion focusses around the domain check and the TMCH claims period. Section 2.3 of the I-D states that:

** quote on **
The server MAY support multiple launch phases sequentially or simultaneously.  The <launch:phase> element MUST be included by the client to define the target launch phase of the command.
** quote off **

So when doing a domain check during a TMCH claims period the domain check in the "Claims check form", "Availability Check Form" and "Trademark Check Form" must contain the <launch:phase> element describing the active phase.

So far so good. But what about the "normal operation" domain check. This is the standard epp domain check (without the launchphase extension). The draft does not explicitly say anything about it, but according to Section 2.3 one could argue that this is not allowed during a TMCH claims period as there is no <launch:phase> element provided.

I would love to here from other WG-members what they think about this...

Kind regards,
Rik Ribbers
_______________________________________________
EppExt mailing list
EppExt@ietf.org<mailto:EppExt@ietf.org>
https://www.ietf.org/mailman/listinfo/eppext