ICANN ICANN Email List Archives

[gnso-ff-pdp-may08]


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

[gnso-ff-pdp-may08] Line 409, PDF page 18 and footnote 5

  • To: gnso-ff-pdp-May08@xxxxxxxxx
  • Subject: [gnso-ff-pdp-may08] Line 409, PDF page 18 and footnote 5
  • From: Joe St Sauver <joe@xxxxxxxxxxxxxxxxxx>
  • Date: Tue, 2 Sep 2008 11:59:46 -0700

Line 408-411 mentions:

   o Make additional non-private information about registered domains 
   available through DNS-based (not WHOIS[fn5]) queries (e.g., by 
   defining new uses for TXT resource records), perhaps including the 
   age of the domain, the number of name server changes made during a 
   recent defined time interval, and the like

I would also propose adding after line 411 text clarifying that:

   "The DNS-based zone envisioned under this section need not be offered 
   by ICANN itself, nor the registries or registrars. Rather, private
   entities, given bulk access to the required data, might offer that 
   data via DNS or another mechanism in the public interest. ICANN, the 
   registries and the registrars need only provide bulk access to the 
   required data already available through whois (albeit 
   currently available only at ad hoc low query volume levels)."

Footnote 5 states:

   5. A DNS-based system could be queried through automation rather than
   manually. Whois is a manual protocol and is not suitable for real time
   queries.

I propose replacing the last sentence of footnote 5 with: "Whois is
a protocol which, as routinely deployed, generally forbids automated 
queries, and hence is only suitable for ad hoc manual query volumes. 
DNS has demonstrated the ability to scale to extremely large automated
query volumes in support of things like DNS block lists, and should 
not be require the same sort of a priori query traffic volume limits, 
although limits to control demonstrable abuse may still be needed from
time to time.

Regards,

Joe

Disclaimer: all opinions strictly my own



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

Privacy Policy | Terms of Service | Cookies Policy