[98722] in North American Network Operators' Group
Re: [policy] When Tech Meets Policy...
daemon@ATHENA.MIT.EDU (Dorn Hetzel)
Thu Aug 16 09:14:27 2007
Date: Thu, 16 Aug 2007 09:12:10 -0400
From: "Dorn Hetzel" <dhetzel@gmail.com>
To: "william(at)elan.net" <william@elan.net>
Cc: "John L" <johnl@iecc.com>, "Marshall Eubanks" <tme@multicasttech.com>,
nanog@nanog.org
In-Reply-To: <Pine.LNX.4.62.0708152257420.26447@sokol.elan.net>
Errors-To: owner-nanog@merit.edu
------=_Part_16407_12251004.1187269930829
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Well, if they only delete 89% instead of 99.9% then to make 1,000,000 tasted
registrations they will have to keep 100,000 of them, which will send a fair
amount of money to the registry. Effectively making the minimum
registration costs for tasting 10% of the normal cost.
On 8/16/07, william(at)elan.net <william@elan.net> wrote:
>
>
>
> On Thu, 16 Aug 2007, John L wrote:
>
> >
> >>> The .ORG registry asked last year for permission to charge 5 cents per
> >>> deletion to any registrar that deletes more than 90% of their
> >>> registrations.
> >>
> >> I don't like that so much. Complications invite gaming the system.
>
> Yes, they are just going to delete 89% of their registrations.
>
> > It has the practical advantage of already having been implemented.
>
> What is important is not if it has been implemented but how effective
> it has been. But unfortunately with just one TLD, its possible that
> positive info can not be relied on as given limitations bad registrants
> could have just moved to using other TLDs that do not have the limits).
>
> Personally I think one way to do attempt to deal with it is to require
> explanation for each and every registration that is deleted and then
> look overall at types of explanations given and put additional barriers
> for certain cases (i.e. paperwork, etc) plus capability of ICANN to do
> audits of registrars deleted domains to verify that explanations they
> are given are consistent with actual activity.
>
> --
> William Leibzon
> Elan Networks
> william@elan.net
>
------=_Part_16407_12251004.1187269930829
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Well, if they only delete 89% instead of 99.9% then to make 1,000,000 tasted registrations they will have to keep 100,000 of them, which will send a fair amount of money to the registry. Effectively making the minimum registration costs for tasting 10% of the normal cost.
<br><br><div><span class="gmail_quote">On 8/16/07, <b class="gmail_sendername">william(at)elan.net</b> <<a href="mailto:william@elan.net">william@elan.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>On Thu, 16 Aug 2007, John L wrote:<br><br>><br>>>> The .ORG registry asked last year for permission to charge 5 cents per<br>>>> deletion to any registrar that deletes more than 90% of their<br>
>>> registrations.<br>>><br>>> I don't like that so much. Complications invite gaming the system.<br><br>Yes, they are just going to delete 89% of their registrations.<br><br>> It has the practical advantage of already having been implemented.
<br><br>What is important is not if it has been implemented but how effective<br>it has been. But unfortunately with just one TLD, its possible that<br>positive info can not be relied on as given limitations bad registrants
<br>could have just moved to using other TLDs that do not have the limits).<br><br>Personally I think one way to do attempt to deal with it is to require<br>explanation for each and every registration that is deleted and then
<br>look overall at types of explanations given and put additional barriers<br>for certain cases (i.e. paperwork, etc) plus capability of ICANN to do<br>audits of registrars deleted domains to verify that explanations they
<br>are given are consistent with actual activity.<br><br>--<br>William Leibzon<br>Elan Networks<br><a href="mailto:william@elan.net">william@elan.net</a><br></blockquote></div><br>
------=_Part_16407_12251004.1187269930829--
