Re: [alac] Re: .NET FYI

[Bret Fausett <bfausett@xxxxxxxxxxxxxxxx>]

At out meeting with the Ombudsperson in Mar del Plata, Mr. Fowlie noted 
that if the ALAC were to comment on something and have that comment 
ignored (actually or apparently), we would have standing to seek his 
office's assistance in getting an explanation from the ICANN staff and 
board. This is one decision in which we might want to try this. If 
Verisign is the best applicant, so be it, but I would simply like 
someone to explain to me why ICANN's contention that Verisign is in 
breach of its existing .NET agreement (see, sitefinder, et al.) was not 
a factor in the award process. It still boggles my mind.

Wendy Seltzer wrote:

> Sometimes I wonder why we even bother commenting...
>
> --Wendy
>
> At 1:48 PM -0700 6/9/05, Denise Michel wrote:
>
> > http://www.icann.org/
> >
> > ICANN Board Designates VeriSign to Retain Control of .NET Registry
> >
> > 8 June 2005
> >
> > Marina del Rey, CA - 8 June 2005 - ICANN's Board has named VeriSign, 
> > Inc. as the designated .NET successor registry. ICANN has also 
> > approved entering into a new agreement with VeriSign for their 
> > continued management of the .NET registry for six additional years. 
> > This announcement is the culmination of the .NET RFP and successor 
> > registry process that began on 6 March 2004 and included an 
> > independent evaluation of VeriSign and four other applicants.
> >
> > In taking this action ICANN's Board considered the entire RFP 
> > Process, an independent evaluator's report, Internet community 
> > comments and the terms of the new agreement.
> >
> > ICANN hired Telcordia Technologies, Inc. (an independent third party) 
> > to conduct the evaluation of the applications and the qualifications 
> > of the applicants. In April, Telcordia declared that all five 
> > applicants were capable of running the registry for .NET but gave the 
> > highest ranking to the incumbent registry, VeriSign. In May, 
> > Telcordia confirmed this ranking after evaluating an additional round 
> > of comments from all five applicants.
> >
> > VeriSign's current agreement for .NET is scheduled to run out on 30 
> > June 2005. The agreed framework for ICANN and VeriSign's new 
> > arrangement will be set out in a new .NET Registry agreement which 
> > will strike a balance between innovation and business certainty, with 
> > the need to ensure competition, security and stability in the domain 
> > name system.
> >
> > Commenting on the designation, Dr. Paul Twomey, President and CEO of 
> > ICANN, stated: "We would like to thank all five qualified applicants, 
> > the entire Internet community, ICANN's Generic Supporting 
> > Organization, and Telcordia for the work in making this a successful 
> > process."
> >
> > A detailed outline of the .NET Successor Registry Process can be 
> > found at the following link:
> > http://icann.org/tlds/dotnet-reassignment/net-rfp-process-summary-08jun05.pdf 
> >
> >
> > Additionally, here are some of the key documents and announcement 
> > from the process:
> >
> > 27 May 2005 Telcordia Report .NET RFP on Evaluation
> > http://icann.org/tlds/dotnet-reassignment/net-rfp-finalreport-issue4-27may05.pdf 
> >
> >
> > 3 May 2005 ICANN Posts Telcordia Review of Findings
> > http://icann.org/tlds/dotnet-reassignment/review-of-findings-03may05.pdf
> >
> > 20 Jan 2005 ICANN Receives Five Applications to Operate .NET
> > http://icann.org/announcements/announcement-19jan05.htm
> >
> > 12 Dec 2004 ICANN .NET Reassignment RFP
> > http://icann.org/tlds/dotnet-reassignment/net-rfp-final-10dec04.pdf
> >
> > 5 Aug 2004 Final Report from the GNSO on .NET Criteria
> > http://www.gnso.icann.org/issues/dotnet/dotnet-reportv9.pdf
> >
> > 29 Jun 2004 Final Procedure for Designating Subsequent .NET Registry 
> > Operator
> > http://www.icann.org/announcements/announcement-29jun04.htm
> >
> > 6 Mar 2004 ICANN Board Resolution regarding Preparation for the 
> > Designation of a Transparent Procedure for Designating a Subsequent 
> > .NET Registry Operator
> > http://www.icann.org/minutes/rome-resolutions-06mar04.htm

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature