[Gnso-impl-thickwhois-rt] Thick Whois Policy Language revisions from the IRT meeting on 17 January 2017

Tue Jan 24 18:55:05 UTC 2017

Marc,

Regarding to your point   “reduced validation rules” don’t seem to have an end date....

In the following section for registrar, doesn't it spell out the end day is Feb. 1, 2019 because we MUST migrate all required fields of existing domain names?

1.      The following requirements apply to Registrars only:

Between 1 August 2017 and 1 February 2019, Registrars MUST migrate to the relevant Registry Operator all required fields of Existing Domain Names that are available in the Registrar database that enable the Registry Operator to comply with WHOIS (available via port 43) and web-based directory services requirements described in Section 1 of ...

Joyce

  ----- Original Message ----- 
  From: Anderson, Marc 
  To: dennis.chang at icann.org ; gnso-impl-thickwhois-rt at icann.org 
  Sent: Monday, January 23, 2017 7:03 PM
  Subject: Re: [Gnso-impl-thickwhois-rt] Thick Whois Policy Language revisions from the IRT meeting on 17 January 2017

  Dennis,

  Thank you for providing the updated redlines of the CL&D and Transition policy documents.

  In the CL&D Policy document the “not to be deployed before date” was removed as agreed to on our last call (being that it occurs in the past).  Under Implementation Notes, section 2 explains the need for the “not to be deployed before date”.  That section isn’t needed anymore and should be removed as well.

  In the Thick Transition policy document section 2.5 references Section 1 of Specification 4 of the “Base Registry Agreement approved on 9 January 2014” (“Base Registry Agreement”), but it does not include the “or subsequent amendments thereto” language.  In all other instances where the “Base Registry Agreement” is referenced, the “or subsequent amendments thereto” languages is included and I believe it is intended to be included in section 2.5 as well.

  Section 2.4 requires registry operators to support contact operations by 1 Aug 2017 but the main purpose of section 2.4 is to define what we’ve referred to in the IRT as the “reduced validation rules”.  Basically instead of implementing contact support in compliance with RFC5733, the registry operator will only require the “contact:id, contact:postalinfo type, and contact:authinfo” fields.  Per our discussions in the IRT this is intended to support registrars during the backfill period (1 Aug 2017 to 1 Feb 2019).  Based on my read of the policy the “reduced validation rules” don’t seem to have an end date.  We don’t want them to extend indefinitely making a non RFC compliant implementation permanent.  Unless I’m missing something, I think this section should be tweaked to give an end date for the “reduced validation rules”.

  Thank you,

  Marc Anderson

  From: gnso-impl-thickwhois-rt-bounces at icann.org [mailto:gnso-impl-thickwhois-rt-bounces at icann.org] On Behalf Of Dennis Chang
  Sent: Tuesday, January 17, 2017 9:56 PM
  To: gnso-impl-thickwhois-rt at icann.org
  Subject: [EXTERNAL] [Gnso-impl-thickwhois-rt] Thick Whois Policy Language revisions from the IRT meeting on 17 January 2017

  Dear Thick IRT,

  Thank you for your participation and support today in reviewing the public comment and decisions made to handle them.

  As promised, we’ve revised the policy language per our discussion at the meeting.

  For CL&D Policy:

  1.       The “not to be deployed before date” was removed per the suggestion. For this policy, this is the only change.

  2.       No change was made for the suggestion to add a “provision for extension to the effective date” as the IRT agreed

  For Transition Policy:

  1.       The clause containing “RDAP” was removed from section 2.10. The resulting language is exactly as Francisco provided in the chat which IRT agreed to.

  2.       Section 2.4 had two changes per the suggestions and agreements by the IRT

  a.       The word “starting” was changed to “by” to offer flexibility for the Registry Operator to provide support earlier. 

  b.       <contact:polstalinfo> was changed to <contact:postalinfo type> to identify the attribute more accurately

  3.       Changes to section 2.8 and 2.9 were made to make it more readable. IRT was already in agreement with the intent of the language and this change was only to make it easier to understand.

  4.       Regarding the suggestion to add “Alternative triggers for waivers,” there was no IRT agreement to make the change and therefore no change was made.

  This is considered the final review by the IRT before the publication and the announcement on 1 February 2017 per our plan.

  One more IRT meeting has been added for next Tuesday as you’ve requested.

  However, it can be cancelled if the IRT provides support for these finalized languages to be in alignment with the Policy Recommendation prior to the meeting date.

  We look forward to your prompt review and continued support. 

  — 

  Kind Regards,

  Dennis S. Chang

  GDD Services & Engagement Program Director

  +1 213 293 7889

  Skype: dennisSchang

  www.icann.org[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/20170124/dc6dd771/attachment.html>