[RAA-WG] Submission, draft 1

[Debbie Garside]

 +1

Best regards

Debbie

> -----Original Message-----
> From: raa-wg-bounces at atlarge-lists.icann.org
> [mailto:raa-wg-bounces at atlarge-lists.icann.org] On Behalf Of
> Danny Younger
> Sent: 19 August 2007 17:33
> To: Vittorio Bertola; RAA-WG at atlarge-lists.icann.org
> Subject: Re: [RAA-WG] Submission, draft 1
>
> Vittorio,
>
> I haven't had a chance yet to do an uninterupted and thorough
> read of the full document, but there is one section (8.1)
> that caught my eye:
>
> "ICANN should require registries to escrow the information
> they have (depending on the registry model, thick or thin) in
> an escrow program with the same characteristics as the
> registrars' one."
>
> As you know, ICANN issued an announcement on 5 March
> 2007 entitled "ICANN gTLD Registry Data Escrow Report"
> wherein ICANN indicated that the gTLD  experiences with the
> current escrow program would be reported on April 30.
>
> That didn't happen on schedule.  Instead we had a report
> issued on 1 June 2007 entitled "Building Towards a
> Comprehensive gTLD Registry Failover Plan"
> that had a section (3.6) devoted to Data Security and Data
> Escrow that listed the following suggested
> improvements:
>
> 1.  Escrow of all information that would be required to
> recreate the registration and restore service to registrants
> 2.  Escrow of all data fields specified in EPP 1.0
> (Extensible Provisioning Protocol, see RFC 4930)[18] 3.
> Status of the name registration 4.  Any registration
> "features" (locks, domain proxy,
> etc.)
> 5.  Transactional data
> 6.  Use of a standard, non-proprietary electronic file
> format, such as XML 7.  Stored data encryption and data
> transmission encrypted 8.  Data signing 9.  Digitally signed
> deposits 10.  Verification of incoming data deposits 11.
> Escrow agent certification and annual certification test 12.
> A requirement in the data escrow agreement that escrow agent
> notify the registry (and registry services provider, if
> applicable) if an escrow deposit is not received 13.  Data
> placed in escrow should be tested to ensure that the data can
> be used to restore registry operations
>
> The document also noted that "ICANN will be issuing an update
> on the data escrow report as part of this project describing
> potential improvements to the data escrow requirements".
>
> Rather than specifying that registry escrow requirements
> should have the same characteristics as the registrar escrow
> program, I think that we should instead commend ICANN on
> their efforts to date and encourage the timely publication of
> the updates that have been promised.  In my view, I think
> that they have this project well under control, and the
> community at this point would best be served by knowing the
> implementation timetable under consideration so that we may
> continue to track the progress being made.
>
> references:
> http://www.icann.org/announcements/announcement-05mar07.htm
> http://www.icann.org/tlds/data-escrow-report05mar07.htm
> http://www.icann.org/registries/reports/registry-failover-01jun07.htm
>
>
>
>
>
> ______________________________________________________________
> ______________________Ready for the edge of your seat?
> Check out tonight's top picks on Yahoo! TV.
> http://tv.yahoo.com/
>
> _______________________________________________
> RAA-WG mailing list
> RAA-WG at atlarge-lists.icann.org
> http://atlarge-lists.icann.org/mailman/listinfo/raa-wg_atlarge
> -lists.icann.org
>
> RAA WG Online:
> https://st.icann.org/alac/index.cgi?registrant_registrar_relations
>
>
>