ICANN ICANN Email List Archives

[dssa]


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

Re: [dssa] hm. does anybody have an authoritative source for the definition of "core registry functions"?

  • To: Patrick Jones <patrick.jones@xxxxxxxxx>
  • Subject: Re: [dssa] hm. does anybody have an authoritative source for the definition of "core registry functions"?
  • From: "Mike O'Connor" <mike@xxxxxxxxxx>
  • Date: Thu, 12 Jan 2012 07:42:58 -0600

hi Patrick,

so is there a definitive spot to go look for the current state of the 
list/architecture?  note the subject line of the post -- that's really what i'm 
on the hunt for…

mikey


On Jan 12, 2012, at 7:43 AM, Patrick Jones wrote:

> 
> Mikey -
> 
> As Keith noted below (and Greg Aaron as well), we tried to limit critical
> registry functions in the context of those functions that were critical for
> the operation of a TLD for the protection of the registrants in that TLD and
> ensure confidence in the DNS. I'm fairly sure of the DSSA group, that Keith,
> Greg, Rick Wilhelm and Jim Galvin were all part of the registry
> failover/registry continuity discussions that started in 2006/07 and have
> been active in it since. Several ccTLD representatives also reviewed and
> provided input from their perspective and experience on this work between
> 2007-2009. And At Large contributed as well.
> 
> Patrick 
> 
> 
> On 1/8/12 12:52 PM, "Drazek, Keith" <kdrazek@xxxxxxxxxxxx> wrote:
> 
>> 
>> 
>> Hi Mikey, 
>> 
>> 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.
>> 
>> http://www.icann.org/en/registries/continuity/gtld-registry-continuity-plan-25
>> apr09-en.pdf
>> 
>> 
>> Earlier definitions had a slightly longer lists of six or more:
>> 
>> http://www.icann.org/en/registries/reports/registry-failover-01jun07.htm#ancho
>> r3 (see Section 3 of the 2007 Registry Failover Report)
>> 
>> http://www.icann.org/en/registries/continuity/gtld-registry-continuity-plan-25
>> apr09-en.pdf (see page 4 of the 2009 Registry Continuity Plan)
>> 
>> 
>> Hope this helps. 
>> 
>> Regards, Keith
>> 
>> 
>> 
>> 
>> Keith Drazek
>> Director of Policy
>> kdrazek@xxxxxxxxxxxx
>> 
>> m: +1-571-377-9182
>> 21345 Ridgetop Circle Dulles, VA 20166
>> 
>> VerisignInc.com 
>> 
>> 
>> 
>> -----Original Message-----
>> From: owner-dssa@xxxxxxxxx [mailto:owner-dssa@xxxxxxxxx] On Behalf Of Mike
>> O'Connor
>> Sent: Sunday, January 08, 2012 9:20 AM
>> To: dssa@xxxxxxxxx
>> Subject: [dssa] hm. does anybody have an authoritative source for the
>> definition of "core registry functions"?
>> 
>> 
>> hi all,
>> 
>> 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?
>> 
>> thanks,
>> 
>> mikey
>> 
>> - - - - - - - - -
>> phone  651-647-6109
>> fax    866-280-2356
>> web  http://www.haven2.com
>> handle OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)
>> 
>> 
>> 
> 
> 

- - - - - - - - -
phone   651-647-6109  
fax             866-280-2356  
web     http://www.haven2.com
handle  OConnorStP (ID for public places like Twitter, Facebook, Google, etc.)





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

Privacy Policy | Terms of Service | Cookies Policy