From: Marika Konings <marika.konings@icann.org>
To: "gnso-pednr-dt@icann.org" <gnso-pednr-dt@icann.org>
Sender: "owner-gnso-pednr-dt@icann.org" <owner-gnso-pednr-dt@icann.org>
Content-Class: urn:content-classes:message
Date: Thu, 12 Mar 2009 06:34:12 -0700
Subject: [gnso-pednr-dt] Results of Deletion and Renewal Consensus Policy
 Audit by ICANN Compliance Department
Thread-Topic: [gnso-pednr-dt] Results of Deletion and Renewal Consensus
 Policy Audit by ICANN Compliance Department
Thread-Index: AcmjFzqh28wtUAngEUCfRscpoynR/g==
Message-ID: <C5DECDE4.30E2%marika.konings@icann.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative;
	boundary="_000_C5DECDE430E2marikakoningsicannorg_"
MIME-Version: 1.0

--_000_C5DECDE430E2marikakoningsicannorg_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Dear All,

For your information, ICANN=92s compliance team recently carried out a dele=
tion and renewal consensus policy audit in relation to the Expired Domain D=
eletion Consensus Policy, which closely relates to some of the issues raise=
d in the context of the Post-Expiration Domain Name Recovery Issues Report.=
 You will find the relevant section of the Contractual Compliance semi-annu=
al report below. The complete version of the report can be found here: http=
://www.icann.org/en/compliance/reports/contractual-compliance-report-27feb0=
9-en.pdf.

I have been informed by our compliance team that follow-up audit activity i=
s being carried out as a result of the non-compliance identified. As a resu=
lt of this follow-up, the compliance team estimates that the number of non-=
compliant registrars is about 30-40% less today then when the report was pu=
blished.

With best regards,

Marika

=3D=3D=3D=3D=3D=3D=3D=3D=3D

>From Contractual Compliance Semi-Annual Report
February 2009

4.5 Deletion and Renewal Consensus Policy Audit

4.5.1 Executive Summary

ICANN's agreements with accredited registrars and gTLD registry operators r=
equire that they comply
with various specifically stated procedures and consensus policies. Pertine=
nt language from the policy
follows.

The expired domain deletion policy states that, =93At the conclusion of the=
 registration period, failure by
or on behalf of the Registered Name Holder to consent that the registration=
 be renewed within the
time specified in a second notice or reminder shall, in the absence of exte=
nuating circumstances, result
in cancellation of the registration by the end of the auto-renew grace peri=
od (although Registrar may
choose to cancel the name earlier). Among other requirements, the registrar=
 must provide notice to
each new registrant describing the details of their deletion and auto-renew=
al policy including the
expected time at which a non-renewed domain name would be deleted relative =
to the domain=92s
expiration date, or a date range not to exceed ten days in length. If a reg=
istrar makes any material
changes to its deletion policy during the period of the registration agreem=
ent, it must make at least the
same effort to inform the registrant of the changes as it would to inform t=
he registrant of other
material changes to the registration agreement.=94

4.5.2 Audit Objective
=95 To protect the registrants by ensuring they are provided notice of the =
expired name practices of
the registrar with whom they have registered their domain name.
=95 The primary objective of the audit was to determine which registrars ac=
tively sponsoring
domains have a statement addressing their Deletion and Renewal Consensus Po=
licy posted on
their website.

4.5.3 Methodology
ICANN=92s Contractual Compliance staff developed a list of all ICANN-accred=
ited registrars that were
actively registering domain names. For each registrar listed, ICANN staff e=
xamined their website to
examine where, if at all, the Deletion and Removal Policy was made availabl=
e to current and potential
registrants.

4.5.4 Findings
A majority of ICANN-accredited registrars provide a notice on the Deletion =
and Removal Policy to
registrants on their website. Table 4-6 provides a brief summary:

4.5.5 Observations
Over 82% of ICANN-accredited registrars actively selling domain names have =
information posted on
their websites that explains what happens if registrants fail to renew thei=
r domain registration after a
specified amount of time. In most cases, this information was found in the =
legal notices section or the
registration agreement documents posted on registrars=92 websites. Figure 4=
-6 contains the text posted
by a registrar.

Figure 4-6 Sample Text for Deletion and Renewal Consensus Policy

4.5.6 Follow-up Actions
ICANN sent notices to registrars that did not appear to have a statement di=
sclosing their Deletion and
Removal Policy posted on their website allowing them to clarify the reasons=
 for this and providing
them five business days to post this information. In the next few weeks, st=
aff will perform a review of
the websites of those registrars to verify that the information is posted.

--_000_C5DECDE430E2marikakoningsicannorg_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html><head>
<title>Results of Deletion and Renewal Consensus Policy Audit by ICANN Comp=
liance Department</title>
</head>
<body>
<font face=3D"Calibri, Verdana, Helvetica, Arial"><span style=3D"font-size:=
11pt">Dear All,<br>
<br>
For your information, ICANN=92s compliance team recently carried out a dele=
tion and renewal consensus policy audit in relation to the Expired Domain D=
eletion Consensus Policy, which closely relates to some of the issues raise=
d in the context of the Post-Expiration Domain Name Recovery Issues Report.=
 You will find the relevant section of the Contractual Compliance semi-annu=
al report below. The complete version of the report can be found here: <fon=
t color=3D"#0000FF"><u><a href=3D"http://www.icann.org/en/compliance/report=
s/contractual-compliance-report-27feb09-en.pdf">http://www.icann.org/en/com=
pliance/reports/contractual-compliance-report-27feb09-en.pdf</a></u></font>=
. <br>
<br>
I have been informed by our compliance team that follow-up audit activity i=
s being carried out as a result of the non-compliance identified. As a resu=
lt of this follow-up, the compliance team estimates that the number of non-=
compliant registrars is about 30-40% less today then when the report was pu=
blished.<br>
<br>
With best regards,<br>
<br>
Marika<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
>From Contractual Compliance Semi-Annual Report<br>
February 2009 &nbsp;<br>
</span></font><span style=3D"font-size:11pt"><font face=3D"Calibri Bold"><b=
r>
4.5 Deletion and Renewal Consensus Policy Audit<br>
<br>
</font></span><font face=3D"Calibri Bold"><font size=3D"1"><span style=3D"f=
ont-size:9pt">4.5.1 Executive Summary<br>
<br>
ICANN's agreements with accredited registrars and gTLD registry operators r=
equire that they comply<br>
with various specifically stated procedures and consensus policies. Pertine=
nt language from the policy<br>
follows.<br>
<br>
The expired domain deletion policy states that, =93At the conclusion of the=
 registration period, failure by<br>
or on behalf of the Registered Name Holder to consent that the registration=
 be renewed within the<br>
time specified in a second notice or reminder shall, in the absence of exte=
nuating circumstances, result<br>
in cancellation of the registration by the end of the auto-renew grace peri=
od (although Registrar may<br>
choose to cancel the name earlier). Among other requirements, the registrar=
 must provide notice to<br>
each new registrant describing the details of their deletion and auto-renew=
al policy including the<br>
expected time at which a non-renewed domain name would be deleted relative =
to the domain=92s<br>
expiration date, or a date range not to exceed ten days in length. If a reg=
istrar makes any material<br>
changes to its deletion policy during the period of the registration agreem=
ent, it must make at least the<br>
same effort to inform the registrant of the changes as it would to inform t=
he registrant of other<br>
material changes to the registration agreement.=94<br>
<br>
4.5.2 Audit Objective<br>
=95 To protect the registrants by ensuring they are provided notice of the =
expired name practices of<br>
the registrar with whom they have registered their domain name.<br>
=95 The primary objective of the audit was to determine which registrars ac=
tively sponsoring<br>
domains have a statement addressing their Deletion and Renewal Consensus Po=
licy posted on<br>
their website.<br>
<br>
4.5.3 Methodology<br>
ICANN=92s Contractual Compliance staff developed a list of all ICANN-accred=
ited registrars that were<br>
actively registering domain names. For each registrar listed, ICANN staff e=
xamined their website to<br>
examine where, if at all, the Deletion and Removal Policy was made availabl=
e to current and potential<br>
registrants.<br>
<br>
4.5.4 Findings<br>
A majority of ICANN-accredited registrars provide a notice on the Deletion =
and Removal Policy to<br>
registrants on their website. Table 4-6 provides a brief summary:<br>
<br>
4.5.5 Observations<br>
Over 82% of ICANN-accredited registrars actively selling domain names have =
information posted on<br>
their websites that explains what happens if registrants fail to renew thei=
r domain registration after a<br>
specified amount of time. In most cases, this information was found in the =
legal notices section or the<br>
registration agreement documents posted on registrars=92 websites. Figure 4=
-6 contains the text posted<br>
by a registrar.<br>
<br>
</span><span style=3D"font-size:7.5pt">Figure 4-6 Sample Text for Deletion =
and Renewal Consensus Policy<br>
<br>
</span><span style=3D"font-size:9pt">4.5.6 Follow-up Actions<br>
ICANN sent notices to registrars that did not appear to have a statement di=
sclosing their Deletion and<br>
Removal Policy posted on their website allowing them to clarify the reasons=
 for this and providing<br>
them five business days to post this information. In the next few weeks, st=
aff will perform a review of<br>
the websites of those registrars to verify that the information is posted.<=
/span></font></font>
</body>
</html>


--_000_C5DECDE430E2marikakoningsicannorg_--
