ICANN/GNSO GNSO Email List Archives

[council]

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

RE: [council] Verisign signs the root

  • To: "GNSO Council " <council@xxxxxxxxxxxxxx>
  • Subject: RE: [council] Verisign signs the root
  • From: "Tim Ruiz" <tim@xxxxxxxxxxx>
  • Date: Thu, 04 Jun 2009 03:37:49 -0700
  • List-id: council@xxxxxxxxxxxxxx
  • Reply-to: "Tim Ruiz" <tim@xxxxxxxxxxx>
  • Sender: owner-council@xxxxxxxxxxxxxx
  • User-agent: Web-Based Email 5.0.17
Why not allocate it to VeriSign? It actually makes the most sense.
Currently, ICANN/IANA make requests for root zone changes (with DOC
approval) to VeriSign who actually makes and deploys the changes. That's
the arrangement through their Cooperative Agreement with the DOC. It has
been working well and keeps ICANN from creeping into operational
responsibilities. ICANN is supposed to be a coordinating body. What do
you think their budget will look like if they start expanding their
mission?

Tim

-------- Original Message --------
Subject: [council] Verisign signs the root
From: Adrian Kinderis <adrian@xxxxxxxxxxxxxxxxxx>
Date: Thu, June 04, 2009 5:27 am
To: Council GNSO <council@xxxxxxxxxxxxxx>

  http://icann.org/en/announcements/announcement-2-03jun09-en.htm
 
 This is sure to make for some interesting conversation in Sydney.
 
 Quite frankly I am surprised to see this. How is this function simply
allocated to VeriSign (a U.S. Public Company) by ICANN and the DOC?
 
 Perhaps we could add this to the GNSO agenda somewhere?
 
 Thanks.
 
 
 Adrian Kinderis
<<< Chronological Index >>>    <<< Thread Index >>>