- ALAC - lists.icann.org

Contractual Compliance: Addressing Domain Name System (DNS) Infrastructure Abuse
by Andrei Kolesnikov Nov. 10, 2018

Nov. 10, 2018

piece of contractual compliance addressing DNS infrastructure abuse: https://www.icann.org/news/blog/contractual-compliance-addressing-domain-na… Recent dashboard for September https://features.icann.org/compliance/dashboard/0918/report Bookmark dashboard page https://features.icann.org/compliance/dashboard/report-list if you are interested in overall contractual party responses, including end users. --andrei -- Andrey Kolesnikov RIPN.NET

1 0

What do users want?
by Alan Greenberg Nov. 7, 2018

Nov. 7, 2018

I am taking advantage of my new "freedom" to do some long overdue cleanup. I found a short handwritten document I wrote about 10 years ago (after I had been involved with the ALAC for a year or two) on what Internet users want. Note that a lot of this is far beyond the remit of ICANN, but other parts are not. ================= Users want an experience that is: -Satisfying -Safe -Predictable -Easy to access and fast In a bit more detail, this means: - Pages display properly - No SPAM - No Phishing - Reproducible - Mail gets delivered - Fast enough that speed is not an issue. Another was of looking at is as an embodiment of the Principle of Least Astonishment (https://en.wikipedia.org/wiki/Principle_of_least_astonishment) They have no desire to know anything about Internet Governance. And most have no interest in how the Internet actually works. A classic quote from Arthur C. Clarke is "Any sufficiently advanced technology is indistinguishable from magic." It doesn't matter how or why it works, as long as it works. From my personal experience, I have been involved in the Internet for about 30 years. Due to the travel I have done, or other times it comes up in conversation, I have often been asked what I am doing. If I try to explain, the most common result is that their eyes glaze over, they say "oh, that's interesting" and they try to find a way to change the subject.

12 14

Endorsement request for the ICANN Leadership Programme 2019
by Maureen Hilyard Nov. 6, 2018

Nov. 6, 2018

My dear ALAC colleagues Messages from the LP coordinators are becoming more urgent. Therefore, in order to enable our candidates to register by November 8, I am requesting an ALAC endorsement by email, of the candidates proposed by their RALOs for the ICANN Leadership Programme 2019. If you have any conflicts or disagreement with the proposed names, please let us all know. I have alternates in the wings. *Please respond to this thread by 7 Nov Weds 12:00utc*. 1 - LAC Harold Arcos harold.arcos(a)gmail.com LACRALO Secretary 2 - AP Lianna Galstyan lianna(a)magic.am APRALO Vice Chair 3 - NA Eduardo Diaz eduardodiazrivera(a)gmail.com NARALO Chair 4 - EU Joanna Kulesza joannakulesza(a)gmail.com EURALO ALAC 5 - AF Mohamed El Bashir mbashir(a)mbash.net AFRALO CHAIR Also, apparently, more names can be submitted for the Chairing Skills Programme, so if you know of anyone who may want to upskill their Chairing Skills and would like to attend this programme (and is funded to go to Kobe), please suggest their names too. Sorry for the haste. Still waiting on a suitable date and time for the ALAC meeting from staff. Maureen

13 13

SSAC update
by Andrei Kolesnikov Oct. 31, 2018

Oct. 31, 2018

Dear ALAC, below are SSAC related topics at recent ICANN meeting in Barcelona Board resolutions (Oct.25): - reappointments of SSAC members to three-year terms ( Jaap Akkerhuis, Patrik Fältström, Ondrej Filip, Jim Galvin, Robert Guerra, Julie Hammer, Ram Mohan, Doron Shikmoni, and Suzanne Woolf - Merike Kaeo wil be a member of BTC (board technical committee) and the BRC (board risk committee) - Ram Mohan completes 10 years of service on the ICANN board representing SSAC ICANN 63 updates Publications [SAC103]: SSAC Response to the new gTLD Subsequent Procedures PDP WG Initial Report (3 October 2018) [SAC102]: SSAC Comment on the Updated Plan for Continuing the Root KSK Rollover (20 August 2018) [SAC101]: SSAC Advisory Regarding Access to Domain Name Registration Data (18 June 2018) [SSAC2018-16]: Draft Assessment Report of the Independent Examiner (13 June 2018) [SSAC2018-15]: Review of IDN Implementation Guidelines (11 June 2018) Current work in progress Name Collision Analysis Project SSAC Organizational Review Internet of Things WP Emerging Security Topics (Ongoing) DNSSEC Workshops (Ongoing) Membership Committee (Ongoing) Topics of interest / possible new work Improving SSAC working processes DNS Privacy, DNS over HTTP, DNS over TCP Pros and cons of hyper local root / RFC 7706 DNSSEC DS key management and other registrar/registry control issues Best practices for handling take-down procedures Security issues specific to specialized TLDs Studying abuse in nTLDs Questions to the community What topics would you like SSAC to consider as work items? What would you like SSAC to comment on? -- Andrey Kolesnikov RIPN.NET

5 4

Re: [ALAC] traffic report
by Seun Ojedeji Oct. 29, 2018

Oct. 29, 2018

It seems to be focused on certain region. Regards On 26 Oct 2018 11:22 AM, "Fouad Bajwa" <fouadbajwa(a)gmail.com> wrote: Is this part of a larger study? On Fri, 26 Oct 2018, 1:08 pm Andrei Kolesnikov, <andrei(a)rol.ru> wrote: > https://www.sandvine.com/hubfs/downloads/phenomena/ > 2018-phenomena-report.pdf > > This is very interesting and reflects the consumption (of the end users) > > --andrei > > -- > Andrey Kolesnikov > RIPN.NET > > _______________________________________________ > ALAC mailing list > ALAC(a)atlarge-lists.icann.org > https://atlarge-lists.icann.org/mailman/listinfo/alac > > At-Large Online: http://www.atlarge.icann.org > ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+ > Advisory+Committee+(ALAC) > _______________________________________________ ALAC mailing list ALAC(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: https://community.icann.org/display/atlarge/At-Large+ Advisory+Committee+(ALAC)

2 1

traffic report
by Andrei Kolesnikov Oct. 26, 2018

Oct. 26, 2018

https://www.sandvine.com/hubfs/downloads/phenomena/2018-phenomena-report.pdf This is very interesting and reflects the consumption (of the end users) --andrei -- Andrey Kolesnikov RIPN.NET

3 2

towards board resolution on reserve fund
by Andrei Kolesnikov Oct. 24, 2018

Oct. 24, 2018

FYI from CCWG -- On October 24, 2018 at 1:20:10 PM, Erika Mann (erika(a)erikamann.com) wrote: > *Dear CCWG AP colleagues - * > > *Cherine Chalaby asked for a meeting this morning, October 24, to inform > me as CCWG AP Co-Chair about a resolution the Board will pass tomorrow > morning, October 25, concerning the replenishment of the Reserve Fund. > Maarten Botterman attended the meeting and Chris Disspain was present for a > short period at the beginning of the meeting.* > > *To replenish the Reserve Fund, the Board resolution will request a > contribution from ICANN ORG on an annual basis (8 years), total $32 > Million, and an immediate contribution from Auction Proceed, total $36 > Million. These two amounts seen together would replenish the Reserve Fund > (in 8 years) to the agreed height. * > > *Cherine was interested in informing us ahead of the decision and I > mentioned, that we were expecting such a move and, as far as this is > concerned, we're not surprised to see the Board passing this resolution > tomorrow and that we do appreciate his approach in informing us ahead of > passing the resolution. * > > > Reminder:* The* '*Document for Public comment – Replenishment Strategy > for the ICANN Reserve Fund' (open date, March 6th, 2018/closed April 25th, > 2018) mentioned the following about the replenishment of the fund in > relation to the topics mentioned above: * > * > https://www.icann.org/en/system/files/files/proposed-reserve-fund-replenish… > <https://www.icann.org/en/system/files/files/proposed-reserve-fund-replenish…>* > > *§ Contribution from ICANN Org: Future adopted budgets could be made to > provide a contribution to the Reserve Fund on an annual basis. This would > require ICANN Org to plan each fiscal year for expenses to be lower than > funding by an amount explicitly designated for the purpose of replenishing > the Reserve Fund. Given ICANN’s funding constraints, contributions from > ICANN org to the Reserve Fund replenishment result from a reduced > allocation of ICANN’s resources to its on-going activities, in order to > produce a surplus that is allocated to the Reserve Fund. Such allocation is > and needs to continue being the subject of community engagement and input. * > > *§ Auction Proceeds: ICANN currently has US$ 104 million collected from > auctions that were held as the mechanism of last resort to resolve string > contention in the new gTLD program (including investment returns). This > amount excludes US$ 132 million relating to the auction of the .WEB string > net of auction fees * > > *Kind regards, * > *Erika * > > *Barcelona, October 24, 2018* >

1 0

RoP Revisions
by Alan Greenberg Oct. 23, 2018

Oct. 23, 2018

Attached are: - Details on the two votes to be taken prior to approval of the RoP. - Redline and clean versions of the RoP - Redline and clean versions of the E-mail Guide. Alan

1 0

Fwd: CCWG Accountability Work Stream 2
by Alan Greenberg Oct. 22, 2018

Oct. 22, 2018

FYI >To: Thomas Rickert <epdp(a)gdpr.ninja>, Jordan Carter ><jordan(a)internetnz.net.nz>, Tijani BEN JEMAA <tijani.benjemaa(a)topnet.tn> >From: Alan Greenberg <alan.greenberg(a)mcgill.ca> >Subject: CCWG Accountability Work Stream 2 >Cc: Bernard Turcotte <turcotte.bernard(a)gmail.com>, Karen Mulberry ><karen.mulberry(a)icann.org>, At-Large Staff <staff(a)atlarge.icann.org> > >On 09 October 2018 the ALAC unanimously ratified the Final Report of >the Cross Community Working Group (CCWG)-Accountability Work Stream >2 with the following caveat to be addressed during the Board >deliberations on the WS2 Recommendation and the ensuing implementation: > >"The recommendations formulated in the various sections of this >report all have merit in advancing ICANN's transparency and >accountability. However, taken together, they may amount to a >daunting burden on ICANN Org and its volunteer community. For this >reason, the ALAC recommends that, as the recommendations are >implemented, ICANN should take an approach minimizing the impact and >work associated with following these recommendations." > >Alan Greenberg >Chair, ALAC

1 0

Proposal about ALAC Rules of procedure
by Sergio Salinas Porto Oct. 21, 2018

Oct. 21, 2018

The At-Large Advisory Committee (ALAC) is the primary organizational home for Internet end users within the Internet Corporation for Assigned Names and Numbers (ICANN). The role of the ALAC is to consider and provide advice on the activities of ICANN, insofar as they relate to the interests of Internet end users. *Sergio Salinas Porto**Presidente Internauta Argentina**Asociación Argentina de Usuarios de Internet <http://www.internauta.org.ar/>/FeTIA <http://www.fetia.org.ar/>/CTA <http://ctamdq.org.ar/>**FLUI- Federación Latinoamericana de Usuarios de Internet <http://www.fuilatin.org/>**facebook: salinasporto <http://www.facebook.com/salinasporto> **twitter: sergiosalinas <http://twitter.com/sergiosalinas>**Youtube: salinasporto <http://www.youtube.com/salinasporto>**Skype:internautaargentina**Mobi:+54 9 223 5 215819**"Ojalá podamos ser desobedientes, cada vez que recibimos órdenes que humillan nuestra * * conciencia o violan nuestro sentido común" Eduardo Galeano*

5 5