Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Registrar Constituency GNSO Update

A copy of an update that I presented to the GNSO Registrar constituency on October 24, 2006

  • Be the first to comment

  • Be the first to like this

Registrar Constituency GNSO Update

  1. 1. Registrar Update <ul><li>Council // Whois // Transfers </li></ul>
  2. 2. GNSO Council // Current Agenda <ul><li>IDN TLDs </li></ul><ul><li>Policies for Registry Contracts </li></ul><ul><li>New gTLDs </li></ul><ul><li>Whois </li></ul><ul><li>Data Accuracy Review </li></ul><ul><li>Transfers Review </li></ul><ul><li>GNSO Reform </li></ul>
  3. 3. Whois <ul><li>Operational Point of Contact Proposal is moving forward. </li></ul><ul><ul><li>subject to active discussion over the past year. </li></ul></ul><ul><ul><li>many minor changes, but substantially similar to what has been presented at prior meetings </li></ul></ul>
  4. 4. Whois //OPOC <ul><li>All registries publish thin data set </li></ul><ul><li>Registrars only publish name of registrant, and contact information for an “agent” authorized to act on the registrant’s behalf </li></ul><ul><li>Admin, Tech, etc. contacts are deprecated </li></ul><ul><li>Registrars implement best practices for third party access to data not published in Whois //OPOC </li></ul><ul><li>Data continues to be published via Whois:43 and Whois //WWW </li></ul><ul><li>Current proposal is online at http://tinyurl.com/y3mt63 </li></ul>
  5. 5. Whois //New Proposal <ul><li>In the last 30 days, IPC/BC/ISPC bloc have published last minute proposal dubbed “special considerations” </li></ul><ul><li>Requires all data to be published in centralized thick registry. </li></ul><ul><li>Registrants can “opt-out” of publication </li></ul><ul><li>opt-outs would be processed by 3rd party centralized service </li></ul><ul><li>additional costs would be covered by additional “tax” applied to all registrations/renewals. </li></ul>
  6. 6. New TLDs <ul><li>Closing in on final report </li></ul><ul><ul><li>New TLDs are being recommended </li></ul></ul><ul><ul><li>“heavy” application and review process </li></ul></ul><ul><ul><ul><li>pre-application publication </li></ul></ul></ul><ul><ul><ul><li>review process </li></ul></ul></ul><ul><ul><ul><li>application fees fund process </li></ul></ul></ul>
  7. 7. New TLDs <ul><li>Grants may be made available to cover some application fees based on applicant need. </li></ul><ul><li>Applicants must meet pre-defined technical standards, all consensus policies (past and present) </li></ul><ul><li>String checks will be applied (approval process includes public and government consultation) </li></ul>
  8. 8. New TLDs <ul><li>String criteria </li></ul><ul><ul><li>not visually or phonetically confusingly similar to existing strings </li></ul></ul><ul><ul><li>not infringe the rights of a third party </li></ul></ul><ul><ul><li>not cause technical issues (i.e. “.exe” </li></ul></ul><ul><ul><li>not contrary to public policy, morality or deceptive </li></ul></ul>
  9. 9. New TLDs <ul><li>String Criteria (cont) </li></ul><ul><ul><li>not reserved per RFC 2026 </li></ul></ul><ul><li>New DRP to cover trademark interests </li></ul><ul><li>Applicants must use registrars </li></ul><ul><li>Allocated on a FCFC, “grant as you go” basis </li></ul>
  10. 10. New TLDs <ul><li>Will use frame agreement to bring basic consistency to registry agreements </li></ul><ul><ul><li>proposed 10 year term for new agreements </li></ul></ul><ul><ul><li>renewal expectancy </li></ul></ul><ul><ul><li>sanctions and termination rights </li></ul></ul><ul><ul><li>adherence to IDN standards </li></ul></ul>
  11. 11. New TLDs <ul><li>adherence to IDN standards </li></ul><ul><li>ICANN may refer to national authorities to ensure compliance wrt market or pricing power </li></ul><ul><li>ICANN should take consistent approach wrt registry fees taking into account regional, economic and business models </li></ul>
  12. 12. questions [email_address] 416.828.8783

×