ICANN ICANN Email List Archives

[gnso-pednr-dt]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [gnso-pednr-dt] PEDNR: A proposed path forward

  • To: "'PEDNR '" <gnso-pednr-dt@xxxxxxxxx>
  • Subject: Re: [gnso-pednr-dt] PEDNR: A proposed path forward
  • From: Jeff Eckhaus <eckhaus@xxxxxxxxxxxxxxx>
  • Date: Tue, 2 Nov 2010 09:51:17 -0700

All,

Thanks for the feedback on the proposal and I am sure it will be a major
topic of discussion today. Some of the comments that were received were
related to the number of days allowed to the registrant after expiration
for guaranteed renewal.

They ranged from "I would like to haggle over the length of time" to "it
is a good start. But several weeks shorter than required".
If possible on the call today could we go over the reasons why the
commenters do not believe this is enough time? Would like to hear the
evidence or reasoning behind these comments.

Thanks

Jeff




On 11/2/10 6:56 AM, "Berry Cobb" <berrycobb@xxxxxxxxxxxxxxxxxxx> wrote:

>PEDNR Team,
>
>I agree too that the Rr proposal is a great start.  Thank you for
>providing
>us with this first step for bringing consistency and more predictability
>to
>the expiration process.  Similar to Mikey, there a few additional items I
>would like to see before we paint the horizon and draw this WG to a close.
>For example, the documentation of this spaghetti process that can
>facilitate
>the education that both sides agree needs to be created to enhance
>Registrant knowledge and expectation.
>
>Often, my white board is my only outlet to get an issue off my brain so I
>can sleep better at night.  Attached is a whiteboard drawing of my take on
>the possible "future state" of the process.  I wanted to share this with
>the
>group before I spent any time on building this in Visio.  Please forgive
>my
>pathetic whiteboard penmanship and I recommend using zoom to decipher the
>labels.  As this is kind of a mess, I will be happy to walk through the
>diagram on our call to assist peeps in understanding my logic.  I suspect
>some of my logic is wrong, and I desire assistance from everyone to make
>it
>right.  Whether we use something like this or not, it will be a great aid
>to
>ensure I understand the impacts and consequence of any policy changes we
>may
>consider here.
>
>That is all for now.  Thanks again and see you on the call today!  B
>
>
>Berry Cobb
>Infinity Portals LLC
>berrycobb@xxxxxxxxxxxxxxxxxxx
>http://infinityportals.com
>720.839.5735
>
>-----Original Message-----
>From: owner-gnso-pednr-dt@xxxxxxxxx [mailto:owner-gnso-pednr-dt@xxxxxxxxx]
>On Behalf Of Mike O'Connor
>Sent: Monday, November 01, 2010 2:03 PM
>To: James M. Bladel
>Cc: PEDNR
>Subject: Re: [gnso-pednr-dt] PEDNR: A proposed path forward
>
>
>hi all,
>
>i like this a lot,  lots to talk about, wrangle over, etc.  but a great
>first step.  hats off to you folks.
>
>here are things i like;
>
>-- consistent behavior immediately after expiry
>
>-- registrants get to go to the front of the line and have that position
>protected for a period of time
>
>-- education (presumably made simpler by virtue of that consistent process
>after expiry)
>
>if i were climbing a mountain, i'd say that this is a good place to drive
>that first piton in.
>
>there are a few things that i'd like to add to the pile (and i'd like to
>haggle over the length of time), but i'll leave that for another day.
>
>thanks,
>
>mikey
>
>
>On Nov 1, 2010, at 2:12 PM, James M. Bladel wrote:
>
>>
>> Good afternoon, everyone.
>>
>>
>> With our review of community feedback complete, several of us on the
>> WG have been working to synthesize all the various positions and
>> opinions expressed on PEDNR into a compromise proposal.
>>
>>
>> The objectives of putting this forward are:
>>
>> (1)  Provide additional safeguards for registrants to guard against
>> the inadvertent loss of registrations, secured by Consensus Policy.
>> (2)  Provide some consistency in the registrant's experience with
>> expiring names.
>> (3)  Accomplish (1) and (3) in a manner that does not unnecessarily
>> disrupt the numerous commercial and non-commercial activities in our
>> industry.
>>
>> With these in mind, we submit the following slate of proposals for
>> your consideration.
>>
>>
>> Grace Period (Secured by Consensus Policy)
>> -------------------------------------------
>> Guaranteed five-day registrar grace period (what to call it will need
>> to be determined so as to avoid confusion with similarly named
>> periods) following expiration.  Only the RAE can recover/renew name
>> during this period.  While the name will not go to auction during this
>> period, it could be explicitly deleted by the Registrar, which commences
>the RGP.
>>
>>
>> Renewal notices (Secured by Consensus Policy)
>> ---------------------------------------------
>> Requirement to send (by a method at each registrar's discretion) a
>> minimum of one renewal notice to registrant no later than 10 days
>> prior to expiry, and a second notice the day prior to the expiry date
>> notifying the RAE that the 5-day registrar grace period will begin the
>> following day.
>>
>>
>> Whois
>> -----
>> No changes to Whois recommended.
>>
>>
>> Community Education
>> -------------------
>> Registrars:
>> Best practice recommendation: A registrar will design and host a
>> neutral-content site with important information about how to properly
>> steward a domain name and prevent unintended loss.
>> Registrar should provide on its web site, and send to registrant in
>> separate e-mail to registrant immediately following initial
>> registration, a set of instructions for keeping domain name records
>> current and for lessening the chance of mistakenly allowing the name
>> to expire.
>>
>> ALAC:
>> Budget time/money/resources to public education campaign to encourage
>> renewals and prevent unwanted loss of a name.
>>
>
>- - - - - - - - -
>phone     651-647-6109
>fax          866-280-2356
>web     http://www.haven2.com
>handle    OConnorStP (ID for public places like Twitter, Facebook, Google,
>etc.)
>
>
>


Please NOTE: This electronic message, including any attachments, may include 
privileged, confidential and/or inside information owned by Demand Media, Inc. 
Any distribution or use of this communication by anyone other than the intended 
recipient(s) is strictly prohibited and may be unlawful.  If you are not the 
intended recipient, please notify the sender by replying to this message and 
then delete it from your system. Thank you.




<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy