[Gnso-impl-thickwhois-rt] [for iRT review] Draft Thick Whois Transition Policy for .COM, .NET, and .JOBS
theo geurts
gtheo at xs4all.nl
Wed Sep 7 20:08:59 UTC 2016
Agreed, this is works better Roger.
Thanks,
Theo
On 7-9-2016 20:41, Anderson, Marc wrote:
>
> Hey Roger,
>
> I like this definition, thank you for proposing it. I agree this is
> clearer and reads better being consistent with the Think definition.
> I support this change.
>
> Thanks,
> Marc
>
> *From:*gnso-impl-thickwhois-rt-bounces at icann.org
> [mailto:gnso-impl-thickwhois-rt-bounces at icann.org] *On Behalf Of
> *Roger D Carney
> *Sent:* Wednesday, September 07, 2016 2:28 PM
> *To:* gnso-impl-thickwhois-rt at icann.org
> *Subject:* Re: [Gnso-impl-thickwhois-rt] [for iRT review] Draft Thick
> Whois Transition Policy for .COM, .NET, and .JOBS
>
> Good Afternoon,
>
> On the call and in my email to the list, I suggested that the
> definition for Thick (Registrations) could be made clearer and Dennis
> asked that I provide some language suggestions. So being more
> consistent with the Thin definition, how about something like:
> “/domain name for which the sponsoring Registrar provides a copy of
> the associated contact information to the Registry Operator. Registry
> Operator maintains the technical information (e.g., name servers,
> statuses, creation date) and the sponsoring Registrar associated with
> the domain name. Contact information for the domain name is maintained
> by the sponsoring Registrar./”
>
> Thanks
>
> Roger
>
> *From:*gnso-impl-thickwhois-rt-bounces at icann.org
> <mailto:gnso-impl-thickwhois-rt-bounces at icann.org>
> [mailto:gnso-impl-thickwhois-rt-bounces at icann.org] *On Behalf Of
> *Dennis Chang
> *Sent:* Tuesday, September 06, 2016 4:54 PM
> *To:* gnso-impl-thickwhois-rt at icann.org
> <mailto:gnso-impl-thickwhois-rt at icann.org>
> *Subject:* Re: [Gnso-impl-thickwhois-rt] [for iRT review] Draft Thick
> Whois Transition Policy for .COM, .NET, and .JOBS
>
> Dear Thick Whois IRT,
>
> Thank you for your participation and contribution today.
>
> Attached is the draft policy document we worked on at the meeting
> together: one version with redline and one clean as V2.
>
> We’ll continue the team edit at our meeting next week to finalize the
> document.
>
> Same time same day same call in info.
>
> Agenda on IRT wiki:
>
> * Transition from thin to thick
> o Draft Consensus Policy document review - continue from section 2.9
> o Public Comment readiness
> * Whois Conflict Procedure (if time permits)
> * Draft memo to GNSO Council regarding Privacy (if time permits)
> * Next steps
>
> —
>
> Kind Regards,
>
> Dennis S. Chang
>
> GDD Services & Engagement Program Director
>
> +1 213 293 7889
>
> Skype: dennisSchang
>
> www.icann.org <http://www.icann.org> "One World, One Internet"
>
> *From: *<gnso-impl-thickwhois-rt-bounces at icann.org
> <mailto:gnso-impl-thickwhois-rt-bounces at icann.org>> on behalf of
> Dennis Chang <dennis.chang at icann.org <mailto:dennis.chang at icann.org>>
> *Date: *Thursday, September 1, 2016 at 5:05 PM
> *To: *"gnso-impl-thickwhois-rt at icann.org
> <mailto:gnso-impl-thickwhois-rt at icann.org>"
> <gnso-impl-thickwhois-rt at icann.org
> <mailto:gnso-impl-thickwhois-rt at icann.org>>
> *Subject: *[Gnso-impl-thickwhois-rt] [for iRT review] Draft Thick
> Whois Transition Policy for .COM, .NET, and .JOBS
>
> Dear Thick Whois Policy Implementation Review Team,
>
> Attached for your review is our initial draft of the Thick Whois
> Transition Policy for .COM, .NET and .JOBS. The draft Policy includes
> the various elements discussed in our recent meeting on this topic.
>
> As you review the draft, you will find bracketed text in four
> sections: sections 2.9, 2.10, 3.4 and 3.5. These sections are
> bracketed because they reference the Registry Registration Data
> Directory Services**Consistent Labeling and Display Policy and the
> Registration Data Access Protocol gTLD Profile. As you may be aware, a
> Request for Reconsideration (RfR) was submitted by the Registries
> Stakeholder Group in August regarding the Registry Registration Data
> Directory Services Consistent Labeling and Display Policy
> <https://www.icann.org/resources/pages/rdds-labeling-policy-2016-07-26-en>__that
> was published on 26 July 2016. The RfR objects to the inclusion of
> RDAP in the Consensus Policy. While the RfR goes through its own
> process, we thought it was important to continue progressing the
> implementation project with the goal of opening Public Comment in
> September and announcing the Transition Policy by 1 February 2017 per
> our schedule. Therefore, the text is bracketed as it may need to be
> revisited pending the resolution of the RfR and we wanted to directly
> call the IRT’s attention to it.
>
> We will review all contents of the document at our next IRT meeting as
> a team but please provide your comments in advance via email if possible.
>
> Thank you for your support!
>
> —
>
> Kind Regards,
>
> Dennis S. Chang
>
> GDD Services & Engagement Program Director
>
> +1 213 293 7889
>
> Skype: dennisSchang
>
> www.icann.org <http://www.icann.org> "One World, One Internet"
>
>
>
> _______________________________________________
> 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/20160907/90e781ca/attachment-0001.html>
More information about the Gnso-impl-thickwhois-rt
mailing list