[RDS-WHOIS2-REC4-Compliance] Meeting #7 - Rec 4: Compliance (30 May 2018 @ 16:00 UTC)

[Jean-Baptiste Deroulez]

Dear Compliance subgroup members,

Following today’s call, please find below the decisions reached and action items:

DECISIONS REACHED

  *   Rec #1 to be redrafted to apply to registries not registrars
  *   Rec #2 may be covered under Rec 3
  *   Rec #3 :
     *   (1) Policy or contracts should require that WHOIS indicate whether a domain is on hold due to inaccurate data
     *   (2) Domains on serverHold due to inaccurate data in WHOIS should not be unsuspended without inaccurate data being remedied

  *   Rec #4: Agreed but possibly belongs under Outreach or Accuracy recommendations

  *   Rec #5: Should lead to two related recommendations - one on outreach to raise awareness of bulk WHOIS inaccuracy reporting, and a second on making it easier for registrars to receive multiple inaccuracy reports related to the same problem or the same domain name


  *   Rec #6: Agreed but need to be fleshed out further (for example, that grandfathering should not apply after renewal).

  *   Rec #7: Policy should integrate metrics, measurements, and reporting to ensure that the policy is effective in addressing the issue, and when metrics are defined, compliance would audit, track, report, and enforce as applicable for the policy.



  *   Rec 8: Dig further and consult with Lili

ACTION ITEM(S)

  *   Susan to update draft to reflect decisions reached and respond to Volker's comments

Kind regards,

Jean-Baptiste

From: RDS-WHOIS2-REC4-Compliance <rds-whois2-rec4-compliance-bounces at icann.org> on behalf of Jean-Baptiste Deroulez <jean-baptiste.deroulez at icann.org>
Date: Tuesday, May 29, 2018 at 5:49 PM
To: "rds-whois2-rec4-compliance at icann.org" <rds-whois2-rec4-compliance at icann.org>
Subject: [RDS-WHOIS2-REC4-Compliance] Meeting #7 - Rec 4: Compliance (30 May 2018 @ 16:00 UTC)

Dear Rec #4 Compliance subgroup members,

This is to kindly remind you that your subgroup call #7 [community.icann.org]<https://urldefense.proofpoint.com/v2/url?u=https-3A__community.icann.org_x_2yUFBQ&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=a5VfrQZP4r0Kte2xBJT17IgRyRBHECC3vHSuFP_QBqD22G4dgkHhRZBEhshbjycD&m=C6B_tDQ7L91Ibp3gNdRo9BD0e3qkTjlFrbN2np4SQQA&s=hnrY7g_G4L-3YYtl2UYyKOQgPxH8WxGMrXNoJz-RGWc&e=> is scheduled for tomorrow at 16:00 UTC. Please share in advance any document you would like us to project in Zoom.

You should all have received dial-in details to join this call. If not, please contact us (off list) at rds-whois2-staff at icann.org<mailto:rds-whois2-staff at icann.org>.

Please find below the list of open action items:


  *   Subgroup to try testing recommendation on WHOIS policies that are being examined by this review (e.g., PP, IDN) to see if metrics/monitoring/reporting and enforcement have been defined for those
  *   Susan to formulate recommendation to include compliance taking a risk-based approach that is not just reactive - addressing systemic complaints and taking a risk-based approach
  *   Susan to examine CCT recommendation on DAAR to build this subgroup’s recommendation
  *   Susan to research 2013 RAA negotiation materials to determine any reasons for allowing grandfathering.
  *   Question 1: Susan to formulate a follow-up question for Compliance (possibly also GDD) regarding counting of null fields and the subset of null fields that occur for grandfathered domains.
  *   Carlton to draft finding/recommendation on use of DAAR to improve accuracy of WHOIS.

As always, let us know if you have any questions or concerns.

Kind regards,

Jean-Baptiste
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rec4-compliance/attachments/20180530/0a0fd2e6/attachment-0001.html>