Page History

* Status will be confined to the following terms: Drafting, Commenting, Voting, Adopted, Rejected, Suspended, No consensus, No statement, To Be Confirmed (TBC), Other

...

(*) Comments submitted after the posted Close Date/Time are not guaranteed to be considered in any final summary, analysis, reporting, or decision-making that takes place once this period lapses.

FINAL

...

VERSION TO BE SUBMITTED IF RATIFIED

Please click here to download a copy of the PDF below.

ALAC Statement on

The final Statement in PDF format is to be added here if the draft below is ratified. 

DRAFT STATEMENT

As you know the Post Expiration Domain Name Recovery (PEDNR) PDP was approved by the Board last year and the resultant Policy (now called the Expired Registration Recovery Policy - ERRP) was posted for comment.pdf

FINAL DRAFT VERSION TO BE VOTED UPON BY THE ALAC

The PEDNR PDP recommended that registrars who operate web site for registration must post their information about renewal fees and state what method they will use to contact registrants. The recommendation was silent regarding resellers because it was the belief that registrars, in honoring all of the terms of their contract, would require resellers to post this information as well.how a registrar will contact a registrant should be readily made available on the registrar web site (Rec. 5 & 6). It was the clear intent of the recommendations that this apply to ALL registrants.

Although it was not clear why at the time, ICANN staff working on the resultant changes to the RAA added very welcome wording explicitly requiring that registrars require resellers to post this information as well. The proposed policy can be found atParagraphs 4.1 and 4.2 of the ERRP (http://www.icann.org/en/resources/registrars/consensus-policies/errp/draft-policy-11oct12-en.pdf and the sections in question are paragraphs ) require, among other things, that if a registrar operates a web site, certain information must be clearly displayed there. Paragraphs 4.1.2 and 4.2.3 .

There were no negative comments about this in the public comments which were due to close on Nov. 11th. Staff extended the comment period for one more week, and had explicitly called attention to the changes on the Implementation Review Group mailing list and explicitly asking for comments to be posted on this.

require that a reseller, if one is used, must similarly display this information.

Michele Neylon, the registrar who was on the Implementation Review Group submitted a statement to the ERRP Comment saying that the proposed language about resellers was debated at length by the PDP WG and the final decision was to not include such language in the recommendation. That is factually correct and indeed the report made reference to the fact that there was an explicit decision to not include it. His statement can be found at It is the understanding of the ALAC that the belief within the PEDNR WG was that all provisions of the RAA that applied to registrars must be enforced by registrars on resellers (for those who use them). Since that has now proven to be false (http://forum.icann.org/lists/draft-errp-policy/msg00001msg00004.html.

The ICANN Registrar Relations staff person who I had been working with was unavailable, so I asked compliance whether that was how they saw this as well. The reply was direct and clear that this was not how they interpreted the RAA terms and that the web posting provisions would not apply to resellers unless the explicit. The exchange is appending to this message.

I propose the following:

1. Under my own name but as former Chair of the PEDNR WG and a member of the Implementation Review Team, I will post the statement from Compliance that without the explicit reseller language, that the new Policy will not benefit all Registrants, but only those who deal directly with Registrars, and based on my understanding, that was not the intent of the WG.
2. ALAC should post a statement supporting the need to keep the explicit reseller language. This statement may need to be altered if registrars in the interim post a message agreeing to keep the language.

) it is imperative that either sections 4.1.2 and 4.2.3 of the proposed ERRP not be omitted, or the ERRP wording otherwise be adjusted to ensure that it covers websites operated by resellers.

The ALAC understands that registrars might be reluctant to include terms that have not been fully vetted during the PDP process, but the two paragraphs in question are identical in impact to the existing 3.12.5 and should have no unforeseen consequences not already in the current RAA.

Without these two paragraphs, there is no obligation for a registrar to ensure that a reseller displays this information and a significant percentage of registrants, those who deal with resellers, may be deprived of this information.  The access to this information that the PDP was attempting to ensure is no longer guaranteed, and the registrar, by subcontracting services to a reseller, has effectively been relieved from fulfilling these RAA obligations. This calls into question the value of the immense time and energy that the community puts into developing PDP Consensus Policy Recommendations and indeed the effectiveness of the entire RAA. Resellers are responsible for a large percentage of gTLD registrations, particularly those by individual users, and they should be afforded the FULL protection of their rights under the RAA.