RE: [gnso-dt-wg] Quantifying the Registrar impact to changing AGP

["Jothan Frakes" <jfrakes@xxxxxxxxxxx>]

Good points.  
I will do a straw poll within the registrar constituency to quantify the first 
point.

The second point sounds like an ICANN directed question (if it was not 
rhetorically posed).

-jothan

-------------
Jothan Frakes
Oversee.net / Domain Sponsor
Jfrakes@xxxxxxxxxxx
+1.213 925 5206 / +1.206 355 0230 Cel

 -----Original Message-----
From:   Mike Rodenbaugh [mailto:mxr@xxxxxxxxxxxxx]
Sent:   Friday, August 10, 2007 12:19 PM Pacific Standard Time
To:     Jothan Frakes; gnso-dt-wg@xxxxxxxxx
Subject:        RE: [gnso-dt-wg] Quantifying the Registrar impact to changing 
AGP

This makes sense, but I wonder what sort of statistics registrars can
provide to show often they use the AGP in this way or in any other way
besides tasting?

I am also curious, like Danny, to know how ICANN came up with the 5%
figure in the budget.

Mike Rodenbaugh

-----Original Message-----
From: owner-gnso-dt-wg@xxxxxxxxx [mailto:owner-gnso-dt-wg@xxxxxxxxx] On
Behalf Of Jothan Frakes
Sent: Friday, August 10, 2007 11:06 AM
To: gnso-dt-wg@xxxxxxxxx
Subject: [gnso-dt-wg] Quantifying the Registrar impact to changing AGP

Hi

I've received feedback in the form of emails and phone calls from within
the registrar constituency that indicate that one completely valid AGP
use is where domains are registered (testyyyymmddhhmmss-delete.com
replacing yyyy with the year as an example of the activity, etc) and run
through a range of functions, then ultimately deleting the domain name
for a suite of efforts to monitor system health.  

Many do this in rapid segments, this ranges from once per day to many
times per hour, and the naming convention varied.

As a summary, registrars do this by creating a domain, changing
nameservers, adding and deleting hosts, ensuring that the name resolves
in DNS when created, etc. and something that enables proactive
monitoring of the provisioning systems.

There is concern that an overreaching outcome of the DTWG might not
entertain some reasonable replacement, and result in impaired ability to
ensure stability of the provisioning systems for domain management so
that registrars may effectively service their customers, the
registrants.

Certainly there is an opportunity for this point to be raised in the
questionnaire/RFI, but I was requested to voice this within the working
group to ensure that whatever changes might result from the efforts of
this working group not adversely impact the ability to ensure stability
of the provisioning system not be impaired through our efforts.
 
The resounding concern is that something significant changes in the
provisioning system to fix one thing that breaks another as an
unexpected consequence, and they wanted this consequence to be raised
proactively and taken into consideration.

Jothan Frakes

-----------------------------
OVERSEE.NET
818 7th Street, Suite 700
Los Angeles, CA 90017
cl +1.206.355.0230
ph +1.213.408.0080 x 1233
fax +1.213.892.1214
www.oversee.net
jfrakes@xxxxxxxxxxx
 

Confidentiality Warning: This e-mail contains information intended only
for the use of the individual or entity named above.  If the reader of
this e-mail is not the intended recipient or the employee or agent
responsible for delivering it to the intended recipient, any
dissemination publication or copying of this e-mail is strictly
prohibited.  The sender does not accept any responsibility for any loss,
disruption or damage to your data or computer system that may occur
while using data contained in, or transmitted with, this e-mail.  If you
have received this e-mail in error, please immediately notify us by
return e-mail.  Thank you