ICANN ICANN Email List Archives


<<< Chronological Index >>>    <<< Thread Index >>>

RE: [gnso-contactinfo-pdp-wg] URGENT Correction to Recommendation 4 - REPLY NEEDED!

  • To: "gnso-contactinfo-pdp-wg@xxxxxxxxx" <gnso-contactinfo-pdp-wg@xxxxxxxxx>
  • Subject: RE: [gnso-contactinfo-pdp-wg] URGENT Correction to Recommendation 4 - REPLY NEEDED!
  • From: "Pascal Haddad" <phaddad@xxxxxxxxxx>
  • Date: Mon, 22 Jun 2015 19:43:24 +0000

Dear all

I know I am too late for this but I just want to confirm that I also agree on 
the necessary correction in recommendation #4.



From: owner-gnso-contactinfo-pdp-wg@xxxxxxxxx 
[mailto:owner-gnso-contactinfo-pdp-wg@xxxxxxxxx] On Behalf Of Dillon, Chris
Sent: Sunday, June 21, 2015 7:29 AM
To: gnso-contactinfo-pdp-wg@xxxxxxxxx
Cc: Lars Hoffmann
Subject: Re: [gnso-contactinfo-pdp-wg] URGENT Correction to Recommendation 4 - 
Importance: High

Dear colleagues,

Thank you for your prompt dealing with this matter! Much appreciated. It is to 
be hoped that this will avoid delay,

Please confirm you are happy with Lars’ correction below, if you have not 
already done so.


Research Associate in Linguistic Computing, Centre for Digital Humanities, UCL, 
Gower St, London WC1E 6BT Tel +44 20 7679 1599[X] (int 31599) 

From: Lars Hoffmann <lars.hoffmann@xxxxxxxxx<mailto:lars.hoffmann@xxxxxxxxx>>
Date: Saturday, 20 June 2015 16:10
Subject: [gnso-contactinfo-pdp-wg] URGENT Correction to Recommendation 4 - 

Dear all,

Please all read this careful and try to reply on list as soon as possible.

It has come to our attention that there was an important term mistakenly used 
in Recommendation #4 of our Final Report

The Recommendation reads currently:

Recommendation #4 The Working Group recommends that, regardless of the 
language(s)/script(s) used, it is assured that the data fields are consistent 
to standards in the Registrar Accreditation Agreement (RAA), relevant L Policy, 
Additional Whois Information Policy (AWIP) and any other applicable polices. 
Entered contact information data are verified, in accordance with the 
aforementioned Policies and Agreements and the language/script used must be 
easily identifiable.
Level of consensus: Full Consensus

The term ‘verified’ in the second sentence of the recommendation has legal 
implications and would change significantly the contractual obligations of the 
Contracted Parties. As the substance of the Final Report on that particular 
issue makes it clear that "validation" was intended to be used instead of 
“verification”. Both  co-Chairs agree that this is a clerical mistake as the 
Group meant to use the term ‘validate’ not ‘verifiy’ and it should be changed 

With your consent we would like change the working to reflect the actual 
meaning of what the Group meant to recommend. In order to prevent delaying the 
GNSO Council’s vote on our Final Report, this would have to happen as soon as 
possible so that the Motion to adopt can be changed accordingly and in time for 
Wednesday’s Council discussion and vote.

Many thanks and best wishes,

<hr> <FONT style="font-size:14px" face="Calibri">

<b>- UAE:  </b> Official fees for trademark matters have doubled almost across 
the board in comparison with their current level effective as of May 29, 2015. 
The increase will also affect patent filings and title updates. Trademark 
owners should attend to any renewal due over the next 12 months at the existing 
rates prior to the increase.<br /><br />

<b>- Yemen:  </b> In order to avoid delays resulting from interruptions in the 
mail and courier services, applicants are able to file scanned copies of 
supporting documents while submitting the legalized copies as soon as 
available. Also, given that some Yemeni Consulates are refraining from 
legalization at this stage, notarized documents can be filed pending further 
submission of the legalized documents once possible. <br /><br />

<b>- Lebanon: </b> All POA submissions after April 10, 2015 must be 
legalized.<br /><br />

For more information on this or on general IP matters in our region, please 
contact <a href="mailto:news@xxxxxxxxxx";>news@xxxxxxxxxx</a><br /><br/>


<FONT size="1" face="Calibri"><i>The information contained in this message is 
privileged and confidential intended for the use of the individual or entity 
name above. Any use, dissemination, distribution or copying of this 
communication by other than the intended recipient is strictly 

<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy