Jean-Jacques You are far more polite and diplomatic than I felt at first reading. My version -The statement is a simple restatement in plain English of what the registrars must do anyway, so the use of the term 'benefits' is misleading; it is a statement of what registrars MUST do and can be compelled to do. If it is more, then what is the process for making it more - i.e., what is the process for turning what is now merely a restatement of RAA obligations on registrars to a statement of what should be happening. It is only when the document goes beyond what the RAA requires that the term 'benefits' can be justified. Right now - it is only 'rights'. I look forward to a process that makes the statement more than that. Holly On 10/11/2013, at 7:54 PM, jjs wrote:
Thanks Olivier.
Samantha's account is honest and comprehensible.
But from the user perspective,
- the whole exercise is considered a "negotiation". Why? Because successive Boards have accepted the premise that ICANN is in no way a regulatory body, in spite of the fact that it does have some regulatory powers. This attutude can also be seen in the growing distance between a mantra recited by part of the community ("ours is a very limited, purely technical remit") and ICANN's Vision statement (into which the public interest finally made its way).
- "Negotiation" is also used to underline the MSM nature of the corporation. But we should tease out the fact that imposing rules in the global public interest does not contradict MSM, it simply carries it out at a higher level.
Best regards, Jean-Jacques.
-------- Message d'origine -------- De : Olivier MJ Crepin-Leblond <ocl@gih.com> Date : 10/11/2013 11:15 (GMT+02:00) A : ALAC Working List <alac@atlarge-lists.icann.org> Cc : At-Large Worldwide <at-large@atlarge-lists.icann.org> Objet : [ALAC] Fwd: Re: Follow-up on an enquiry during Durban Public Forum
Dear all,
please be so kind to find the answer below, to the question which Evan had asked at the public forum in Durban. The question was: "why is Section 9 of the RAA entitled 'Registrant Benefits and Responsibilities' ?" Kind regards,
Olivier MJ Crépin-Leblond ALAC Chair
-------- Original Message -------- Subject: Re: Follow-up on an enquiry during Durban Public Forum Date: Wed, 30 Oct 2013 12:46:34 -0700 From: Samantha Eisner <Samantha.Eisner@icann.org> To: Evan Leibovitch <evan@telly.org>, Olivier MJ Crepin-Leblond <ocl@gih.com> CC: Fadi Chehade <fadi.chehade@icann.org>, John Jeffrey <john.jeffrey@icann.org>, Cyrus Namazi <cyrus.namazi@icann.org>, ICANN At-Large Staff <staff@atlarge.icann.org>, Cassia Oliveira <cassia.oliveira@icann.org>
Dear Olivier and Evan,
In response to your query below, during the course of the 2013 RAA negotiations, it became clear that the negotiating teams and the community had different understandings of what purpose the document formerly referred to as "Registrant Rights and Responsibilities" was intended to serve. While the negotiating teams from ICANN and the Registrars agreed that this document would be a compilation only of obligations clearly found in the contract, the community input at public sessions on this topic, as well as in the public comment forum, suggested that the "Registrant Rights and Responsibilities" document should serve a broader scope, encompassing issues such as external legal rights relating to privacy and intellectual property.
As explained in the summary of public comments on a proposed final version of the RAA, "For the Registrant Rights and Responsibilities document, there were two versions of a new document posted by commenters as alternatives to the version posted for comment. The current Registrant Rights and Responsibilities document, as posted with the agreement, was not mean to be a full statement of all registrant rights and responsibilities arising out of being a domain name registrant. Rather, it is specifically targeted to identify contractual rights and responsibilities that are stated within the RAA, as opposed to looking to consensus policy or to broader principles of privacy rights. While the suggestions raised in the versions presented during the comment period incorporate some ideas that could be of great value for the community to discuss, they are not geared to the limited purpose of the document. To help clarify the purpose of the document, ICANN will be considering clarifying the title of the document prior to finalizing the RAA." http://www.icann.org/en/news/public-comment/report-comments-proposed-raa-21 jun13-en.pdf.
The term "benefits" was agreed upon by ICANN and the Registrars Negotiating Team to achieve two purposes - first, to clarify the purpose of the document so that it was not seen a broad, sweeping statement of registrant rights, as commenters clearly identified. Second, the use of the term "benefits" helps denote a balance between the listing of key contractual responsibilities to which registrants are bound, and the positive things that the registrants are provided under the agreement, such as access to information. There is no explicit legal meaning that we were trying to afford to the word "benefit", instead the focus was on removing the confusion inherent in the continued use of the term "rights" where not all applicable rights were enumerated.
Best,
Samantha
-- Samantha Eisner Senior Counsel, ICANN 12025 Waterfront Drive, Suite 300 Los Angeles, California 90094 Direct Dial: +1 310 578 8631 samantha.eisner@icann.org
On 9/25/13 6:33 PM, "Olivier MJ Crepin-Leblond" <ocl@gih.com> wrote:
ALAC Correspondence Ref: AL-ALAC-CO-0913-01-00-EN
Dear Fadi,
I am following up on a question which was asked as an individual by my colleague Evan Leibovitch during the Public Forum in Durban:
Quoting the transcript of the session, page 87:
EVAN LEIBOVITCH: Thanks, Steve. I'm Evan Leibovitch, vice chair of the ALAC speaking on my own behalf. But this is based on a number of conversations with a number of people within the At-Large and elsewhere. Without coordinating it at all with Phil, it relates to something he said and it has to do with the relationship between benefits and rights. Somewhere, somehow, section 9 of the RAA had some strange search and replace happen where the words "rights" were taken out and "responsibilities" put in. Not only that but it was done in a confusing way. The document for section 9 heading says "benefits and responsibilities" and the first section talks about rights. Since then there have been many talks this week about rights and responsibilities. The "B" word hasn't been used anywhere, but there it is in the RAA. Can someone explain how it crept in, why it's there, and what is meant by the distinction between rights and benefits? I think to a lot of people, there's a very real distinction in the word. I'd like to know how it crept into the RAA.
STEVE CROCKER: Management response here?
FADI CHEHADE: We'll look into that. That's all I can say. I'm trying to find out some facts, but I appreciate your comment. I appreciate the distinction between the two. That's all I can say.
--- end of transcript ---
The ALAC has discussed this point during its August and its September monthly calls and on its mailing lists and this has proved to be a particularly important point which needed clarification. I am therefore writing to you to ask for this clarification.
It is understood that the RAA is a legal contractual document, several copies of which were signed in Durban. The page in question is Section 9, entitled "Registrants' Benefits and Responsibilities", page 68.
Until the title of this section appeared, the notion of "Registrant Rights and Responsibilities" was the notion that prevailed, certainly in the At-Large world. As Evan Leibovitch mentions in his comment during the public meeting, there is much difference between a Registrants' Rights and a Registrants' Benefits.
But the confusion is then exacerbated by the fact that the next line on that same RAA page is a sub-heading of "Domain Name Registrants' Rights" and the list printed on that page very clearly reads as a list of Registrant Rights. RAA signatories are therefore clearly signing on a list of Registrants' Rights.
Furthermore, Section 3.16 of the same RAA document points to "an educational webpage summarizing the terms of the Registrar Accreditation Agreement and related Consensus Policies (as of the date of this Agreement, located at: http://www.icann.org/en/registrars/registrant-rights-responsibilities-en.h tm)."
On the other hand, Section 3.7.10 mentions "Registrants' Benefits and Responsibilities" as: "Registrar shall publish on its website(s) and/or provide a link to the Registrants¹ Benefits and Responsibilities Specification attached hereto and shall not take any action inconsistent with the corresponding provisions of this Agreement or applicable law."
and:
"3.12.7 Its Resellers shall publish on their website(s) and/or provide a link to the Registrants¹ Benefits and Responsibilities Specification attached hereto and shall not take any action inconsistent with the corresponding provisions of this Agreement or applicable law."
So what we have is references to both Rights and Benefits, and I, like my colleague Evan Leibovitch, would like to point out that these are entirely different words meaning entirely different things -- and I note that from your response in the ICANN Public Forum, you appreciate the distinction between the two.
Would you then please kindly provide clarification as to how the title of that section is called "Registrants' Benefits and Responsibilities" when there are clearly no "Benefits" but indeed there are "Rights" listed?
Warmest regards,
Olivier MJ Crépin-Leblond ALAC Chair
_______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...) _______________________________________________ ALAC mailing list ALAC@atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac
At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA...)