Questions Regarding the .NET RFP
- To: net-rfp-comments@xxxxxxxxx
- Subject: Questions Regarding the .NET RFP
- From: tdurham@xxxxxxxxxxxx
- Date: Fri, 3 Dec 2004 09:43:13 -0800
.NET RFP Questions:
1) Is the migration of .NET from thin to thick a requirement of the RFP? If
not, will a recommendation to migrate to thick be considered more attractive
than a recommendation to remain thin?
2) Will applicants be required to fill in web forms in a manner similar to
the sTLD process, or may we submit materials in our own formats? The
checklist indicates "printed, signed..." applications must be sent to ICANN,
indicating a physical document. Can you provide additional detail?
3) In section 2 #5a, the rfp requests applicants to "...indicate how your
proposed registry service compares against the current service (as defined
as .NET Registry Operator's Monthly Reports over the past 12 months) and
indicate how you could enhance the service." Since the .NET Registry
Operator's Monthly Reports combine .COM and .NET results, it is not possible
to ascertain the "current service" for .NET. Can ICANN (or the incumbent)
provide a more detailed description that will enable a comparison consistent
enough to facilitate evaluation by the evaluators?
4) In Section 2 #5bxvii, applicants are asked to detail their "...Ability to
support the current feature functionality of .NET, including IDN's, support
of IPv6, DNSSEC." "Maintaining existing functional capabilities..." is also
included in Section 8. Will ICANN require the incumbent to detail these
feature functionalities such that a comparison can be made?
5) In Section 6, applicants are asked to describe "The ability and
commitment to provide even higher levels of security and stability than
those offered in the current operation of the .NET registry...". Can ICANN
provide details regarding the current levels so that a comparison can be
6) In Section 8, Transition Plan, VeriSign is excused. However, the .NET
registry may move to EPP and /or a thick model regardless of the operator.
How does ICANN propose to fairly evaluate different applications on the
Transition Plan criterion if a key expected applicant (the incumbent)
provides no such plans?
7) In the confirmation section, applicants are asked to certify that "...the
registry operator will comply with all existing consensus policies of ICANN
and any which are developed via the ICANN process in the future." Since the
RFP does not require a record of past adherence to ICANN policies, should
applicants conclude that a record of past compliance is immaterial to this
8) What is the expected term of the contract?