RE: [dssa] hm. does anybody have an authoritative source for the definition of "core registry functions"?
- To: "dssa@xxxxxxxxx" <dssa@xxxxxxxxx>
- Subject: RE: [dssa] hm. does anybody have an authoritative source for the definition of "core registry functions"?
- From: "Drazek, Keith" <kdrazek@xxxxxxxxxxxx>
- Date: Sun, 8 Jan 2012 17:52:51 +0000
The phrase now used by ICANN is "critical registry functions," which has been
defined most recently through the new gTLD application process. The definition
is in several places in the Applicant Guidebook, including in the section
covering the Continued Operations Instrument.
Earlier definitions had a slightly longer lists of six or more:
(see Section 3 of the 2007 Registry Failover Report)
(see page 4 of the 2009 Registry Continuity Plan)
Hope this helps.
Director of Policy
21345 Ridgetop Circle Dulles, VA 20166
From: owner-dssa@xxxxxxxxx [mailto:owner-dssa@xxxxxxxxx] On Behalf Of Mike
Sent: Sunday, January 08, 2012 9:20 AM
Subject: [dssa] hm. does anybody have an authoritative source for the
definition of "core registry functions"?
i came across the "core registry functions" phrase and thought that might be a
good list for us to have. here's the quote that got me started
"Core registry functions are: access to the shared registry system;
Whois, DNS resolution; data escrow; and DNSSEC"
the list looks like a good scope-defining punch-list for some of our work.
but this is from a Minds and Machines advocacy piece on CircleID and is by no
means authoritative. are they quoting an RFC or something that *is*
authoritative? if so, could you point me in the right direction?
- - - - - - - - -
handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)