ICANN/GNSO GNSO Email List Archives

[council]


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

RE: [council] Agenda Request

  • To: ki_chango@xxxxxxxxx, council@xxxxxxxxxxxxxx
  • Subject: RE: [council] Agenda Request
  • From: "Marilyn Cade" <marilynscade@xxxxxxxxxxx>
  • Date: Tue, 07 Mar 2006 16:06:02 -0500
  • Cc: marilynscade@xxxxxxxxxxx
  • In-reply-to: <20060307205636.84564.qmail@web54709.mail.yahoo.com>
  • Sender: owner-council@xxxxxxxxxxxxxx

<html><div style='background-color:'><DIV class=RTE>
<P>It is interesting to consider how best to proceed. Ross, do you have an outline in 
mind that we can sort of bat back and forth among intersted councilors in a discussion over 
the next week or two? So that we could actually then formulate what a request for an issues 
report might look like? Also, there is perhaps another step taht can be taken and that is 
the development of a background paper -- similar to what Maria did on the second level 
names, although in this case, it might be that the background would largely be provided by 
operations staff? Have to think more about that, overall.</P>
<P>&nbsp;</P>
<P>Marilyn <BR><BR></P></DIV>
<DIV></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #a0c6e5 2px solid; MARGIN-RIGHT: 
0px"><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif">
<HR color=#a0c6e5 SIZE=1>

<DIV></DIV>From:&nbsp;&nbsp;<I>Mawaki Chango &lt;ki_chango@xxxxxxxxx&gt;</I><BR>To:&nbsp;&nbsp;<I>Council GNSO &lt;council@xxxxxxxxxxxxxx&gt;</I><BR>Subject:&nbsp;&nbsp;<I>RE: [council] Agenda Request</I><BR>Date:&nbsp;&nbsp;<I>Tue, 7 Mar 2006 12:56:36 -0800 (PST)</I><BR>&gt;Ross, Sophia, Marylin et al.<BR>&gt;<BR>&gt;I would tend to believe that the issue here is less the duration of<BR>&gt;the RGP itself that the policy "enforcement" and/or implementation<BR>&gt;proposals. So the question would be: shall we initiate a PDP for<BR>&gt;enforcement provision? I find that a bit worrying that some<BR>&gt;registrars, and by no means the least, "begin auctions for names even<BR>&gt;before the names have officially expired but warn auction<BR>&gt;participants that the original owner could still redeem the name."<BR>&gt;<BR>&gt;On the other hand, the following suggests that the issue requires a<BR>&gt;change in policy: "Paul Twomey, chief executive of ICANN, says some<BR>&gt;people in the domain industry recently have raised concerns that the<BR>&gt;guidelines governing expired names are "being utilized in ways that<BR>&gt;were not originally intended." But Mr. Twomey says no one has<BR>&gt;proposed a formal change in policy to address the issue."<BR>&gt;<BR>&gt;Overall, though I suspect that the current apparent consensus does<BR>&gt;not necessarily allow to prejudge, in my view, of a smooth and quick<BR>&gt;PDP (Ross, you never know what you'll run into when you give people<BR>&gt;the opportunity to talk:-)); though I also find reasonnable a time<BR>&gt;period of 30 (RGP) to 75 (+ time for the registrars to inform ICANN)<BR>&gt;days during which the registrant has one chance to claim her/his name<BR>&gt;back; I think it is necessary to take action in order to ensure that:<BR>&gt;i) ICANN be duly informed before any action is taken by the<BR>&gt;registrars on the market regarding the dropped names (even if they<BR>&gt;don't want their initial clients/registrants take advantage of the 45<BR>&gt;day notice allowed by ICANN); and<BR>&gt;ii) the current 30-day RGP be fully observed and respected by all<BR>&gt;players.<BR>&gt;<BR>&gt;That is the least, isn't it?<BR>&gt;<BR>&gt;Mawaki<BR>&gt;<BR>&gt;--- tony.ar.holmes@xxxxxx wrote:<BR>&gt;<BR>&gt; &gt; I think the ISPCP would also be likely to add their support for<BR>&gt; &gt; this<BR>&gt; &gt; item. Its important we try to nail down a process that overcomes<BR>&gt; &gt; some of<BR>&gt; &gt; the current shortfalls which impact many registrants.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; Tony<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; -----Original Message-----<BR>&gt; &gt; From: owner-council@xxxxxxxxxxxxxx<BR>&gt; &gt; [mailto:owner-council@xxxxxxxxxxxxxx]<BR>&gt; &gt; On Behalf Of Ken Stubbs<BR>&gt; &gt; Sent: 05 March 2006 01:53<BR>&gt; &gt; To: 'GNSO Council'<BR>&gt; &gt; Subject: Re: [council] Agenda Request<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; Marilyn's observations here are quite relevant..<BR>&gt; &gt; there has to be basic "enforceable" safeguards built into the<BR>&gt; &gt; process to<BR>&gt; &gt; deal with inadvertent expirations<BR>&gt; &gt; and accidental deletions..<BR>&gt; &gt;<BR>&gt; &gt; many companies (large &amp; small) , have invested significant funds &amp;<BR>&gt; &gt; resources into their respective internet presence and<BR>&gt; &gt; to think that it could all "evaporate" over a mistake made by<BR>&gt; &gt; someone in<BR>&gt; &gt; the accounts payable department or a misdirected email (i.e. spam<BR>&gt; &gt; filtered)&nbsp;&nbsp;is disconcerting to say the least... !<BR>&gt; &gt;<BR>&gt; &gt; regards<BR>&gt; &gt;<BR>&gt; &gt; ken stubbs<BR>&gt; &gt;<BR>&gt; &gt; Marilyn Cade wrote:<BR>&gt; &gt;<BR>&gt; &gt; I am interested in this topic. I chaired the Transfers TF, and we<BR>&gt; &gt; dealt<BR>&gt; &gt; with a variety of topics in that TF...<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; But, the Redemption Grace Period emerged as a safeguard for<BR>&gt; &gt; registrants.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; In those days, I worked for AT&amp;T, and they had a portfolio of over<BR>&gt; &gt; 500<BR>&gt; &gt; names, including .net; .com; .org; several dozen country codes<BR>&gt; &gt; where<BR>&gt; &gt; they had market facing presence, and when the "proof of concept"<BR>&gt; &gt; TLDs<BR>&gt; &gt; were introduced, they also defensively registered in info and .biz<BR>&gt; &gt; in<BR>&gt; &gt; particular.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; Managing the portfolio was part of an assignment to a particular<BR>&gt; &gt; part of<BR>&gt; &gt; the corporation, but still, it was challenging and not simple to<BR>&gt; &gt; keep<BR>&gt; &gt; track of.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; I registered a name or two that I wanted to use, for organizing ad<BR>&gt; &gt; hoc<BR>&gt; &gt; coalitions, and managed them myself. And, then, when I left AT&amp;T, I<BR>&gt; &gt; registered two names, one to use, one to defensively protect my<BR>&gt; &gt; "name".<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; I am now an&nbsp;&nbsp;"average registrant" --&nbsp;&nbsp;I need all the safeguards I<BR>&gt; &gt; can<BR>&gt; &gt; get. My registrar is extremely responsible - wait, BOTH my<BR>&gt; &gt; registrars<BR>&gt; &gt; are responsible. BOTH of them remind me, and remind me, and REMIND<BR>&gt; &gt; me...<BR>&gt; &gt; but you know, I travel, I have a 90 year old father and I get<BR>&gt; &gt; distracted... and I am the CEO of a small business with a lot of<BR>&gt; &gt; other<BR>&gt; &gt; distractions... and focusing on my domain name doesn't always rise<BR>&gt; &gt; to<BR>&gt; &gt; the top of my agenda.... Yet, I depend on it....<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; So, I need all the safeguards I can get. ... :-) within reason.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; I'll try not to extrapolate from my own experience and ineptness,<BR>&gt; &gt; but<BR>&gt; &gt; still, I think about the 'average' registrant. ... and thus,<BR>&gt; &gt; consensus<BR>&gt; &gt; policy for RGP seems fully appropriate.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; Marilyn<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;&nbsp;&nbsp; _____<BR>&gt; &gt;<BR>&gt; &gt; From: owner-council@xxxxxxxxxxxxxx<BR>&gt; &gt; [mailto:owner-council@xxxxxxxxxxxxxx]<BR>&gt; &gt; On Behalf Of Sophia B<BR>&gt; &gt; Sent: Saturday, March 04, 2006 7:16 PM<BR>&gt; &gt; To: ross@xxxxxxxxxx<BR>&gt; &gt; Cc: GNSO Council<BR>&gt; &gt; Subject: Re: [council] Agenda Request<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; I believe that the current policy is fine. It gives enough time in<BR>&gt; &gt; any<BR>&gt; &gt; way it is implemented for registrants to renew.&nbsp;&nbsp;Many people are<BR>&gt; &gt; irresponsible and that is why they loose their domains. I don't<BR>&gt; &gt; think<BR>&gt; &gt; giving them more time would change it.<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; Choosing a better registrar that does a good job of protecting them<BR>&gt; &gt; is<BR>&gt; &gt; more important.<BR>&gt; &gt;<BR>&gt; &gt; Sophia<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; On 03/03/06, Ross Rader &lt;ross@xxxxxxxxxx&gt; wrote:<BR>&gt; &gt;<BR>&gt; &gt; Bruce, fellow Councillors,<BR>&gt; &gt;<BR>&gt; &gt; At our next meeting, I would like to propose the initiation of a<BR>&gt; &gt; new<BR>&gt; &gt; policy development process concerning the Redemption Grace Period<BR>&gt; &gt; and<BR>&gt; &gt; request that this topic be added to our agenda.<BR>&gt; &gt;<BR>&gt; &gt; It has recently come to my attention recently that the current<BR>&gt; &gt; implementation (detailed at<BR>&gt; &gt; http://www.icann.org/bucharest/redemption-topic.htm) is an optional<BR>&gt; &gt; registry service which may not be meeting the needs of registrants<BR>&gt; &gt; as<BR>&gt; &gt; originally envisaged when it was implemented. Recent press reports<BR>&gt; &gt; (see<BR>&gt; &gt; below) and registrant complaints indicate that names are being lost<BR>&gt; &gt; despite the implementation of this registry service.<BR>&gt; &gt;<BR>&gt; &gt; I have spent a lot of time considering whether or not Council can<BR>&gt; &gt; afford<BR>&gt; &gt; to take on additional work given our current workload and have come<BR>&gt; &gt; to<BR>&gt; &gt; the view that because of the widespread support for the Redemption<BR>&gt; &gt; Grace<BR>&gt; &gt; Period amongst the constituencies (as documented on the ICANN<BR>&gt; &gt; website)<BR>&gt; &gt; and the pre-existence of strong policy and implementation proposals<BR>&gt; &gt; that<BR>&gt; &gt;<BR>&gt; &gt; already have consensus support of the stakeholders, we should be<BR>&gt; &gt; able to<BR>&gt; &gt; confirm the Redemption Grace Period proposals as consensus policy<BR>&gt; &gt; fairly<BR>&gt; &gt; quickly and without much additional effort or contentious debate.<BR>&gt; &gt;<BR>&gt; &gt; Because of the pre-existing consensus on this issue, I will propose<BR>&gt; &gt; to<BR>&gt; &gt; move this forward without creating a task force per Annex A,<BR>&gt; &gt; Section 8<BR>&gt; &gt; of the ICANN Bylaws once we have agreed to initiate a PDP and been<BR>&gt; &gt; provided with an issues report by the staff.<BR>&gt; &gt; (http://www.icann.org/general/bylaws.htm#AnnexA-8). i.e. the<BR>&gt; &gt; fast-track.<BR>&gt; &gt;<BR>&gt; &gt; In the very least, creation of an issues report will gather up<BR>&gt; &gt; substantive data on this subject and allow us to make an informed<BR>&gt; &gt; decision regarding whether or not circumstances like those detailed<BR>&gt; &gt; below are widespread enough to justify launching a full-fledged<BR>&gt; &gt; PDP.<BR>&gt; &gt;<BR>&gt; &gt; Your consideration of this matter would be extremely appreciated.<BR>&gt; &gt; If you<BR>&gt; &gt;<BR>&gt; &gt; have any questions, please don't hesitate to drop me a note (or<BR>&gt; &gt; give me<BR>&gt; &gt; a ring).<BR>&gt; &gt;<BR>&gt;=== message truncated ===<BR>&gt;<BR></FONT></BLOCKQUOTE></div></html>




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