[pdp-pcceg-feb06] Information Collected by Registries

["Neuman, Jeff" <Jeff.Neuman@xxxxxxxxxx>]

All,

 

I am still working with the registries to produce an official report on
what information registries collect and what uses they make of the data.
I was optimistic that this could be completed prior to this weekend to
submit to the group, but this is taking more time than I thought.  In
the interest of trying to keep the discussion moving, I wanted to
provide you all with an outline of the information that I have been
putting together on the information collected by a registry.

 

This is an informal submission to guide discussion, but is not intended
as a formal report or response to include as part of the Task Force
report.  This is still being worked on by the registry group.

 

I will not be in MdR this weekend, but am going to try and participate
remotely.  

 

 
Data Collected (or could be collected)
 
 
I.  Registration Information- - Data Collected from Registrars as part
of the domain name registration process.
 
   A.      Thin Unsponsored Registries

i.          Domain Name

ii.         Whois Server

iii.        Referral URL

iv.        Nameserver(s)

v.         Update Date

vi.        Creation Date

vii.       Expiration Date
 
   B.            Thick Unsponsored Registries

 

i.        All Thin Registry Information

ii.       Administrative Contact Information

iii.      Technical Contact Information

iv.       Billing Contact Information
 

   C.   Sponsored / Restricted TLDs - In the process of verifying that
all existing sponsored and restricted TLDs are "thick".

 

i.                     All Information in 1(b) above

ii.                   Information deemed by Registry as needed for TLD
(and set forth in Charter)

iii.                  Other Information specific to be authenticated in
TLD (also set forth in Charter)

 

 

II.          Information required for ICANN Reports: See
http://www.icann.org/tlds/agreements/verisign/appendix-04-01mar06.htm
for an example
 

a.        Accredited Registrar Status. Number of registrars that (1) are
operational, (2) ramp-up (registrars that have submitted all paperwork
to the registry, have been accredited by ICANN, but are just entering
"operational testing", and (3) registrars that have been
ICANN-Accredited, but have not yet submitted all required paperwork or
have not yet been granted access to "operational testing"

b.      Service Level Agreement Performance. Service Level Agreement
performance of the applicable registry; usually with respect to
availability, response time, etc.

c.      TLD Zone File Access Activity.  Number of zone file access
passwords at end of the reporting month; tells registry who has ability
to download copies of the zone file.

d.      Whois Service Activity. The number of Whois queries during the
reporting month.

e.      Total Number of Transactions by Subcategory by Month. The total
number of transactions during the reporting month, in the following
subcategories: adds, deletes, modifies, checks, renews, transfers,
restores; 

f.       Daily Transaction Range. Tabulate the number of total daily
transactions. The range of transaction volume should be shown for each
month, along with the average daily transaction volume.

g.      Per-Registrar Activity Report -  The number of applicable
transactions under (e) and (f) above measured per registrar. 
 

III.         DNS Resolution

      a.        Queries to the TLD Nameservers - This can be broken down
by node, nameserver cluster, etc. by hour, day, week, month, etc.

      b.        Responses/Answers from the TLD Nameservers - this can be
broken down as above.

 

Jeffrey J. Neuman, Esq. 
Sr. Director, Law, Advanced Services  & Business Development 

NeuStar, Inc. 
Loudoun Tech Center 
46000 Center Oak Plaza 
Sterling, VA 20166 
p: (571) 434-5772 
f: (571) 434-5735 
e-mail: Jeff.Neuman@xxxxxxxxxx <mailto:Jeff.Neuman@xxxxxxxxxx>  

 

PRIVILEGE AND CONFIDENTIALITY NOTICE:  The information contained in this
e-mail communication and any attached documentation may be privileged,
confidential or otherwise protected from disclosure and is intended only
for the use of the designated recipient(s).  If the reader or recipient
of this communication is not the intended recipient, or an employee or
agent of the intended recipient who is responsible for delivering it to
the intended recipient, you are hereby notified that any review,
dissemination, distribution, copying or other use of this communication
is strictly prohibited.  If you have received this communication in
error, please immediately notify us by return e-mail and promptly delete
the original electronic e-mail communication and any attached
documentation.  Receipt by anyone other than the intended recipient is
not a waiver of any attorney-client or work-product privilege.