Showing posts with label GNSO Council. Show all posts
Showing posts with label GNSO Council. Show all posts

2019-03-03

News Review | GNSO Council EPDP Vote March 4, Phase 2 Next

graphic "News Review" ©2016 DomainMondo.com
Domain Mondo's weekly internet domain news review (NR 2019-03-03) with analysis and opinion: Features • 1) GNSO Council EPDP Vote March 4, Phase 2 Next,  2) ICANN64 March 9-14, and more, 3) The .COM Monopoly & ICANNand more, 4) ICYMI: Antitrust, Privacy, Internet Freedom, 5) Most Read.

UPDATES:
March 8, 2019, Reminder: Next EPDP Team meeting at ICANN64, Kobe, Japan, Saturday, 9 Mar 2019, 11:00-18:30 JST, (Friday 9:00 pm EST in US); agenda here, more info further below. Links for Adobe Connect and audio here. Slides here.

March 7, 2019: GNSO Council EPDP Vote Aftermath
  • WHOIS Reform, at Last--internetgovernance.org, by Milton Mueller (NCSG EPDP member): "Discussion of this issue has been distorted for years by ICANN’s propensity to cater to special interest groups (mainly trademark interests but also law enforcement agencies) who conflate their interest in getting access to Whois data with the actual purpose for collecting it. The temporary specification‘s discussion of Whois purpose was especially awful (See section 4, page 5). It is amazing how much progress was made having started from that baseline. The need to comply with GDPR, however, gave privacy advocates and the contracted parties a hammer with which to pound away illegitimate constructions of Whois purposes."
  • GNSO Council Meeting March 4, 2019, transcript (pdf) p. 16, Marie Pattullo, GNSO Councilor (BC), after voting "no" on the March 4th motions: "The EPDP’s work is incomplete. This is just Phase 1, and the report is a step backwards for BC members’ interests compared to the temp spec especially as the legitimate purposes for collecting and processing data in the report are insufficiently precise and don't include consumer protection, cyber clients, DNS abuse and IP protections."

March 4, 2019: GNSO Council approves the motions re: EPDP Final Report (Phase 1). The vote approving was unanimous in the Contracted Parties House (CPH) and split in the Non-Contracted Parties House (NCPH) with "No" votes from the Business Constituency (BC) and Intellectual Property Constituency (IPC). Planning for EPDP Phase 2 work was then discussed, excerpts from the presentation:
See also the "mind map" (pdf) prepared by ICANN staff.

1) GNSO Council Votes on EPDP Final Report March 4, EPDP Phase 2 Next
GNSO Council meeting March 4, 2019, 21:00 UTC (4:00 pm EST in U.S.). Agenda embed below.  Audio cast via browser or app. Transcripts and recordings on GNSO Calendar.
Agenda Item 3: COUNCIL VOTE - Adoption of the Final Report (pdf) on Expedited PDP on the Temporary Specification for gTLD Registration Data (45 minutes)
Agenda Item 4: COUNCIL DISCUSSION - Expedited PDP on the Temporary Specification for gTLD Registration Data - Phase 2 Work (45 minutes)
GNSO Council March 4 agenda (pdf) embed below:

Links: GNSO mail list, meeting documents and motions
EPDP Final Report voting threshold: Supermajority, ICANN Bylaws, Section 11.3(i)(xix): A "GNSO Supermajority" shall mean: (A) two-thirds (2/3) of the Council members of each House, or (B) three-fourths (3/4) of the Council members of one House and a majority of the Council members of the other House.
Next EPDP Team meeting: Saturday, 9 Mar 2019, 11:00-18:30 JST, (9:00 pm Friday EST in US) at ICANN64 in Kobe, Japan--agenda--"for Phase 2 planning, and a discussion on how to manage the coincident Implementation and Phase 2 efforts" according to an email from the EPDP leadership team.  Links for audio and Adobe Connect on the "EPDP Team meeting" link above. EPDP Linksmail list and wiki; EPDP Final Report (pdf); EPDP Charter (pdf); Bird & Bird legal memos; EPDP legal mail list, ICANN's controllership legal memo (pdf).

Rafik Dammak, EPDP Acting Chair
"The GNSO Council and the EPDP team leadership are currently working to develop a plan for addressing Phase 2 and we need to know if there will be changes to the composition of the group."--email from Rafik Dammak, March 1, 2019.
"... When I initially committed to join the group, my intention was to participate in the entirety of the ePDP but the Phase 1 commitment was extremely taxing so I’d like to get a little bit of an understanding of how the leadership group thinks the timing in Phase 2 will compare."--Matt Serlin
"Both Hadia and I plan to continue. That of course presumes we can come up with a REASONABLE work plan that will not kill us."--Alan Greenberg
"... I think many of us are in the situation which Matt describes.  Please, what is the timeline you anticipate?  Will there be face to face meetings, and if so is there a budget for travel?  Will we be keeping our independent counsel?  These are questions whose answers will  influence my decision."--Stephanie Perrin
Related--email from GNSO Chair Keith Drazek to GNSO Councilor (and EPDP member) Ayden Férdeline re: Draft - 2019 GNSO Council Strategic Planning Session Report:
"Hi Ayden, Thanks for your work on this. I have asked Steve to incorporate some of your stylistic edits and some additional language, but I don’t think we can include the commentary on the participation of other SO/AC members in the EPDP and suggestions that other groups are sending discredited and disruptive members to engage with the GNSO.  That’s not something we should include in our formal report on the SPS. Thanks, Keith" (emphasis added)
Search for New EPDP Chair: email Feb 28, 2019, from GNSO Chair Keith Drazek: "Following two Council leadership calls this week, we have finalized the attached Expression of Interest (EOI) [embed below] for the EPDP WG Phase 2 Chair. This will be posted tomorrow and the deadline for responses will be March 22. Our goal is to confirm the new Chair during our April 18 Council meeting. We wanted to be sure to get this posted as soon as possible and certainly in advance of Kobe. The substance of the EOI is the same as the version we used for Phase One. In the interim transition period, while we find a permanent Chair, Rafik [Dammak] will be Acting Chair." [link and emphasis added]

EOI for EPDP WG Phase 2 Chair (reformatted from the original for ease of reading):

EPDP Related: ICANN and GDPR – nowhere near compliance | edri.org 27 Feb 2019: "... while the [EPDP] Initial Report proposes a strong reliance on “legitimate purpose of the controller” as a legal basis for most of the data processing practices, it at no point shows that it has balanced those purposes with the interests of the data subjects. This lack of proportionality was an explicit concern of the WP29 opinion in 2003, and the Initial Report falls far short of the balancing tests as described in WP 29 Opinion 05/2014. Furthermore, the Initial Report doesn’t acknowledge the principle of data minimisation ..."
Editor's notebe sure to read the full thread--Ayden Férdeline (ferdeline.com) is a GNSO Councilor and EPDP member. He is a tech policy fellow with the Mozilla Foundation in Berlin, Germany.

See also
  • Ann Cairns, executive vice chairman of Mastercard, discussing the internet of things, digital identities, and data privacy regulation at the Mobile World Congress 2019, says Europe's approach to data protection will be adopted worldwide--CNBC International | YouTube.com.
  • Revealed: Facebook’s global lobbying against data privacy laws--Leaked Facebook memo describes company's lobbying efforts in 2012 and 2013 against a proposed European data directive which later became GDPR--theguardian.com.

2) Other ICANN News
graphic "ICANN | Internet Corporation for Assigned Names and Numbers"
 ICANN64 | Kobe
a. ICANN64 9-14 March 2019, Kobe, Japan: ICANN64 Schedule.
Date and time in Kobe, Japan:
Meeting resources:

b.  ICYMI this past week on Domain Mondo:
  • ICANN, New gTLDs, Trademarks, RPMs, & Website Content (video) with Rebecca Tushnet, Harvard Law School; Brian Winterfeldt, Winterfeldt IP Group; Mary Wong, ICANN; Becky Burr, ICANN Board & Neustar; Sarah Deutsch, ICANN Board; Kathy Kleiman, Center for Information Technology, Princeton University; Jeff Neuman, Com Laude/Valideus; Mitch Stoltz, EFF; Brian King, MarkMonitor; at a conference at the American University Washington College of Law, Washington, D.C., Feb. 25, 2019.

c. ICANN org publishes Charter on Government Engagement Approach--icann.org. See
draft charter (pdf).

d. ICANN CTO David Conrad to oversee IANA Services and Public Technical Identifiers (PTI)--icann.org.

e. 22 Feb 2019 Letter from Verisign (Patrick Kane) to ICANN (Cyrus Namazi) (pdf) embed below  re: Request for Thick WHOIS Consensus Policy Extension:

f. Cooperative Engagement Process (CEP) and Independent Review Process (IRP) Status Update 25 Feb 2019 (pdf) excerpts:
IRP proceeding: Afilias Domains No. 3 Limited re: new gTLD .WEB. IRP commenced on 26 November 2018; two panelists have been appointed; awaiting appointment of remaining panelist. No hearings are currently scheduled.
CEP proceedings:

g. ICANN & ITU--ICANN Submits Application to International Telecommunications Union (ITU) for ITU-D Sector membership.
Editor's note: Questions about this at @sgdickinson and CCWG-InternetGovernance.

h. ICANN org recommends gTLD registries and registrars to implement the February-2019 version of the gTLD RDAP profile in their RDAP service. Editor's note: the recommended RDAP profile is already out-of-date per EPDP Phase 1 Final Report. ICANN's gTLD registry operators and registrars are required to implement a RDAP service by 26 August 2019.

i. Public Note (pdf) concerning the case of the gTLD “.AMAZON”
 Brazilian Internet Steering Committee
To: ICANN Board of Directors and GAC re: ICANN Board Resolutions 2019.01.16.02 – 2019.01.16.04
"The Brazilian Internet Steering Committee – CGI.br, exercising the mandate conferred upon it by Decree no. 4.829/2003 ... Endorses the request made by the Brazilian government in its letter to the ICANN Board of Directors, dated February 21, 2019, 'to postpone a final decision on the .AMAZON application to ICANN 65, with a view to allow the eight Amazon countries and Amazon Inc. to find a mutually acceptable solution.'"

3) Names, Domains & Trademarks
graphic "Names, Domains & Trademarks" ©2017 DomainMondo.com
a. The .COM Monopoly & ICANN--breakingviews.com: "... ICANN could reject the price hikes. Then again, Verisign may offer to increase the nonprofit’s cut in exchange for agreeing to the increases. A public consultation should help keep both groups honest, but the risk remains that a sweetheart deal gets even sweeter."

b.  Tucows $TCX Q4 2018 Q&A Transcript (pdf), excerpt: "With respect to domain portfolio sales, our portfolio of domains that we hold for resale in the aftermarket is something that we consider tactical, not strategic, as an asset. The bulk portfolio sale in Q4 2018 was generated from our non-surname portfolio of names held."

c. Once You’ve Filed a UDRP, There May Be No Going Back--Lexology.com: "1. Do not file frivolous UDRP complaints ..."

4) ICYMI Internet Domain News 
graphic "ICYMI Internet Domain News" ©2017 DomainMondo.com
Antitrust Enforcement Needs to Evolve for the 21st Century--eff.org.

EFF Supporting California’s Privacy For All Bill, Which Puts People, Not Tech Companies, in Control of Personal Data--eff.org.

Authoritarian assault on Internet Freedom is on the move in Russia and India--editorial in the washingtonpost.com..

India presses on with internet regulations--Chinese-style censorship feared after government consults with tech giants--asia.nikkei.com.

2019-02-03

News Review | ICANN EPDP Dysfunction & Burnout, Report Delayed

graphic "News Review" ©2016 DomainMondo.com
Domain Mondo's weekly internet domain news review (NR 2019-02-03 with analysis and opinion: Features •  1) ICANN EPDP Dysfunction & Burnout, Report Delayed, 2) EPDP Meetings, 3) ICANNBelgium's DPA, 4) ACTO, ICANN & .AMAZON, 5) Dot COM Dominates Aftermarket, 6) ICYMI: Internet Freedom, Data Protection, Internet Shutdowns, Google Public Policy Fellowships, 7) Most Read.

UPDATE FEB 5: EPDP Schedule changes a) Final Report 'drop dead date' now Feb 25 (revised timeline embed below). b) EPDP Plenary Meetings this week changed to Tuesday Feb 5, Wednesday Feb 6, Thursday Feb 7, starting at 14:00 UTC (9am EST). Observers: Adobe Connect. More info at 2) below.

4 Feb 2019 Letter (pdf) from ICANN CEO Goran Marby to GNSO Council Chair Keith Drazek:

UPDATES Feb 3-4, 2019: 
EPDP Consensus Call #1 email from EPDP Chair Kurt Pritz with attachment embed below:

EPDP Consensus Call #2 email from EPDP Chair Kurt Pritz with attachment embed below:  

Original Post:
1. EPDP Dysfunction & Burnout, Final Report (Phase I) Delayed:
[GNSO-EPDP-Team mail list] "Extreme workload warning!"
"While I understand that we have a deadline to meet, and we do not wish to push any more work than absolutely necessary to the next phase of our WHOIS policy development, I would like to push back on the amount of activity that we are now expected to join over the next couple of weeks in order to push the EPDP final report over the finish line. Many of us have busy lives beyond ICANN, and cannot drop everything to attend 4 three hour plenary meetings a week, let alone the other small team meetings (and respond to the list). Given that we have achieved really only a modest level of consensus on our policy recommendations to date, I would like to register a very strong warning that we will not accept changes to the text that have not been agreed in full committee with full attendance. This appears to be a golden opportunity for those who are being paid to work full time on lobbying for certain outcomes, to insert or reinsert their favorite language into the text. In the name of maintaining the integrity of the multi-stakeholder process, flawed as it undoubtedly is, let us resist this and accept the fact that we cannot fix in our last couple of weeks what we lingered over for months."--Stephanie Perrin, EPDP member and NCSG Chair, EPDP Mail List, Jan 28, 2019.
"I’d like to echo Stephanie’s concerns ... After two weeks of being AWOL (ePDP Toronto and GNSO Los Angeles), my employer is anxious for me to turn my attention to my real job.  I will not be joining the additional sessions next week, nor do I recall our discussing or agreeing to this ask."--James Bladel, EPDP member (GoDaddy, RrSG), EPDP Mail List, Jan 28, 2019.
Hi James and everyone: I got it. I am at NamesCon and spent the ride to the airport this morning on a EPDP staff call and have been holed up in my room typing up legal issues since I arrived. I haven’t sold (or bought) a domain name yet. The additional sessions are not a requirement; invitations were sent as placeholders as a heads up, but there is no confirmation yet on whether we go ahead with these or whether they are needed. Let’s discuss the go-forward plan on the call tomorrow - although we might not have a Plan B in place by then - we can at least generate a joint understanding of status and final objective. Thanks (Stephanie and James) for this interjection. Best regards, Kurt [Pritz, EPDP Chair (appointed by the GNSO Council)] EPDP Mail List Jan 28, 2019.
EPDP Timeline as of Jan 28, 2019 (pdf) now REVISED as of Feb 4, embed below:

Updated Editor's note: the EPDP's "drop dead date" is Feb 11 25, 2019, for submission of the final report to the GNSO Council.

2) ICANN EPDP Meetings for Week Ending Feb 9, and Weekly Recap
Updated: EPDP Plenary Meetings are now scheduled for Tuesday Feb 5, Wednesday Feb 6, Thursday Feb 7,  Friday Feb 8, at 14:00 UTC (9am EST) (schedule subject to change).

Notes and action items from the Thursday, Feb 7, 2019, EPDP meeting here.

Observers may use Adobe Connect, or audiocast via browser / app. Links: Draft Final Report info, EPDP Initial Report (pdf) and public comments to the Initial Report; PCRT Public Comment Review Tool; GNSO Council EPDP page and updates; links to EPDP meeting transcripts and recordings are on the GNSO calendar. Other EPDP links: wiki; mail list; action items; Temp Spec; EPDP Charter (pdf); Data Elements Workbooks (pdf), packet (pdf) small team agreements, ICANN's legal memo on Controllership (pdf), Bird & Bird legal memos are here.

EPDP recap for week ending Feb 2: Jan 29 EPDP meeting wiki page and Jan 31 EPDP meeting wiki page, notes and action items here; Legal committee Jan 30, and Data Elements group Jan 29 (5 EPDP team members + Pritz) and Jan 31 (4 EPDP team members + Pritz).

The Most Important EPDP development has been the legal advice provided by Ruth Boardman, Bird & Bird, to the select few members of the EPDP "legal committee" but finally made available to the full EPDP working group on Friday, Feb 1, 2019, here and here (note: more legal advice may be forthcoming). So far, the EPDP team has been advised:
  • relevant parties could be subject to liability if a registrant wrongly self-identifies as a legal person (and not a natural person) and the registrant's data is disclosed in reliance on this self-identification;
  • where the RNH [registrant] and the technical contact are not the same person, relying on the RNH to provide notice on the registrar's behalf will not meet GDPR's notice requirements if the RNH fails to provide the notice;
  • it is not clear if the contractual necessity condition [GDPR Article 6(1)(b)] can only apply where there is a contract between data controller and data subject;
  • "What is 'necessary' is interpreted strictly. We do not think that the EPDP could successfully argue that preventing DNS abuses is 'necessary' for the contract with the RNH" [registrant]. 

More info on Jan 29 and 31 EPDP meetings on last week's News Review, but the following from the Jan 29 transcript (pp. 54-57)  gives an indication of what's going on:
Milton Mueller: "As I said, I think we need to clarify with the legal counsel whether ICANN can, as controller, and ICANN needs to decide whether it’s a controller here of course, but assuming it is, then the fact that it doesn’t have the data doesn’t necessarily mean that it can request it if [it] is the controller, so we need legal advice on that and whether that’s actually – needs a distinctive purpose. But, you know, that’s not a third party access issue under any construction, that’s ICANN getting data about its own system and doing research on it, which we support but we don't want it in Purpose 2."
Kurt Pritz: Thanks, Milton. Alan, go ahead – Alan Greenberg. 
Alan Greenberg: "Yes, thank you. I misspoke before when I said it could go into Purpose 2; I’d forgotten that Purpose 2 is third parties right now so it cannot be Purpose 2. ICANN under no conditions is a third party. We can fix it, however, either by adding a new purpose or simply modifying Purpose 2 to say to third parties for legitimate lawful purposes, or to ICANN, and then add a processing activity for it. So we could make Purpose 2 apply to ICANN as well if people – if that’s offensive to people then it probably has to be a new purpose not because we need a purpose for ICANN doing the processing of the data but to ensure that it can be sent to ICANN. So it’s not the processing that’s the purpose, it’s the transmission to ICANN that we have to ensure is enshrined in some purpose. So we can fix 2 by adding ICANN as an Other recipient in addition to third parties. I can't see anywhere else it fits. I wouldn’t want to put it into 5 because 5 is very much a compliance one and this is not a compliance issue. Thank you."
Kurt Pritz: Thanks, Alan. ....
Farzaneh Badii: "Thank you, Kurt. Farzaneh speaking. So I think that we are really getting confused because we keep repeating and digging up issues that – and questions that we have responded to multiple times ..." [Editor's note: and so it goes.]
3) Status of ICANN’s exchanges with Belgium's Data Protection Authority (DPA)
Excerpt from 27 Jan 2019 Letter from ICANN GDD Cyrus Namazi (pdf)  
Video interview with Willem DebeuckelaerePresident of Belgium's DPA, at European Data Protection Days in Berlin in May 2018:

More info at: edpd-conference.com. Editor's note: ICANN has its sole EU office in Brussels, Belgium, and therefore Belgium's Data Protection Authority (DPA).is the "lead supervisory authority" over ICANN, stated Mr. Debeuckelaere in his letter, adding: 
"Finally, I wish to note that the GDPR places responsibility for compliance with the provisions of the GDPR upon the (joint) controller(s). It does not provide for a system of prior consultation, except in the case of article 36. It also does not foresee the possibility of prior approval, except in the cases mentioned by articles 40 (codes of conduct) and 47 (binding corporate rules)." 
See also:
"Use of WHOIS Data .... We also have some concerns about whether the practice of having the DAAR collection system query registration data is compliant with GDPR and other privacy regulations. Such queries would require a disclosure of personal data that has not previously been contemplated and could have significant repercussions for both registry operators and ICANN."--gTLD Registries Stakeholder Group (RySG) comments (link above) (emphasis added).

4) Other ICANN News: ACTO, ICANN & .AMAZON
graphic "ICANN | Internet Corporation for Assigned Names and Numbers"
28 January 2019 Letter (pdf) from Alexandra Moreira Lopez, Secretary General, Amazon Cooperation Treaty Organization (ACTO), to GAC Chair Manal Ismail re: New gTLD Applications for .AMAZON:

5) Names, Domains & Trademarks: Dot COM Dominates Aftermarket
graphic "Names, Domains & Trademarks" ©2017 DomainMondo.com
GoDaddy 2019 aftermarket domain trends and NamesCon keynote | slideshare.net excerpt:

6) ICYMI Internet Domain News: Internet Freedom, Data Protection, Internet Shutdowns and Google Public Policy Fellowships
graphic "ICYMI Internet Domain News" ©2017 DomainMondo.com
Has the internet afforded humans more freedom, or less?--Social-Media Outrage Is Collapsing Our Worlds--The internet once made it easier to slip from one domain to another. Is there a way to preserve that vital freedom?--theatlantic.com.

Google and IAB ad category lists show ‘massive leakage of highly intimate data,’ GDPR complaint claims--techcrunch.com.

Ireland questions Facebook’s plan to merge Messenger, Instagram, and WhatsApp--previous data-sharing proposals have ‘given rise to significant data protection concerns’--theverge.com.

Dr Paul Vixie, Farsight Security, on pushing back against cyber criminals--Tech Radio via Soundcloud.com.

African governments use internet shutdowns to silence opposition more and more--what can people do?--euronews.com. See also Zimbabwe President Mnangagwa Justifies Internet Shut Down, Although “He Deeply Believes In Freedom Of Speech And Expression”--techzim.co.zw.

Venezuela: The Committee to Protect Journalists have called on Venezuelan authorities to stop blocking news outlets and to ensure that access to the internet is available amid the country's political crisis and widespread protests--cpj.org.

Applications are open for the Google North America Public Policy Fellowship--all applications must be received by 12:00 p.m. EST, Friday, February, 15th. More information about Google Public Policy Fellowships, including in Latin America, Europe, Middle East, and Africahere.

7) Most Read this past week on DomainMondo.com: 
graphic "Domain Mondo" ©2017 DomainMondo.com



-- John Poole, Editor  Domain Mondo 

feedback & comments via twitter @DomainMondo


DISCLAIMER

2016-11-30

GNSO Admits Domain Name Transfer Policy Flawed, Blames ICANN Staff

UPDATE December 2, 2016: The letter from James Bladel on behalf of the GNSO Council has now been published on the ICANN correspondence webpage (pdf), embed below:


UPDATE November 30, 2016: Philip Corwin has today advised Domain Mondo that the letter by James Bladel on behalf of the GNSO Council, embedded below, "is still under development and has not yet been sent."  Domain Mondo obtained the letter from ICANN via one of its public daily briefing emails with the text "GNSO Council to ICANN Board Thursday, November 24 2016 05:20 PM" and a direct link to the letter (pdf) with no other reference either on the ICANN website or GNSO website.

*Original posting:
In the world of ICANN, incompetence begets incompetence and compounds itself in perpetuity:
New transfer policy QA | OpenSRS.com: "At OpenSRS, we believe that the ICANN community who came up with this new policy did a disservice to [domain name] registrants. The policy requirements do not add any positive element to the experience of managing a domain name, and there has been no consideration how this policy would align with the number of other ICANN mandated policies which are already in place. Nonetheless, OpenSRS is, like all other ICANN accredited registrars, bound by the terms of the Transfer Policy .." (emphasis added). For more see News Review | What Is ICANN? | New ICANN Domain Name Transfer Policy. 
The new ICANN Domain Name Transfer Policy effective December 1, 2016 has been sharply criticized as indicated in the quote above, and now it has come to light that the Generic Names Supporting Organization (GNSO) which developed this flawed policy (one of many flawed policies that the GNSO is renown for propagating without proper forethought or competence), has now had second thoughts about the way the policy was implemented by ICANN staff, and in a letter (embed further below) states:
"the GNSO Council respectfully requests the ICANN Board of Directors to instruct ICANN staff to (a) remove any privacy/proxy service compliance from the Transfer Policy and to transfer the issue to the PPSAI Implementation Review Team for evaluation and recommendation, and (b) to withhold any compliance enforcement of the Transfer Policy relating to the enabling or disabling of privacy/proxy services pending the outcome of the PPSAI IRT."
Truth is the whole Domain Name Transfer Policy is flawed as OpenSRS noted above. But the GNSO Council, as is typical, takes no responsibility for its incompetent policy-making, and instead blames ICANN staff for misinterpreting the policy in the implementation phase:
"Although the the IRTP Part C policy recommendations are silent on the issue, ICANN staff, based on initial guidance from the IRTP Part C Implementation Review Team, interprets the Transfer Policy to require registrars to implement the CoR when any change is made to the public WHOIS data, even when that change does not result in a change to the underlying customer data. The RrSG has pointed out, however, that this approach is untenable as it guts the intent of the Transfer Policy (as the actual registrant may change without the process being triggered) and creates significant operational complications for routine changes carried out by P/P providers.1 While ICANN staff is sympathetic to these challenges, they are obliged to represent what they see as the direction provided by the IRTP Part C Implementation Review Team (IRTP-C IRT)."
The ICANN community members who developed this flawed policy are listed here and include some current members of the GNSO Council, including Chair James Bladel (GoDaddy) and Philip Corwin (Internet Commerce Association). Who were the members of the IRTP Part C Implementation Review Team (IRTP-C IRT)? Unknown, that information is either hidden or buried on the ICANN and GNSO websites (ICANN likes to hide information and keep things "secret" from public view), though the mailing list includes GNSO Chair James Bladel, author of the GNSO Council letter embedded below:

GNSO Council letter (highlighting added) embed below (pdf):


*posting revised in accordance with Update(s)

feedback & comments via twitter @DomainMondo


DISCLAIMER

2015-11-06

Verisign's Keith Drazek: GNSO, IANA, ICANN, WHOIS, New gTLDs (videos)



Video above: Verisign's Keith Drazek reflects on his forthcoming term on the GNSO Council, his experience within ICANN including his previous experience on the ccNSO Council, as well as WHOIS policy, and the new gTLDs Reviews. (source: ICANN; Published on Oct 30, 2015)

Video below: Keith Drazek discusses his representation of the gTLD Registries on the IANA Stewardship Transition Coordination Group (ICG) during the group’s first meeting in London, 17-18 July 2014. Topics mentioned include Verisign's Role as Root Zone Maintainer as well as Registry operator for .COM and .NET. (source: ICANN; Published on Jul 25, 2014)



Keith Drazek is Vice President of Public Policy and Government Relations at Verisign, Inc., operator of the .COM and .NET domain name registries, Internet Root Zone Maintainer pursuant to an agreement with the US Department of Commerce (NTIA), as well as operator of  two of the world's 13 Internet root servers. Keith has been active in the ICANN community for more than a decade, including his most recent role as Chair of ICANN’s GNSO Registry Stakeholder Group. Prior to joining Verisign in 2010, he worked for ten years at the U.S. Department of State, and ten years in the domain name industry - 2 years at a registrar and 8 years at a registry (Neustar). His experience in the domain name industry includes business development, channel management, government relations, external affairs, and Internet policy development. He studied International Relations at George Washington University in Washington, DC. (primary source: ianacg.org)

See also on Domain MondoVerisign, ICANN, Internet Root Zone, Risk Factors to the Root Domain Oct 26, 2015




DISCLAIMER

Domain Mondo archive