Re: [eppext] draft-ietf-eppext-launchphase Support for a "Claims Service" post the Claims Phase
"Gould, James" <JGould@verisign.com> Thu, 08 January 2015 19:35 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 0A5B61A9081
for <eppext@ietfa.amsl.com>; Thu, 8 Jan 2015 11:35:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level:
X-Spam-Status: No, score=-3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
HTML_MESSAGE=0.001, J_CHICKENPOX_64=0.6, J_CHICKENPOX_65=0.6,
RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 2-ASdgcDGRPe for <eppext@ietfa.amsl.com>;
Thu, 8 Jan 2015 11:35:23 -0800 (PST)
Received: from exprod6og111.obsmtp.com (exprod6og111.obsmtp.com [64.18.1.27])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 6600D1A9087
for <eppext@ietf.org>; Thu, 8 Jan 2015 11:35:20 -0800 (PST)
Received: from brn1lxmailout01.verisign.com ([72.13.63.41]) (using TLSv1) by
exprod6ob111.postini.com ([64.18.5.12]) with SMTP
ID DSNKVK7b97lXfdAd5+sujcAEpjgmtgBSpM86@postini.com;
Thu, 08 Jan 2015 11:35:23 PST
Received: from brn1wnexcas01.vcorp.ad.vrsn.com
(brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205])
by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t08JZIsM007226
(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL);
Thu, 8 Jan 2015 14:35:18 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by
brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Thu, 8
Jan 2015 14:35:17 -0500
From: "Gould, James" <JGould@verisign.com>
To: Francisco Obispo <fobispo@uniregistry.com>
Thread-Topic: [eppext] draft-ietf-eppext-launchphase Support for a "Claims
Service" post the Claims Phase
Thread-Index: AQHQK2YwQl5JVElI9UChfyCYUoIA/Jy20n+AgAAe+YA=
Date: Thu, 8 Jan 2015 19:35:17 +0000
Message-ID: <B392E842-86BF-4F1E-96FC-ED2EA7E19F6D@verisign.com>
References: <D0D41AB9.46E54%trung.tran@neustar.biz>
<64BB8C0B-ED45-4384-AC10-BC0E5206E26E@uniregistry.com>
In-Reply-To: <64BB8C0B-ED45-4384-AC10-BC0E5206E26E@uniregistry.com>
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_B392E84286BF4F1E96FCED2EA7E19F6Dverisigncom_";
type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/_uGD4wKTABAooh8dL5XtP6q4Icc>
Cc: Jody Kolker <jkolker@godaddy.com>, "Tran, Trung" <Trung.Tran@neustar.biz>,
"eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] draft-ietf-eppext-launchphase Support for a "Claims
Service" post the Claims Phase
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: <http://www.ietf.org/mail-archive/web/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: Thu, 08 Jan 2015 19:35:27 -0000
Francisco, What do you mean by the extended claims phase? Is there a past mail list thread on this or is this a new issue? Please clarify. Thanks, — 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 Jan 8, 2015, at 12:44 PM, Francisco Obispo <fobispo@uniregistry.com<mailto:fobispo@uniregistry.com>> wrote: Hi James, The only component that is still open is what to call that extended claims phase. Perhaps it’s useful to suggest a name for that special phase (extended-claims?) to avoid having 100 different phase names. I believe the clarification is very useful. Thanks Francisco Obispo CTO - Registry Operations <Mail Attachment.png> 2161 San Joaquin Hills Rd. Newport Beach, CA, 92660 off. +1.345.749.6284 fax. +1.345.746.6263 On Jan 8, 2015, at 9:11 AM, Tran, Trung <Trung.Tran@neustar.biz<mailto:Trung.Tran@neustar.biz>> wrote: Thanks Jim for bringing this to the eppext. This will definitely help the post claims phase. With the wording changes, is there still a way to determine if there’s a trademark against the name regardless on whether or not the claims ack is needed in the create domain? Trung From: Jody Kolker <jkolker@godaddy.com<mailto:jkolker@godaddy.com>> Date: Thursday, January 8, 2015 at 11:15 AM To: "Gould, James" <JGould@verisign.com<mailto:JGould@verisign.com>>, "eppext@ietf.org<mailto:eppext@ietf.org>" <eppext@ietf.org<mailto:eppext@ietf.org>> Subject: Re: [eppext] draft-ietf-eppext-launchphase Support for a "Claims Service" post the Claims Phase Thanks Jim. >From a registrar perspective, this will solve the issue of domains that are released after the initial 90 day claims period but still require a claim to be presented to the customer. Thanks, Jody Kolker 319-294-3933 (office) 319-329-9805 (mobile) Please contact my direct supervisor Charles Beadnall (cbeadnall@godaddy.com<mailto:cbeadnall@godaddy.com>) with any feedback. This email message and any attachments hereto is intended for use only by the addressee(s) named herein and may contain confidential information. If you have received this email in error, please immediately notify the sender and permanently delete the original and any copy of this message and its attachments. From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Gould, James Sent: Monday, January 05, 2015 3:18 PM To: eppext@ietf.org<mailto:eppext@ietf.org> Subject: [eppext] draft-ietf-eppext-launchphase Support for a "Claims Service" post the Claims Phase All, There was an issue raised privately in supporting claims as a Claims Service post the Claims Phase. According to section 2.4.3 of the RPM Requirements, “...releases for Allocation or registration such reserved domain name at any time following the start date of the Claims Period, such domain MUST be subject to the Claims Services (as described in Section 3) for a period of ninety (90) calendar days following the date Registry Operator releases such domain name for registration…”. This means that support for the Claims Check Form needs to be revised to indicate whether or not the Claims Create Form is needed for the domain name and the use of the Claims Create Form should be supported in phases other than “claims”. There are no XML schema changes required to support this. Please review and provide feedback to the proposed revised language in the draft below to include in the next version of the draft that will also include the Implementation Status section discussed at the IETF-91 EPPEXT meeting. Change 3.1.1 "Claims Check Form" as follows: The Claims Check Form defines a new command called the Claims Check Command that is used to determine whether or not there are any matching trademarks, in the specified launch phase, for each domain name passed in the command, that requires the use of the "Claims Create Form" on a Domain Create Command. Instead of returning whether the domain name is available, the Claims Check Command will return whether or not at least one matching trademark exists for the domain name, that requires the use of the "Claims Create Form" on a Domain Create Command. <launch:name> Contains the fully qualified name of the queried domain name. This element MUST contain an "exists" attribute whose value indicates if a matching trademark exists for the domain name that requires the use of the "Claims Create Form" on a Domain Create Command. A value of "1" (or "true") means that a matching trademark does exist and that the "Claims Create Form" is required on a Domain Create Command. A value of "0" (or "false") means that a matching trademark does not exist or that the "Claims Create Form" is NOT required on a Domain Create Command. Change 3.3.2 "Claims Create Form" as follows: <launch:phase> SHOULD contain the value of "claims" to indicate the claims launch phase. A value other than "claims" MAY be used to pass the claims notice for domain names outside of the claims phase. Based on the above revised language the following may be done: • During claims phase with a claims check command • If domain has matching trademark • return exists=true • else • return exists=false • During post claims phase with a claims check command • If domain was released post claims phase start and is within 90 days of release and has matching trademark • return exists=true • else • return exists=false • During claims phase with a create command • If domain has matching trademark • claims notice is required • else • claims notice is NOT required • During post claims phase with a create command • If domain was released post claims phase start and is within 90 days of release and has matching trademark return • claims notice is required • else • claims notice is NOT required Thanks, — JG <image001.png> James Gould Distinguished Engineer jgould@Verisign.com<mailto:jgould@Verisign.com> 703-948-3271 12061 Bluemont Way Reston, VA 20190 VerisignInc.com “This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.” <image001.png>_______________________________________________ EppExt mailing list EppExt@ietf.org<mailto:EppExt@ietf.org> https://www.ietf.org/mailman/listinfo/eppext
- [eppext] draft-ietf-eppext-launchphase Support fo… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Jody Kolker
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Tran, Trung
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Francisco Obispo
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Francisco Obispo
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Francisco Obispo
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Jody Kolker
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Tran, Trung
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Michael Holloway
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Rik Ribbers
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Michael Holloway
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Jothan Frakes
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Jothan Frakes
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Michael Holloway
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Michael Holloway
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Gould, James
- Re: [eppext] draft-ietf-eppext-launchphase Suppor… Michael Holloway