RE: AW: AW: [gnso-trans-wg] Some thoughts on approach regarding the
Tim and all, I received Tom's paper OK. I've saved it and now try to relay the saved copy. Also saved it as a web page. Hope either works... Best regards Olof -----Original Message----- From: owner-gnso-trans-wg@xxxxxxxxx [mailto:owner-gnso-trans-wg@xxxxxxxxx] On Behalf Of Tim Ruiz Sent: den 23 januari 2008 18:05 To: Thomas Keller Cc: gnso-trans-wg@xxxxxxxxx Subject: RE: AW: AW: [gnso-trans-wg] Some thoughts on approach regarding the Sorry Tom. Same problem. Can you give me a summary or just paste it into the body of the email? Tim -------- Original Message -------- Subject: AW: AW: [gnso-trans-wg] Some thoughts on approach regarding the From: "Thomas Keller" <tom@xxxxxxxx> Date: Wed, January 23, 2008 10:15 am To: "'Tim Ruiz'" <tim@xxxxxxxxxxx>, <gnso-trans-wg@xxxxxxxxx> Ok, next try ;) tom -----Ursprüngliche Nachricht----- Von: owner-gnso-trans-wg@xxxxxxxxx [mailto:owner-gnso-trans-wg@xxxxxxxxx] Im Auftrag von Tim Ruiz Gesendet: Mittwoch, 23. Januar 2008 16:38 An: gnso-trans-wg@xxxxxxxxx Betreff: RE: AW: [gnso-trans-wg] Some thoughts on approach regarding the Tom, your doc came in as garbage embedded in the message of the email (see below) instead of as an attachment. Haven't seen that before so not sure what happened. Could you try resending it to me? Tim=20 -------- Original Message -------- Subject: AW: [gnso-trans-wg] Some thoughts on approach regarding the transfer issues From: "Thomas Keller" <tom@xxxxxxxx> Date: Wed, January 23, 2008 9:24 am To: "'Olof Nordling'" <olof.nordling@xxxxxxxxx>, <gnso-trans-wg@xxxxxxxxx> Hello, I basically followed Olofs suggestion with the exception that I only created three groups and not five. Please have a look at the attached document for my first shot. As you will see I left the prioritization of the former TF as they are and just arranged the issues in groups following the ranking. Best, tom -----Urspr=FCngliche Nachricht----- Von: owner-gnso-trans-wg@xxxxxxxxx [mailto:owner-gnso-trans-wg@xxxxxxxxx] Im Auftrag von Olof Nordling Gesendet: Montag, 21. Januar 2008 17:45 An: gnso-trans-wg@xxxxxxxxx Betreff: [gnso-trans-wg] Some thoughts on approach regarding the transfer issues Dear all, Having re-read the document from Ross' prioritization committee (at http://gnso.icann.org/drafts/irdx-policy-priorities-20dec07.pdf ) I just wanted to share some thoughts with you: 1. According to a statement at the end of the paper "those issues scoring 8 or higher enjoy the broadest support from the committee". That would imply that issues 1 - 5 are in that group. 2. We could consider this top group in the listed order and see if any issue therein could usefully be grouped with any other issue with lower priority with a view to a PDP. Perhaps, for example, that issue 1 could be grouped with issue 7? 3. Then such "PDP embryos" could be further considered from the perspectives of, for example, a) potential importance to the registrants, b) likelihood of reaching consensus, c) cost/ease of implementation of a possible outcome etc - and, low and behold, a proposed PDP running order would emerge like magic (?). Just my three Euro-cents to start our discussions... Best regards Olof Attachment:
transfer_grouping_draftv1.doc --- Begin Message ---<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40";> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 11"> <meta name=Originator content="Microsoft Word 11"> <link rel=File-List href="transfer_grouping_draftv1_files/filelist.xml"> <title>Operational issues</title> <!--[if gte mso 9]><xml> <o:DocumentProperties> <o:Author>tom</o:Author> <o:Template>Normal</o:Template> <o:LastAuthor>home</o:LastAuthor> <o:Revision>2</o:Revision> <o:TotalTime>1</o:TotalTime> <o:LastPrinted>2008-01-23T14:50:00Z</o:LastPrinted> <o:Created>2008-01-23T17:36:00Z</o:Created> <o:LastSaved>2008-01-23T17:36:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>656</o:Words> <o:Characters>3742</o:Characters> <o:Company>1&1InternetAG</o:Company> <o:Lines>31</o:Lines> <o:Paragraphs>8</o:Paragraphs> <o:CharactersWithSpaces>4390</o:CharactersWithSpaces> <o:Version>11.9999</o:Version> </o:DocumentProperties> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:GrammarState>Clean</w:GrammarState> <w:HyphenationZone>21</w:HyphenationZone> <w:ValidateAgainstSchemas/> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> <w:UseWord2002TableStyleRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" LatentStyleCount="156"> </w:LatentStyles> </xml><![endif]--> <style> <!-- /* Font Definitions */ @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:1627421319 -2147483648 8 0 66047 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; mso-ansi-language:DE; mso-fareast-language:DE;} span.GramE {mso-style-name:""; mso-gram-e:yes;} @page Section1 {size:612.0pt 792.0pt; margin:70.85pt 70.85pt 2.0cm 70.85pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 10]> <style> /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman"; mso-ansi-language:#0400; mso-fareast-language:#0400; mso-bidi-language:#0400;} </style> <![endif]--> </head> <body lang=EN-US style='tab-interval:35.4pt'> <div class=Section1> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><b style='mso-bidi-font-weight:normal'><span lang=EN-GB style='font-size:10.0pt; font-family:"Courier New";mso-ansi-language:EN-GB'>Enhancements to the current operational rules of the transfer policy<o:p></o:p></span></b></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>1. <span class=GramE>j</span>. Whether there could be a way for registrars to make Registrant Email Address data available to one another. Currently there is no way of automating approval from the Registrant, as the Registrant Email Address is not a required field in the registrar Whois. This slows down and/or complicates the process for registrants, especially since the Registrant can overrule the Admin Contact. (CT5.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>5. <span class=GramE>q</span>. Whether standards or best practices should be implemented regarding use of Registrar Lock status (e.g., when it may/may not, should/should not be applied). (CT8.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>6. <span class=GramE>h</span>. <span class=GramE>Whether provisions on time-limiting FOAs should be implemented to avoid fraudulent transfers out.</span> For example, if a Gaining Registrar sends and receives an FOA back from a transfer contact, but the name is locked, the registrar may hold the FOA pending adjustment to the domain name status, during which time the registrant or other registration information may have changed<span class=GramE>.(</span>CT9.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>7. <span class=GramE>c</span>. <span class=GramE>Whether additional provisions on undoing inappropriate transfers are needed, especially with regard to disputes between a Registrant and Admin Contact.</span> The policy is clear that the Registrant can overrule the AC, but how this is implemented is currently at the discretion of the registrar. (CT9.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>15. <span class=GramE>i</span>. Whether requirements should be in place for Registrars of Record to send an FOA, and/or receive the FOA back from Transfer Contact before acking a transfer<span class=GramE>.(</span>13.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>18. <span class=GramE>p</span>. Whether the process could be streamlined by a requirement that<span style='mso-spacerun:yes'> </span><o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span class=GramE><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New"; mso-ansi-language:EN-GB'>registries</span></span><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language:EN-GB'> use IANA IDs for registrars rather than proprietary IDs.(16.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><b style='mso-bidi-font-weight:normal'><span lang=EN-GB style='font-size:10.0pt; font-family:"Courier New";mso-ansi-language:EN-GB'>Enhancements to the current transfer dispute policy<o:p></o:p></span></b></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>2. <span class=GramE>o</span>. <span class=GramE>Whether a process for urgent return/resolution of a domain name should be developed, as discussed within the SSAC hijacking report (<span lang=DE style='mso-ansi-language:DE'><a href="http://www.icann.org/announcements/hijacking-report-12jul05.pdf";><span lang=EN-GB style='mso-ansi-language:EN-GB'>http://www.icann.org/announcements/hijacking-report-12jul05.pdf</span></a></span>; see also <span lang=DE style='mso-ansi-language:DE'><a href="http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm";><span lang=EN-GB style='mso-ansi-language:EN-GB'>http://www.icann.org/correspondence/cole-to-tonkin-14mar05.htm</span></a></span>).</span><span style='mso-spacerun:yes'> </span>(CT6.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>4. <span class=GramE>e</span>. Whether reporting requirements for registries and dispute providers should be developed, in order to make precedent and trend information available to the community and allow reference to past cases in dispute submissions. (CT7.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>8. <span class=GramE>d</span>. <span class=GramE>Whether additional provisions should be included in the TDRP on how to handle disputes when multiple transfers have occurred.</span> (CT10.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>14. <span class=GramE>b</span>. Whether review of registry-level dispute decisions is <span class=GramE>needed(</span>some complaints exist about inconsistency).(CT13.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>16. <span class=GramE>a</span>. Whether dispute options for registrants should be developed and implemented as part of the policy (registrants currently depend on registrars to initiate a dispute on their behalf)<span class=GramE>.(</span>14.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>19. <span class=GramE>f</span>. Whether requirements or best practices should be put into place <span class=GramE>for<span style='mso-spacerun:yes'> </span>registrars</span> to make information on transfer dispute resolution options available to registrants.(CT16.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><b style='mso-bidi-font-weight:normal'><span lang=EN-GB style='font-size:10.0pt; font-family:"Courier New";mso-ansi-language:EN-GB'>New Issues related to the current transfer policy<o:p></o:p></span></b></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>3. <span class=GramE>g</span>. Whether there is need for other options for electronic authentication (e.g., security token in FOA) due to security concerns on use of email addresses (potential for hacking or spoofing). (CT6.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>9. <span class=GramE>m</span>. <span class=GramE>Whether special provisions are needed for change of registrant simultaneous to transfer or within a period after transfer.</span> The policy does not currently deal with change of registrant, which often figures in hijacking cases. (CT10.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>10. <span class=GramE>n</span>. Whether existing penalties for policy violations are sufficient or if additional provisions/penalties for specific violations should be added into the policy. (CT10.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>11. <span class=GramE>r</span>. <span class=GramE>Whether registrants should be able to retrieve authInfo codes from third parties other than the registrar.</span> (CT12.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>12. <span class=GramE>s</span>. Whether the policy should incorporate provisions for <span class=GramE>handling<span style='mso-spacerun:yes'> </span>“</span>partial bulk transfers” between registrars </span><span lang=EN-GB style='font-size:10.0pt;font-family:Tahoma;mso-ansi-language:EN-GB'>–</span><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'> that is, transfers involving a number of names but not the entire group of names held by the losing registrar. (CT12.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>13. <span class=GramE>k</span>. Whether additional provisions relating to transfer <span class=GramE>of<span style='mso-spacerun:yes'> </span>registrations</span> involving various types of Whois privacy services should be developed as part of the policy. (CT13.0)<o:p></o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'><o:p> </o:p></span></p> <p class=MsoNormal style='mso-layout-grid-align:none;text-autospace:none'><span lang=EN-GB style='font-size:10.0pt;font-family:"Courier New";mso-ansi-language: EN-GB'>17. <span class=GramE>l</span>. Whether additional requirements regarding Whois history should be developed, for change tracking of Whois data and use in resolving disputes<span class=GramE>.(</span>14.0)<o:p></o:p></span></p> <p class=MsoNormal><span lang=EN-GB style='mso-ansi-language:EN-GB'><o:p> </o:p></span></p> </div> </body> </html>
|