[lac-discuss-en] Fwd: [ALAC-Announce] ICANN News Alert -- Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now Available

Wed Apr 19 21:14:29 UTC 2017

FYI
--
Kind regards,
Bartlett D. Morgan

---------- Forwarded message ----------
From: ICANN At-Large Staff <staff at atlarge.icann.org>
Date: 19 April 2017 at 04:08
Subject: [ALAC-Announce] ICANN News Alert -- Updated ICANN Procedure for
Handling WHOIS Conflicts with Privacy Laws Now Available
To: ALAC Announce <alac-announce at atlarge-lists.icann.org>

[image: ICANN][icann.org]
<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.icann.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=hsrBi_CR3TLGOV-Rd042QZLZiVb5_XjdhTOlbGRbmlE&e=>
News
Alert

https://www.icann.org/news/announcement-2017-04-18-en[icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2017-2D04-2D18-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=xZ6w4HR7Kmj4hdbDPa0pl3Sr2fZyyXiuqgGRXs1g6i0&e=>
------------------------------
Updated ICANN Procedure for Handling WHOIS Conflicts with Privacy Laws Now
Available

18 April 2017

LOS ANGELES – 18 April 2017 – The Internet Corporation for Assigned Names
and Numbers (ICANN) today published the updated Procedure for Handling
WHOIS Conflicts with Privacy Laws (WHOIS Procedure), which is effective
immediately.

*Read the Revised WHOIS Procedure[icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_resources_pages_whois-2Dprivacy-2Dconflicts-2Dprocedure-2D2008-2D01-2D17-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=jrmS1HdvfMEhBbPTuLW34ztf9fVA4toDQ8ncnzDHsys&e=>.*

The WHOIS Procedure has been revised to incorporate an alternative trigger
to invoke the WHOIS Procedure. The current trigger in the WHOIS Procedure
allows a registry operator or ICANN-accredited registrar to invoke the
procedure if the contracted party is in receipt of a notification of an
action that its compliance with WHOIS obligations is prevented by local
laws. With the additional trigger, a registry operator or ICANN-accredited
registrar may now also invoke the WHOIS Procedure by providing ICANN with a
written statement from the applicable government agency responsible for
enforcing its data privacy laws and indicating that a WHOIS obligation in
an ICANN contract conflicts with such applicable national law.

The modification to the WHOIS Procedure is based on input from the
community and the work of an Implementation Advisory Group (IAG), which was
tasked with reviewing possible changes to the WHOIS Procedure and providing
the Generic Names Supporting Organization (GNSO) with recommendations to
facilitate resolution of issues where WHOIS requirements conflict with
applicable laws.

In May 2016, the IAG submitted its final report[gnso.icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_drafts_iag-2Dreview-2Dwhois-2Dconflicts-2Dprocedure-2D23may16-2Den.pdf&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=lfKB9ouJmAmJ3VAcZqKNXqTgVvHUJsVsA7YwpXsELJw&e=>
[PDF, 155 KB] and recommendation to the GNSO Council. In February 2017, the
GNSO Council passed a resolution[gnso.icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_council_resolutions-23201703&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=3cwNSUYaNBIjVfmk880P2VyhMSlA8fs7JPLY2GaU4bM&e=>
adopting IAG's recommendation and confirmed that the modification to the
WHOIS Procedure does not change the intent of the original GNSO policy
recommendations.
Background

In November 2005, the GNSO concluded a policy development process
(PDP)[gnso.icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issues_whois-2Dprivacy_council-2Drpt-2D18jan06.htm&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=MOYbTnOkoDT69LHCxZ03POnSMj_imLej3y2jxLb9Fhc&e=>
establishing a Procedure to allow gTLD registry operators and registrars to
demonstrate when they are prevented by local laws from fully complying with
the provisions of their respective ICANN contracts regarding personal data
in WHOIS. The ICANN Board of Directors adopted the recommendations in May
2006 and directed staff to develop such a procedure. A contracted party
that credibly demonstrates that it is legally prevented from complying with
its WHOIS obligations can invoke the procedure, which became effective in
January 2008. To date, the procedure has never been invoked. ICANN launched
a review[icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_whois-2Dconflicts-2Dprocedure-2D2014-2D05-2D22-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=DS2cpoUbNG6nrt3BuRFtqD1G06BIiLssAkV2FCnxi8A&e=>
of the procedure in May 2014 and has concluded this review with this update
to the WHOIS Procedure.

Following a Call for Volunteers[icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_news_announcement-2D2014-2D10-2D14-2Den&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=n17aP_T9JJWAjzYJrhXRwaguwo5lb1igdZXtG579A4U&e=>
addressed to all interested parties, an IAG was formed to review the
implementation of the policy recommendations and began its work in January
2015. The IAG devoted most of its time to discussing whether additional
triggers to invoke the Procedure should be incorporated and, if so, how to
ensure that they remain consistent with the existing policy.
About ICANN

*ICANN's mission is to help ensure a stable, secure and unified global
Internet. To reach another person on the Internet, you have to type an
address into your computer - a name or a number. That address has to be
unique so computers know where to find each other. ICANN helps coordinate
and support these unique identifiers across the world. ICANN was formed in
1998 as a not-for-profit public-benefit corporation and a community with
participants from all over the world. ICANN and its community help keep the
Internet secure, stable and interoperable. It also promotes competition and
develops policy for the top-level of the Internet's naming system and
facilitates the use of other unique Internet identifiers. For more
information please visit: www.icann.org[icann.org]
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_&d=DwMFaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=mrDeztziKLa7gZqGADzxcnHA3QXmXYsnChWYBR4NElI&m=ac9sYVKag9-y1JgA_w4gifabB9NUxmfec1GfuSZlZig&s=oLJzki4MqdSchXd-Kr9hrJaCrpe-aq5QgqKF3udB6Yk&e=>.*

_______________________________________________
ALAC-Announce mailing list
ALAC-Announce at atlarge-lists.icann.org
https://atlarge-lists.icann.org/mailman/listinfo/alac-announce

At-Large Official Site: http://www.atlarge.icann.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/lac-discuss-en/attachments/20170419/66d6bc60/attachment.html>