Showing posts with label Milton Mueller. Show all posts
Showing posts with label Milton Mueller. Show all posts

2018-09-23

News Review: ICANN & GDPR, EPDP F2F Meeting in LA, Sep 24-26

graphic "News Review" ©2016 DomainMondo.com
Domain Mondo's weekly internet domain news review (NR 2018-09-23 with analysis and opinion: Features •  1) ICANN & GDPR, EPDP F2F Meeting in LA, Sep 24-262) ICANN New gTLDs CCT-Review Report, and more, 3)a.Canada's TM law, b. GoDaddy & new gTLDs, c. ccTLD .eu, and more, 4) ICYMI: Internet Freedom (EU,UK), Net Neutrality (US), 5) Most Read.

UPDATE Sep 24, 2018: ICANN said today it is considering (beyond its role as a WHOIS data 'controller' and its role in contractual enforcement), to "be acknowledged under the law as the coordinating authority of the WHOIS system ... shifting the liability for providing access to non-public registration data to ICANN and establishing a globally scalable unified solution for access to non-public WHOIS data," adding, "it will be important to engage with the European Data Protection Board to test with them whether the approaches and interpretations of the law may ultimately provide a feasible solution meeting the needs of stakeholders seeking access to non-public WHOIS." (emphasis added)

1) ICANN & GDPR, EPDP F2F Meeting in LA, Sep 24-26
ICANN EPDP Working Group Face-to-Face Meeting in LA Sep 24-26, 2018. Google Map of ICANN offices and hotel and logistics info (pdf). Non-members of the EPDP Team can follow EPDP meetings via Adobe Connect or audio cast via browser or application.

LA F2F Meeting wiki pageagenda with local (PDT) and UTC times, slides, documents, recordings. Meeting facilitators: David Plumb, Gina Bartlett and Toby Berkman of CBI.org.

Notes:
UPDATE Sep 24, 2018, slides:

F2F agenda (subject to change), times shown are local PDT:

Editor's note: links to EPDP meetings' transcripts are posted (usually within 24 hours) on the GNSO calendar. See also EPDP Team wiki, mail list, Temp Spec, EPDP Charter (pdf), GNSO's EPDP page, & weekly updates to GNSO Council.

EPDP Highlights for the week ending Sep 22 (emphasis and links added):

GNSO Council mail list:
Sep 18, 2018: "The BC/IPC [ICANN Business Constituency and Intellectual Property Constituency] recently sent a letter [pdf] to ICANN org about the accreditation and access model. This letter seems problematic at this stage of the game. We discussed this issue ad nauseam during the EPDP Charter development and the Council has tasked the EPDP with addressing the Annex. To ask ICANN org to circumvent the EPDP undermines the policy development process and seems disingenuous to the Council's approval of the Charter. In addition, the EDPB's July 5 letter [pdf] states responsibility for designing an access model lies with ICANN and the registries/ registrars, not just ICANN as indicated in the BC/IPC letter. Will our BC and/or IPC councilors please shed some light on this?"--Darcy Southwell (RrSG).  
Sep 19, 2018: "Darcy has asked an excellent question. As an outgoing councilor, I guess I can afford to be blunt here. What is going on? I quit the RDS PDP after two years of soul destroying work because it was blindingly clear we were going nowhere, and the Board was already working on a temp spec to override anything we were doing. IS the same thing going to happen with the EPDP? I am deeply concerned about the integrity of the multi-stakeholder process. Sorry for being direct, but time is precious."--Stephanie Perrin (NCSG). 
Editor's note: the lone response from either BC or IPC councilors as of Sep 21, 2018, is here
EPDP Sep 18 meeting chat transcript (pdf):  Milton Mueller (NCSG): "... confusing access with purpose again .... and again .... and again" .... Farzaneh Badii (NCSG): "... gating questions have to be answered. We are not answering them. Every meeting has turned into an access meeting ..." Stephanie Perrin (NCSG): "Another useful document on the DPIA process, endorsed by the Schleswig Holstein DPA (co-author) is available here ... targeted to GDPR compliance ... (file under
educational efforts, or what we ought to be doing at this point) ... Useful also in that it crosslinks to relevant standards." 

EPDP Sep 18 meeting transcript (pdf, 49 pp.):
Milton Mueller (NCSG): "Yes, Kurt [Pritz], these comments are primarily directed to you as the chair of this committee. We've just spent half of our meeting on an extraneous agenda item. I don't know how we got – how this got prioritized. I think it’s very evident from the discussion that it should not have been prioritized. And I’m – I really think that we need to have better management of our agenda. We have to focus on the things that are essential to the temp spec and that is what data is collected, what are the purposes and what data is going to be redacted in public Whois. It’s simply unacceptable for us to keep getting distracted from these fundamental issues onto things that are secondary and that may not even be controversial once we've decided what data elements are actually going to be collected and what are going to be disclosed. So can we get off Appendix C? Can we just drop it? It’s not getting us anywhere. It’s a waste of time and I think I still don't understand how we even got on this." p.19 
Kurt Pritz (EPDP Chair): "Okay, Milton ..." 

[Editor's note: Kurt Pritz, the inept EPDP Chair appointed by the GNSO Council, is a major contributor to the EPDP working group's dysfunction. Maybe the LA F2F meeting facilitators (CBI) can ameliorate some of the effects of Pritz's dysfunction.]

Stephanie Perrin (NCSG): "... In many ways Alan [Woods, RySG] has just made my point. We are going in circles, folks. I hope some people have now taken the training but unfortunately the training is, while it’s very good I think, for length of time that takes to do it ... it does not help us do a privacy impact assessment on the framework that we're dealing with. And the problem, as I see it, is that the bylaws to which Alan keeps referring ... require a privacy impact assessment. Everybody’s assuming that the bylaws as ICANN has set them up, are some kind of gospel. They don't comply with data protection law. We have been told by the DPAs point blank over years, that it's not up to ICANN to set itself up as a law enforcement data dump. I’m paraphrasing there ... the purposes of third parties are not the purposes of ICANN and ICANN cannot write itself bylaws that provide that ... If we’re going to be going in circles you might as well go back and do a privacy impact assessment of the entire registration data service because this isn't working ..." p.24

EPDP Sep 20 meeting chat transcript (pdf): Amr Elsadr (NCSG): "I'm in favor of attempting to answering the Charter questions, as opposed to redlining the temp spec." ...   Kristina Rosette (RySG):+1 Amr (answering charter questions and not redlining TS) ... Milton Mueller (NCSG): "Please, let's not redline Temp Spec" .... "our ultimate objective is to replace the temp spec with a real policy, have we forgotten that?" ... farzaneh badii (NCSG): "why are we thinking about section by section. lets think about charter questions, the data elements, answer questions and then see which sections of temp specc has to be revised." Milton Mueller (NCSG): "exactly, Farzy." Amr Elsadr (NCSG):@Farzi: +1 ....  Milton Mueller (NCSG): "An access method is outside the gating question" ... Ashley Heineman (GAC): "I agree Milton" ... Thomas Rickert (ISPCP): "Kurt - I think Milton made an excellent point when he said that you can only have a discussion about redaction once you know what you collect in the first place" ...  Ashley Heineman (GAC): "... I think the charter questions provide a good framework for our discussions" ... Milton Mueller (NCSG): "I am going to leave the call ... this is a waste of time" ... Thomas Rickert (ISPCP): "... Today, I am quite frustrated because we do not seem to be making any progress at all."

EPDP Sep 20 meeting transcript (pdf, 45pp.):
Milton Mueller (NCSG): "Yes I’m just – there’s some kind of strange process going on here but I
thought I had made the point [p. 35] that we cannot discuss access to nonpublic Whois data until we know what the data is and what is public and what is nonpublic. And here we are having a discussion of access to these data elements that we don't even know and we don't know what's public and nonpublic. Why is this happening? Did I miss something in the discussion? It seemed like you agreed with me, Kurt, that there was a logical order to the discussion of these elements. Are we discussing what we’re going to discuss when we’re in Los Angeles? Or are we having this discussion in a real sense? I’m just completely lost here." p.40

Kurt Pritz (EPDP Chair): "Thanks, Milton. I think there are several topics in Appendix A, other than
redaction, that require discussion where redaction isn't necessarily on the critical path. And so what …" p.40

Milton Mueller (NCSG): "… redaction is not on the critical path when you're talking about access to nonpublic Whois data and redaction tells you what's public and what's not public? How can you say that?" p.40

Kurt Pritz (EPDP Chair): "I wasn’t referring to access, I was referring to some of these other things that are in Appendix A ..." p.40

Mark Svancarek (BC): "... I really reject the idea that we must define all data elements to be redacted before we can talk about the concept of reasonable access ..." p.41 

James Bladel [RrSG]: "... I keep feeling like we just continue to get wrapped around the access issue and ... it’s unfortunately just not something we can take on in the scope of the time that we have. And I think that that’s one of the reasons why the GNSO Council designed the charter the way they did. So I think we just need to kind of note it, flag it, and move on. Thanks." p. 42

Editor's noteThe continual diversions to access and 3rd party purposes and interests, particularly by Facebook's Margie Milam  and Microsoft's Mark Svancarek (BC EPDP members), together with the inept EPDP Chair's dysfunction, is fast sinking any chance of this EPDP working group addressing 3rd-party "access" to redacted WHOIS registration data, due to a lack of time, if nothing else. But again, that may be the strategy of the IPC (Intellectual Property Constituency) and BC (Business Constituency) in order to put more "pressure" on ICANN management and the ICANN Board to adopt and implement a "unified accreditation and access model" more to IPC and BC's liking, without input from this EPDP working group. See BC/IPC Sep 7 letter (pdf) to ICANN CEO Goran Marby.

The EPDP working group wasted almost the entire month of August compiling a "triage report" for the GNSO Council that could instead have been simplified to a survey completed in the first week of August, followed immediately with the EPDP Team addressing the Charter's gating questions. Instead the inept EPDP "leadership team" assisted by ICANN staff, forced the EPDP working group to engage in temp spec redlining exercises:
“I came into this thinking that the fastest way home was to sort of redline the temporary specification"--Kurt Pritz, EPDP meeting Sep 20, 2018, transcript, supra, p.10.
In other words, Kurt Pritz thought he knew a better way than following the GNSO Council's EPDP Charter, which is why the EPDP team is behind schedule and "off track" as it arrives in LA this week for its face-to-face meeting. I have observed every meeting of this EPDP working group, and thus far, from all indications, it appears Pritz lacks the intellect, aptitude, and/or skills, to be an effective EPDP Chair. Until the Chair's dysfunction is addressed, this EPDP isn't likely to get much done.

More info and updates on last week's meetings in last week's News Review.
Photo of ICANN CEO Goran Marby, with words below:" ICANN's  GDPR Train Wreck"  ©2018 DomainMondo.com
Definition of "train wreck" -- a chaotic or disastrous situation that holds a peculiar fascination for observers.
Note also:
ICYMI ICANN Lost Again in the Appellate Court in Germany:
ICANN v. EPAG Domainservices, GmbH (a Tucows affiliate)

2) Other ICANN News
graphic "ICANN | Internet Corporation for Assigned Names and Numbers"
a. ICANN's Whitewash CCT-Review Report: Competition, Consumer Trust, and Consumer Choice Review Team Final Report (pdf), re: new gTLDs
"the review team concluded that the New gTLD Program should be regarded only as a “good start,” and that a number of policy issues should be addressed before any further expansion of gTLDs."--Report, supra, p.6 (emphasis added)
Editor's note: a good start? Hardly! New gTLDs are (for the most part) a BIG #FAIL, but ICANN's CCT-Review Team was unable or unwilling to honestly assess and acknowledge ICANN's Mistakes, Fiascos, and Horrible Implementation which resulted in this disastrous new gTLDs program. Recommendation: Relegate this CCT-Review Report to File 13But did anyone really expect anything different from this Review Team handpicked by former ICANN CEO Fadi Chehadé?

b.  Root KSK Rollover: ICANN Board approved (with dissent) to change or "roll" the key for the DNS root on 11 October 2018 (first time the key has ever been changed)--ICANN.org. See also What To Expect During the Root KSK Rollover (updated 17 Sep 2018)(pdf).

c. ICANN Webinars on Proposed Updates to Draft Operating Standards for Specific Reviews 04 Oct 2018: 16:00 UTC, and 05 Oct 2018: 00:00 UTC. More info here.

d. GNSO Project List (pdf) 19 Sep 2018.

e. New gTLD .Merck: Merck KGaA’s written Submission (pdf) in support of Oral Presentation to BAMC on 4 Sep 2018.

f. is for FAIL: ICANN Reviews | glassdoor.com--what ICANN employees are saying about ICANN: "Sinking ship ... Senior management don't seem to have a clue ... Highly political and run by SJW's with ego problems ..."

3) Names, Domains & Trademarks
graphic "Names, Domains & Trademarks" ©2017 DomainMondo.com
a. Trademarks: changes to Canada's trademark laws will remove the use requirement, possibly opening up the trademarks register to a flood of speculation. The changes, set to come into effect next year, will also institute three international trademark treaties: the Nice Agreement, Singapore Treaty and Madrid Protocol--CanadianLawyerMag.com. Editor's note: forget about domain speculation, trademark speculation may be the speculators' new game of choice and Canadian trademark lawyers' equivalent of ICANN's new gTLDs program.

b. Domains: Top Registrar in World: Godaddy has only 5.8% of top 16.6 MILLION New GTLD Registrations! | ricksblog.comEditor's note: GoDaddy $GDDY, the world's largest domain name registrar, manages 21% of all domain names in the world--expandedramblings.com--but new gTLDs' domain names comprise only 1% of all domain names managed by GoDaddy. Why? New gTLDs (for the most part) are a BIG #FAIL.

c. ccTLD .eu: Euro bureaucrats tie up .eu in red tape to stop Brexit Brits snatching back their web domains | register.co.uk.

d. Prepared especially for ICANN's Next Round? A Top Level Domain (TLDRegistry In A Box, don't you want your very own brand new gTLD?

4) ICYMI Internet Domain News 
graphic "ICYMI Internet Domain News" ©2017 DomainMondo.com
Internet Freedom
EU: "EU copyright rules would limit online freedom"--Mitchell Baker, Executive Chairwoman of Mozilla, Mountain View, CA, US--ft.com. But see also "French applaud EU copyright reform vote"--euractiv.com.

Internet Freedom
UK: "Politicians are threatening our right to have private discussions - we must not let them ban secret social media groups"--telegraph.co.uk.

Net Neutrality
US: FCC Chairman Ajit Pai Slams California Net Neutrality Bill--"The internet should be run by engineers, entrepreneurs, and technologists, not lawyers, bureaucrats, and politicians," Pai said. Pai is also citing a recent federal court of appeals ruling as evidence states lack the legal authority to reimpose net neutrality.

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



-- John Poole, Editor  Domain Mondo 

feedback & comments via twitter @DomainMondo


DISCLAIMER

2018-09-02

News Review: 1) ICANN EPDP Struggles; 2) New gTLD .WEB Updates

graphic "News Review" ©2016 DomainMondo.com
Domain Mondo's weekly internet domain news review (NR 2018-09-02) with analysis and opinion: Features •  1) EPDP Struggles, 2) Other ICANN news: a. New gTLD .WEB Updates: Ruby Glen (Donuts) & Afilias, b. DNA & ICANN, and more, 3)a. IDNs--Who Needs Them? b. Afilias Inc., c. Centralnic, and more, 4) ICYMI: a. Facebook & Genocide, b. Egypt, c. Cybercrime & Blockchain, 5) Most Read.

1) ICANN EPDP Struggles
ICANN EPDP Team Meetings this week: Tuesday Sep 4, and Thursday Sep 613:00 UTC, 9am EDT. Non-members of the EPDP Team can follow the EPDP meetings via Adobe Connect: https://participate.icann.org/gnso-epdp-observers, or audio cast via browser or application (e.g.,iTunes).

Editor's note: each EPDP meeting's links to key documents, transcripts, MP3 audio and Adobe Connect recording, will be posted in UPDATES below (as made available by ICANN--note that links to EPDP meetings' transcripts are usually posted on the GNSO calendar within 24 hours). See also EPDP Team wiki, mail list, Temp Spec, and EPDP Charter (pdf).

Sep 6, 2018, EPDP Team Meeting Notes UPDATED:
  • Notes and action items from EPDP Team Meeting 9/6 here.

* * * * * * *
Sep 4, 2018, EPDP Team Meeting Notes UPDATED:
Chat transcript p.5 (pdf)
Editor's note: Little of substance was accomplished at the EPDP team meeting on September 4, 2018. The EPDP team appears to be drowning in dysfunction and lack of direction. EPDP team members have been asking, repeatedly since August 7, for GDPR training which ICANN has yet to provide even though the GDPR was published in May 2016, and training was provided by other California corporations for their respective stakeholders long before the GDPR became enforceable on May 25, 2018.
  • 9/4 Meeting transcript
  • Some "additional considerations and materials" for Tuesday's meeting here.
  • Adobe recording of 9/4 meeting, MP3, chat transcript (pdf).
  • Registries Stakeholder Group (RySG) rationale for removal and onward referral of the contents of Appendix C of the Temp Spec (highlighting added) here (pdf) not approved.
  • Notes and action items here.
  • Slides provided (pdf) were changed for the meeting--copy of 9/4 meeting's slides have not been published by ICANN
* * * * * *
UPDATE: Weekly Reports on the EPDP to GNSO Council hereObjection filed 3 Sep 2018 by Ayden Férdeline (NCSG): "I am reluctant to make this comment, but I think it is necessary. I do not see any substantial changes between the format of the previous report and this one. I don’t think this communicated anything useful then, and this update does not leave me with an accurate snapshot of the two two-hour long EPDP meetings that I sat through last week. We need something better. If there is a need for a report that will give the community confidence that multistakeholderism is working, fine, let’s use this one. But the Council, if it is to deliver proper oversight over this EPDP, needs a separate report that does not sugarcoat what is really happening within meetings and glosses over the challenges actually being faced. If this same reporting format is used again, I will raise this same objection again." (emphasis added)
* * * * * * *
Highlights from last week's ICANN EPDP Team meetings:

Kurt Pritz (the inept EPDP Team Chair appointed by the GNSO Council): "Thanks very much, Terri. And welcome, everyone. I’m holed up in a hotel room in Melbourne Australia at 11 o’clock at night and there’s a show of funny home videos playing in the background so if – I don't know how it got on the TV but if I laugh now and then that’s why." --Aug 30 transcript p. 2 of 48 (pdf). [Editor's note: turn off the TV during meetings Kurt!]

Kurt Pritz: "And I – gosh, I had one other item I wanted to talk about during this part of the meeting but I forgot what it was." Aug 30 transcript p. 3, supra. [Editor's note: Turn off the TV Kurt!]

Terri Agnew (ICANN staff)"And, Kurt, this is Terri. If you're speaking it looks like your line is still muted." Kurt Pritz: "That’s because it was still muted. So Alex, you sort of alluded to a proposed wording, do you have that? And, you know, it’s late here so I don't know if my coffee’s kicked in." Aug 30 transcript p. 6, supra.

Milton Mueller (NCSG): "Yes, so again I think we are very much going down a rabbit hole here that is completely unnecessary. The problem that we have with 4.4.2 as well as 8 and 9 is that it’s really an access issue; it’s not an ICANN purpose issue. So the problem we have with these so-called legitimate interest lists is that they are trying to incorporate those external third party legitimate interests into a definition of the purpose of ICANN's collection and display of the data which is just a mistake. If we could separate those two things very clearly we could come to an agreement. If you think you're going to accommodate access concerns by defining third party interests as part of ICANN's purpose then we, you know, our stakeholder group is never going to accept that because it is, you know, making the confusion that the data protection authorities told us not to do very explicitly, very clearly and repeatedly that the third party interests, even if they're legitimate and even if they would eventually produce access to the data, should not be confused with ICANN's purpose. And this is what we are persistently doing and that’s our main concern with the many items in Section 4 of the temp spec. Aug 30 transcript p. 7, supra.

Ashley Heineman (GAC, U.S.): "... So I’m going to cautiously agree with Milton, at least in part. I think what may have led us astray here is kind of commingling purpose and interest and so I don't have precise wording at this point but I agree with at least exploring the idea of at least separating out these concepts and exploring perhaps, you know, having them addressed elsewhere, perhaps Appendix A, Section 4. But I’m starting to understand the arguments here and I think fundamentally it’s because we’re confusing two concepts that are quite different. So I’ll stop there ...." Aug 30 transcript p.10, supra.

Alan Woods (RySG): "... I’m not sure that trying to polish up individual sections in this way is getting us – is getting us very far again, reading all the comments from people such as Thomas in the chat. Completely agree, it’s cutting off an awful lot of other aspects and I think it [Temp Spec] just needs a rewrite as opposed to a polish. Aug 30 transcript p.15, supra.

Marc Anderson (RySG): "... I think, you know, the drafting of this [Temp Spec], you know, there was an intent to, you know, the intent here was to, you know, to sort of, you know, bolt on some GDPR compliance to the existing system. You know, and so just sort of taking what's there and redlining it isn't going to – isn't going to be a successful endeavor.Aug 30 transcript p. 17, supra.

Terri Agnew: "Kurt, this is Terri. You may still be muted."
Kurt Pritz: "I know and I was – first it was really funny and second of all, it was really insightful."  Aug 30 transcript p. 17, supra.

Marc Anderson (RySG): "... I don't think that the, you know, the way the conversation is flowing right now where we’re sort of jumping around different sections of the temporary specification  and just sort of debating them ad hoc is moving us towards done. You know, and given how short a timeframe we have, you know, I think we need to focus that up a little more ..." Aug 30 transcript p. 27, supra.

Terri Agnew: "And, Kurt, this is Terri. Please check your mute. Actually, Kurt, it looks like perhaps your audio’s dropped from the Adobe Connect site?"
Kurt Pritz: "Yes, can you hear me now?" Aug 30 transcript p. 27, supra.

Alan Greenberg (ALAC)"I believe 4.4.8 [Temp Spec] tries to conflate too many things and the wording therefore becomes completely untenable." Aug 30 transcript p. 27, supra.

Chat 30 Aug 2018Alan Woods (RYSG): "full rewrite of all the sections is necessary was my point- not polish what is there." 

Editor's note: a "full rewrite of all the sections is necessary" -- that, in a nutshell, is also what is so wrong with the EPDP's project plan and work plan (which impliedly presume the Temp Spec just needs to be fine-tuned or "polished").

For more info and updates on last week's meetings, go to last week's News ReviewNote also:
  • Fear mongers forced to eat shorts over spam swamping claims - GDPR and no Whois hasn't caused catastrophe | theregister.co.uk.

2) Other ICANN News
graphic "ICANN | Internet Corporation for Assigned Names and Numbers"
a. New gTLD .WEB UPDATES
(i) U.S. Court of Appeals for the Ninth Circuit, Court Room 1, Richard H. Chambers Court of Appeals Building, 125 South Grand Avenue, Pasadena CA 91105:
ORAL ARGUMENT Oct 9, 2018: Case 16-56890: Ruby Glen, LLC v. ICANN (Ruby Glen, LLC [Donuts affiliate] appeals the district court's Fed. R. Civ. P. 12(b)(6) dismissal of its diversity action against Internet Corporation for Assigned Names and Numbers, seeking to temporarily enjoin ICANN from conducting an auction [for new gTLD .WEB]. The appellate briefs are here.

(ii) New gTLD .WEB applicant Afilias--Request 18-8: Afilias Domains No. 3 Limited | Board Accountability Mechanisms Committee (BAMCRecommendation on Reconsideration Request 18-8, 28 Aug 2018 reconsideration-18-8-afilias-bamc-recommendation-28aug18-en.pdf [211 KB] excerpt:
See also 2018 Reconsideration Requests – Status Update – 29 August 2018 reconsideration-requests-status-2018-29aug18-en.pdf [pdf, 55.9 KB].

b.  DNA (Domain Name Association) & ICANN:
Editor's note: not to mention that ICANN, by virtue of the above, is violating its own Articles of Incorporation and the provisions of IRC 501(c)(3). Remedies might include filing a complaint with the IRS, or the Attorney General of the State of California for initiation of, or authorization to file, a legal action pursuant to federal (U.S.) and state (California) law for involuntary dissolution of the Internet Corporation for Assigned Names and NumbersICANN: incompetent, corrupt, unfit.
UPDATE: go here, here, and here for more on the sordid history of ICANN & the DNA.

c. The New ICANN Fellowship Program | ICANN.org: "... Future fellowship cohorts will consist of 45 participants per ICANN meeting, a 25% reduction from years past. Of the 45 slots, seven (7) will go to Fellowship mentors. We will uphold and enforce the rule which states an individual can only serve as a fellow a total of three instances ..."  See also ICANN Pays Senior VP Sally Costerton Secret Contract $$$ | DomainMondo.com.

d. Nothing of import: Minutes (pdf) of ICANN Board Accountability Mechanisms Committee (BAMC) Meeting 02 Aug 2018; and Agenda of BAMC meeting 04 Sep 2018.

e. Internationalized Domain Names | ICANN.orgInternationalized Domain Names (IDNs) enable people around the world to use domain names in local languages and scripts. Editor's note: see the next item below.

3) Names, Domains & Trademarks
graphic "Names, Domains & Trademarks" ©2017 DomainMondo.com
a. IDNs a/k/a Internationalized Domain Names: Who Needs Them? (Other than cyber criminals for homograph attacks) --
Nobody Needs Arabic Domain Names | muscatdaily.com  26 Aug 2018: "The Telecommunications Regulatory Authority (TRA) has been offering Arabic language domain names since 2012, but luckily, it does not seem that anyone in Oman has made the mistake of actually using one ... Almost ten years ago, ICANN, the global authority for regulating domain names, announced that it would allow the registration of top-level internationalised domain names written in local languages and scripts other than the Latin alphabet ... nobody seems to be using them. Contrary to what was argued by the proponents of [IDNs] ... We have had web content written in the Arabic language before Arabic domain names came out, and we continue to do so without using these domain names ...."
Editor's notewe (the global internet community) did not need 1200+ new gTLDs either, but that didn't stop ICANN.

b.  Afilias, which says it is the world’s second largest top-level domain registry operator, announced Aug 30, 2018, that it has
"formally established a new corporate parent entity, Afilias, Inc. of Delaware, USA.  Afilias plc of Ireland is now a wholly owned subsidiary of Afilias, Inc.  Afilias further announced the relocation of its global corporate headquarters to Horsham, PA [a suburb of Philadelphia], the current offices of its operating subsidiary Afilias USA, Inc." 
Why move from Ireland (part of the EU) to the U.S.? 
"Afilias’ two largest customers, Public Interest Registry (the .ORG registry operator) and GoDaddy (the world’s largest domain name registrar), have US headquarters. These trends, coupled with recent favorable US tax changes, make Afilias’ US presence important in maximizing its future growth."  
Afilias is a privately-held legal entity, formed in September, 2000, by a consortium of nineteen ICANN-accredited domain name registrars, including Tucows Inc. Afilias recently replaced Neustar as the registry services provider for Australia's ccTLD .au, and is currently in litigation against Neustar over India's ccTLD .in. Afilias, (see 2)a. above) was the second-highest bidder for new gTLD .WEB and has been contesting the delegation of .WEB to the winning bidder, Nu Dot Co, financed by Verisign which has an agreement with Nu Dot Co for subsequent assignment of .WEB.

c.  Centralnic Group (LON: CNIC) shares reached a new 52-week low during mid-day trading on Thursday, August 23, 2018, hitting a low of GBX 49 ($0.64), and then hit that low again on Aug 30:
LON: CNIC
Centralnic (domain: centralnic.comreportedly is the 11th largest domain name registrar globally by generic top-level domain volume and among the top five new gTLD backend registry service providers supporting over 100 top-level domains (TLDs). Oh, the penny stock delusions of a new gTLDs true believer!
LON: CNIC
d. Who’s Behind the Screencam Extortion Scam? | KrebsOnSecurity.com"The truth is we may never find out who’s responsible ..."

e. WIPO Center informal Q&A concerning the GDPR as it relates to the UDRP: In preparing a UDRP complaint post-GDPR, how can a trademark owner conduct a WhoIs search/access the domain name registrant’s details?--wipo.int.

f. Why are abandoned domain names dangerous? They are low-hanging fruit for attackers, who can use them to access sensitive email or customer data--csoonline.com.

4) ICYMI Internet Domain News 
graphic "ICYMI Internet Domain News" ©2017 DomainMondo.com
a. Facebook, Myanmar and Genocide: "... the most important global case study regarding the power and potential toxicity of social media; you have to look at Facebook’s enabling role in the Rohingya genocide ..."--datatrekresearch.com. See also U.N. calls for Myanmar generals to be tried for genocide, blames Facebook for incitement--reuters.com.

b. Internet Censorship: Egypt's Sisi signs new law tightening government control online--Law imposes hefty fines, up to five years in prison for those who administer websites deemed to harm national interests.--aljazeera.com.

c. Cybercrime & Blockchain: 4 ways in which blockchain technology will address the problem of cybercrime | techbullion.com: "DNS is effective but it is partially centralized. Blockchain can prevent denial of service attacks since it would decentralize the DNS."

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

-- John Poole, Editor, Domain Mondo 

feedback & comments via twitter @DomainMondo


DISCLAIMER

2016-04-10

News Review: ICANN, China, IANA: ex-CEO Fadi Chehadé's Sad Legacy

DomainMondoShiningLight ©2013domainmondo.com All Rights Reserved
Domain Mondo's review of the past week and look ahead [pdf of this post is here]:

What's happening in the IANA Transition?

• This past week, U.S. Senators Cruz, Lankford and Lee, exchanged letters with ICANN Board Chairman Steve Crocker, fundamentally about conflicts of interest within ICANN, and principally the influence of foreign governments, specifically, the ICANN CEO (now ex-CEO) Fadi Chehade agreeing in December, 2015, to co-chair the High-level Advisory Committee to China's World Internet Conference (WIC) held the last 2 years in Wuzhen, China. Crocker, in his letter of response, wrote a rambling defense and justification of Chehade's conduct without answering any of the Senators' specific questions, essentially admitting that neither he, nor any other member of the ICANN Board of Directors, saw any potential conflict of interest nor anything inappropriate in Chehade attending (while still President and CEO of ICANN), the WIC on ICANN's 'dime' and announcing, via his ICANN President Twitter account, his acceptance of  the offer to Co-Chair the High-level Advisory Committee, thereby, in the eyes of many, lending his support and endorsement, as ICANN CEO, to the objectives of WIC and China's internet governance agenda:
"To whom is the Advisory Committee which Chehade and the others are joining giving advice? It is the World Internet Conference Organizing Committee Secretariat, a CCP [Communist Party of China] organ .... Our opinion is that the advisory committee members are making a mistake. Like so many deluded businessmen and politicians before them, they think that being friendly and cooperative with the [Chinese] regime will either gain themselves privileged access to the market, or will somehow change the basic principles and policy direction of the Chinese state. It may do the first (though it is unlikely) but it certainly will not do the latter. The WIC is intended to justify and advocate a more repressive Internet ... Rather than contesting ideas on a terrain in which internet freedom, bottom up initiative and openness have an advantage, they have foolishly chosen to play the conference diplomacy game on a terrain chosen by the Chinese Communist Party..." --Georgia Tech Professor, Dr. Milton Mueller, December 29, 2015, The Wuzhen Compradors (note: Dr. Mueller has been active in ICANN since its formation in 1998, and is co-founder of its Noncommercial Users constituency).
Read more, including the latest letter from the U.S. Senators and Crocker's reply letter, at ICANN Sends Letter To US Senators But Does NOT Answer Questions | DomainMondo.com, which also references a transcript of the NCPH Intersessional Meeting  at ICANN, February 5, 2016, wherein "ICANN community" stakeholders recognized the real or potential conflict of interest issue in ICANN CEO Chehade's activities in China, and assumed that one or more ICANN Board members had already referred the matter to ICANN's Office of General Counsel as required by ICANN Policy on conflicts of interest.

Those intersessional transcripts [Feb. 4-5, 2016] provide even more insight into the sad legacy that ex-CEO Fadi Chehadé left behind at ICANN--excerpts below--emphasis and links added:

Stakeholder to Fadi Chehade: "... You were talking about what we need to do better. And obviously we need to get more people engaged. It’s certainly been my observation in the three years I’ve been at ICANN that there’s a massive power imbalance. And while I agree we need to get more people engaged, it doesn’t necessarily empower them, particularly in civil society ..."

Stakeholder: "... The concerns raised by many in the [ICANN] community indicate that the existing GNSO [ICANN's main policy-making body, the Generic Names Supporting Organization] structure and operating plans do not yet meet stakeholder expectations. Recent statements made by various stakeholders suggest that current ICANN structure [GNSO] needs to be reviewed, and if need be, improved, amended, replaced or supplemented with new mechanisms ... our house [NCPH] suffers more from the structural issues within the GNSO than the other house [the contracted party house, i.e., the domain name registrars and gTLD registry operators] ... We’ve heard claims before that the GNSO is broken and various issues around structure have been raised by various groups ..."

Stakeholder to Chehade: "... for the multi-stakeholder model to succeed, ICANN has to demonstrate some of the best attributes that you would normally find in public service in a governmental setting --transparency, full accountability and conflict of interest [policy] ..."

Fadi Chehade: "There is no question that ICANN can improve its accountability, its transparency and its policy. There is no question."

Fadi Chehade"I’m going to spend time with him [ICANN's new CEO] mostly on sharing with him the mistakes I did, the difficulties I caused myself because I had not understood well. I did not have the privilege of having time with my predecessor right? I had a coffee with him. And it was not a happy coffee. So I - nobody told me anything."  [Note: this is an odd statement since Chehade was reportedly brought into ICANN by his lifelong friend and former co-worker, then ICANN COO Akram Atallah, who, in turn, was promoted by Chehade to the second-highest paying position within ICANN (it's called cronyism).]

Fadi Chehade: "I’ve learned in these four years that unless he [new ICANN CEO] is listening and deriving his priorities from you, he’s going to have a miserable time. It’s that simple ... See the biggest difficulty for an incoming presidency to ICANN is two parts. The first is his title. The title is a problem because [when] you come in, you think you’re a CEO. You’re not a CEO. This is not a typical CEO job. And so you get into your head all kinds of things about being a CEO that just don’t apply here. And so the title is problematic. And I’ll tell him [new ICANN CEO] this after he signs his offer."  [Note: insightful comment by Chehade, he recognizes the originating source of his problems at ICANN is somewhere inside his "head."]

Fadi Chehade"I think everyone of you could list my mistakes. I can do it for you to save you some time, you know. I made mistakes. It’s okay."  [Note: it would have been helpful and cathartic for the "ICANN community" to have seen Chehade's list of his own mistakes--frankly, I would not be surprised if many of his well-known mistakes were absent from his list--denial is a well-known attribute of dysfunctional leadership (pdf). Also note that remedies to denial in management include having a "powerful board" (Ravi Mistry), but unfortunately for ICANN, its Board is mostly passive, and therefore, mostly useless:
"The second thing [first is the 'CEO' title--see above] is the Board, the name of the Board [ICANN Board of Directors]. This is not a Board in the classic sense of a Board of Directors right? If he [new ICANN CEO] doesn’t understand the nature of this group you elect called the Board which is not a typical Board of Directors and the nature of this community and what it is and the nature then of his much diminished role as CEO President ... if he can’t figure this formula out he’s going to have a rough four years ahead or five years ahead."--Fadi Chehade, NCPH Intersessional. Feb. 5, 2016.]
Is this what happens when an organization is led by a dysfunctional or unprepared CEO, enabled by an equally dysfunctional or unprepared Board of Directors: passing secret Board resolutions, spending hundreds of thousands of dollars and countless hours of ICANN officers and staff time, organizing events and establishing organizations outside the mission and scope of ICANN, instead of focusing on the core issues of improving ICANN functionality, transparency, and accountability?

Is ICANN really ready for prime time?

• Speaking of the IANA transition, and China, Domain Mondo recommends reading, carefully, the recent post from Dr. Mueller's Internet Governance Project: Alternate DNS roots and the abominable snowman of sovereignty, as well as the articles it references: Internet Fragmentation: An Overview (pdf) by William J. Drake, Vint Cerf, and Wolfgang Kleinwächter; and Dr. Paul Vixie's response:
"... I have personally reached out to operators inside the BRICS countries (Brazil, Russia, India, China, South Africa) to ensure that they know about the Yeti-DNS project, and can participate if they so choose. This reflects my view that if some country decides some day that ICANN cannot be trusted, and they want to create their own Internet DNS system, I want them to have the necessary expertise and competence and awareness of tradeoffs, in-country, to pursue their own sovereign course. If asked, I would advise such countries that any such independence would be nasty, brutish, and short. But I will not pretend that they have to listen to me ... Anybody who wants, for whatever reason of their own, to craft their own root zone as a derivative of IANA's root zone, ought to get all the help they need. Our industry's holy scriptures ought to be written in English not Latin, and ought to be read by the laity, ought to be understood and argued about by the world wide Internet community. Open and transparent network science is no threat to Internet governance ..." --Dr. Paul Vixie, Let Me Make Yeti-DNS Perfectly Clear (emphasis added). 
Indeed, is ICANN even trustworthy today? Many, with good reason, say nay.

See also on Domain Mondo: How ICANN and ICANN CEO Fadi Chehadé Evade Accountability and Blocking New gTLDs, ICANN's 'Shadiest' Top-level Domains, 'Wholesale'.

•Meanwhile, work continues on the implentation phase of the ICANN accountability & IANA transition proposal submitted by ICANN's Board of Directors to the NTIA in March:

CCWG and Bylaws Timeline

NTIA is currently assessing ICANN's IANA Transition proposal, a process which it will not finish until sometime in June according to one tentative IANA Transition timeline.

• Finally, note: ICANN and Verisign Announce Start of 90-day Root Zone Management System "Parallel Testing" Period | ICANN.org. See also Parallel Operations Root Zone Management System Comparison | Verisign.com.

In the world of tech, Yahoo (stock: $YHOO | domain: yahoo.com) extended the deadline for receiving bids for its assets to April 18, 2016. Interestingly, Yahoo's Q1 2016 earnings release is scheduled for the following day. Meanwhile, Jack Dorsey continues to transform Twitter, replacing 2 directors. Twitter's Q1 2016 earnings release is scheduled for April 26.

Finally, if you have not seen the video of Elon Musk's SpaceX successfully landing its Falcon 9 rocket on the droneship whimsically named "Of Course I Still Love You" in the Atlantic Ocean, by all means, watch it: SpaceX Successfully Lands Falcon 9 Rocket on DroneShip at Sea (video) | DomainMondo.com.

Have a great week!

-- John Poole, Editor, Domain Mondo





DISCLAIMER

Domain Mondo archive