[Gnso-impl-thickwhois-rt] RDE Deposit SPEC

[theo geurts]

Hi Chris,

Yes, I thought that is still under discussion with compliance right? Or 
I am mistaken?

@Marc, while I was googling for the exact format I came upon this piece: 
http://www.ironmountain.com/Knowledge-Center/Reference-Library/View-by-Document-Type/Data-Sheets-Brochures/R/Registry-Data-Escrow-FAQ.aspx

  * *gTLDs*: As part of its Registry Agreement with the Internet
    Corporation for Assigned Names and Numbers (ICANN), each gTLD
    Registry Operator must comply with provisions contained within a
    Registry Data Escrow Agreement. That agreement requires gTLD
    Registry Operators to transfer registry data for their TLD on a
    daily basis to a reputable escrow agent to be held in escrow. ICANN
    must be named as a third-party beneficiary under each such escrow
    agreement. Escrowing registry data helps ensure continuity of
    service for the gTLD in the event of a natural disaster, a technical
    failure of a registry, or a security breach within the Domain Name
    System (DNS).

Does this apply for Verisign once they moved over to the Thick Registry 
model? Just making sure we do not get blind sided during the comment 
period regarding contractual obligations and the amount of data required 
for those deposits.

Thanks,

Theo

On 15-6-2016 16:49, Chris Pelling wrote:
> Hi Marc,
>
> I would not trust anything in that document at this time.  ICANN are 
> stating on one hand that privacy information should be included in a 
> deposit as well as underlying information, yet that document states 
> otherwise.
>
> Sorry Theo, I should have replied to this yesterday - but got lost 
> with time.
>
> Kind regards,
>
> Chris
>
> ------------------------------------------------------------------------
> *From: *"Anderson, Marc" <mcanderson at verisign.com>
> *To: *"theo geurts" <gtheo at xs4all.nl>, gnso-impl-thickwhois-rt at icann.org
> *Sent: *Wednesday, 15 June, 2016 15:20:07
> *Subject: *Re: [Gnso-impl-thickwhois-rt] RDE Deposit SPEC
>
> Thank you Theo, I’ll take a look at this.
>
> Thanks,
>
> Marc
>
> *From:*gnso-impl-thickwhois-rt-bounces at icann.org 
> [mailto:gnso-impl-thickwhois-rt-bounces at icann.org] *On Behalf Of *theo 
> geurts
> *Sent:* Tuesday, June 14, 2016 3:25 PM
> *To:* gnso-impl-thickwhois-rt at icann.org
> *Subject:* Re: [Gnso-impl-thickwhois-rt] RDE Deposit SPEC
>
> Hi all,
>
> The RDE deposit spec is located here: 
> https://www.icann.org/en/system/files/files/rde-specs-09nov07-en.pdf
>
> Escrow records shall be compiled into a single (uncompressed) CSV text 
> file or multiple (uncompressed) text files approximately 1 gigabyte or 
> one million rows in size, in compliance with RFC 4180 . In accordance 
> with RFC 4180, the character encoding for the CSV file should be 
> US-ASCII, although UTF-8 is also permissible.
> https://tools.ietf.org/html/rfc4180
>
> I do not see the EPP code/auth code mentioned as a requirement so that 
> makes things more complex, at least more complex then EPP I assume.
>
> Best regards,
>
> Theo Geurts
>
>
> _______________________________________________
> Gnso-impl-thickwhois-rt mailing list
> Gnso-impl-thickwhois-rt at icann.org
> https://mm.icann.org/mailman/listinfo/gnso-impl-thickwhois-rt

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/gnso-impl-thickwhois-rt/attachments/20160615/9eb046eb/attachment-0001.html>