February 2020 - At-Large - lists.icann.org

Google Developers : Humans can't read URLs. How can we fix it? - HTTP 203
by Dev Anand Teelucksingh Feb. 12, 2020

Feb. 12, 2020

"In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security. What are browsers doing today to overcome that? And, is there a better way" Watch the 20 min episode : https://youtu.be/0-wB1VY3Nrc Dev Anand

5 5

Re: [At-Large] [technology taskforce] Google Developers : Humans can't read URLs. How can we fix it? - HTTP 203
by Hadia Abdelsalam Mokhtar EL miniawi Feb. 12, 2020

Feb. 12, 2020

He is suggesting a way through which non-technical users can identify easily the eTLD+1 and thus maybe not tricked by bad actors. Hadia From: At-Large [mailto:at-large-bounces@atlarge-lists.icann.org] On Behalf Of Carlton Samuels Sent: Tuesday, February 11, 2020 8:07 PM To: Dev Anand Teelucksingh Cc: Technology Taskforce WG; At-Large Worldwide Subject: Re: [At-Large] [technology taskforce] Google Developers : Humans can't read URLs. How can we fix it? - HTTP 203 I viewed the video and my takeaway was that browsers can be configured for a role in building confidence in domain names. Very good discussion guys. CAS On Mon, 10 Feb 2020, 10:08 pm Dev Anand Teelucksingh, <devtee(a)gmail.com<mailto:devtee@gmail.com>> wrote: Dr. Alejandro Pisanty Baruch <apisan(a)unam.mx<mailto:apisan@unam.mx>> wrote: "is this just one more iteration of "domain names will cease to be relevant soon" or is it a move or trend that will definitely undermine their importance and therefore also change the markets?" I think no, this is not an iteration about domain names becoming irrelevant. The discussion focused on how to ensure browser users can identify what domain they are visiting so IMO, it strengthens the use of domain names by having users trust the domain they are visiting. The challenge as I see it is with the prevalence of many new TLDs, the risk of phishing and malware attacks are higher where bad persons try to trick persons to either: - go to bad persons' website(s) at domains pretending to be another organisation/service in order to get user login credentials to such organisations/services or - open links to malware files and become infected. So typically, bad persons would use typos that look similiar to the legitimate domain or add a few characters before or after the 2nd level domain So for example.com<http://example.com>, there could be exannple.com<http://exannple.com> , examp1e.com<http://examp1e.com>, eexamples.com<http://eexamples.com> and examples.com<http://examples.com> . With more TLDs and wider use of ccTLDs, bad persons could also do things like examples.xyz<http://examples.xyz>, examp1e.tv<http://examp1e.tv> and so on. With longer URLs, one can mask the legitimate domain as a third or fourth level subdomain of a bad persons' domain. Very long URLs like this are more difficult to parse and read on a mobile phone. Content Management Systems for websites over the years unfortunately generate long URLs that do work to direct persons to websites but are obscure for persons to parse. So an example of a bad URL : https://community.icann.org.can.work/display/atlarge/2020-01-27+At-Large+Te… Persons glancing at this URL would see icann.org<http://icann.org> and may think everything is fine and go ahead and click on the URL when its not. Nearly all browser vendors are using the Public Suffix List at https://publicsuffix.org/ which started as a Mozilla Initiative. From the Public Suffix List website, a "public suffix" is one under which Internet users can (or historically could) directly register names. Tracking this is important to ensure that a website can't set cookies that other websites can read or modify under the same domain. What the episode showed was that Mozilla Firefox (at least on the desktop) highlights the part of the domain that is the public suffix by making it slightly bolder than the rest of the URL. It is however to me, very, very subtle and I wish that Mozilla (and other browsers) make the public suffix part more bold or even a slightly bigger font size to alert users as to the true domain being viewed. Some mobile browsers are showing only the domain and not the rest of the URL and allow for the full URL can be viewed and edited when you tap on the URL bar which also helps. Kind Regards, Dev Anand Teelucksingh On Sun, Feb 9, 2020 at 3:23 PM Dr. Alejandro Pisanty Baruch <apisan(a)unam.mx<mailto:apisan@unam.mx>> wrote: Dev, thanks a lot for sending this. While at first it may seem off-topic, it cuts deeply into very relevant questions for us: is this just one more iteration of "domain names will cease to be relevant soon" or is it a move or trend that will definitely undermine their importance and therefore also change the markets? If it proceeds, what balances of power will appear that we don't face now? One example: will the companies that operate search or that provide browsers (or both!) earn new powers? This is already being discussed elsewhere. What are the views that are relevant for ICANN Internet users At Large, and other stakeholders? Yours, Alejandro Pisanty - - - - - - - - - - - - - - - - - - - - - - - - - - - Dr. Alejandro Pisanty Facultad de Química UNAM Av. Universidad 3000, 04510 Mexico DF Mexico +52-1-5541444475 FROM ABROAD +525541444475 DESDE MÉXICO SMS +525541444475 Blog: http://pisanty.blogspot.com LinkedIn: http://www.linkedin.com/in/pisanty Unete al grupo UNAM en LinkedIn, http://www.linkedin.com/e/gis/22285/4A106C0C8614 Twitter: http://twitter.com/apisanty ---->> Unete a ISOC Mexico, http://www.isoc.org . . . . . . . . . . . . . . . . ________________________________ Desde: At-Large [at-large-bounces(a)atlarge-lists.icann.org<mailto:at-large-bounces@atlarge-lists.icann.org>] en nombre de Dev Anand Teelucksingh [devtee(a)gmail.com<mailto:devtee@gmail.com>] Enviado el: viernes, 07 de febrero de 2020 11:21 Hasta: At-Large Worldwide Asunto: [At-Large] Google Developers : Humans can't read URLs. How can we fix it? - HTTP 203 "In this episode, Jake makes the case that URLs are impossible for humans to interpret, especially when it comes to security. What are browsers doing today to overcome that? And, is there a better way" Watch the 20 min episode : https://youtu.be/0-wB1VY3Nrc Dev Anand _______________________________________________ ttf mailing list ttf(a)atlarge-lists.icann.org<mailto:ttf@atlarge-lists.icann.org> https://mm.icann.org/mailman/listinfo/ttf _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0

WEBCAST TODAY: The Controversial Sale of the .ORG Registry: The Conversation We Should Be Having
by Joly MacFie Feb. 11, 2020

Feb. 11, 2020

About to start. AUWCL advertises this as a 'Fireside Chat', so things may get warm! ISOC Live posted: "Today, Tuesday February 11 2020 at noon EST (17:00 UTC) the American University Washington College of Law, the Program on Information Justice and Intellectual Property, the Internet Governance Lab and the WCL Intellectual Property Brief present 'The Cont" [image: livestream] <https://youtu.be/NEDeQt-gJNQ>Today, *Tuesday February 11 2020* at * noon EST* (17:00 UTC) the *American University Washington College of Law <https://www.wcl.american.edu/>*, the* Program on Information Justice and Intellectual Property* <https://www.wcl.american.edu/impact/initiatives-programs/pijip/>, the *Internet Governance Lab <https://internetgovernancelab.org/>* and the *WCL Intellectual Property Brief <https://digitalcommons.wcl.american.edu/ipbrief/>* present '*The Controversial Sale of the .ORG Registry: The Conversation We Should Be Having <https://www.wcl.american.edu/impact/initiatives-programs/pijip/events/the-c…>*' in Washington DC. Speakers: *Andrew Sullivan*, President & CEO, Internet Society; *Mitch Stoltz*, Senior Staff Attorney, Electronic Frontier Foundation; *Benjamin Leff, *Professor of Law, Charitable and Non-Profit Organizations, Washington College of Law; *Marc Rotenberg*, President, Electronic Privacy Information Center; and *Kathryn Kleiman*, IP & Tech Clinic, Washington College of Law (facilitator). The event will be webcast live via *YouTube <https://youtu.be/NEDeQt-gJNQ>*. *VIEW ON YOUTUBE: https://youtu.be/NEDeQt-gJNQ <https://youtu.be/NEDeQt-gJNQ>* *TWITTER: #dotORG <https://isoc.live/11778/#dotORG>* *Permalink* https://isoc.live/11778/ - -- -------------------------------------- Joly MacFie +2185659365 -------------------------------------- -

1 0

IANA Naming Function Review Team (IFRT) #5 meeting
by Kaili Kan Feb. 10, 2020

Feb. 10, 2020

Dear At-Large and All, The IFRT had its 5th meeting via teleconference on 4 February 2020, 17:00 UTC. The meeting discussed the following: -- Approved the Scope of Work; -- No comments received on Work Plan, will continue discussion on 18 Feb.; -- Began reviewing the IANA naming function contract. Attached documents: -- Scope of Work (approved 4 Feb., attached); -- Work Plan (draft at https://docs.google.com/spreadsheets/d/13g-rrryNkXIwLdVC0fiKpEwQFBTwa07Z/ed… ). As the representative of At-Large and the AP region at IFRT, if you have any questions, concerns, suggestions or opinions, please do not hesitate to contact me, so that I may present them at IFRT. Thank you all. Yours, Kaili Kan

1 0

Weekly posting summary for at-large@atlarge-lists.icann.org
by narten＠us.ibm.com Feb. 7, 2020

Feb. 7, 2020

Total of 4 messages in the last 7 days. script run at: Fri 07 Feb 2020 12:53:05 AM EST Messages | Bytes | Who --------+------+--------+----------+------------------------ 25.00% | 1 | 42.83% | 41173 | roberto_gaetano at hotmail.com 25.00% | 1 | 23.45% | 22543 | olivierkouami at gmail.com 25.00% | 1 | 20.47% | 19675 | sebicann at bachollet.fr 25.00% | 1 | 13.25% | 12733 | narten at us.ibm.com --------+------+--------+----------+------------------------ 100.00% | 4 |100.00% | 96124 | Total

1 0

Statement of the Internet Society France about the PIR / .org sale
by Sebicann Bachollet Feb. 6, 2020

Feb. 6, 2020

Dear colleagues Please find the mail send by the Internet Society France President about .org sale. Chers collègues, Merci de trouver ci-après le mail envoyé par le Président du Chapitre de l’Internet Society France. Dear Friends, I want to inform you of the statement of the Internet Society France about the PIR / .org sale. In french and english here : <https://www.isoc.fr/vente-du-point-org/> Vente du .ORG : l’Internet Society France reste vigilant et appelle à reconsidérer cette vente en ouvrant une large consultation des parties prenantes https://www.isoc.fr/vente-du-point-org/ <https://www.isoc.fr/vente-du-point-org/> Sale of .ORG: The Internet Society France is committed and remains vigilant and is calling to reconsider this sale by opening a broad consultation of the stakeholders https://www.isoc.fr/vente-du-point-org/ <https://www.isoc.fr/vente-du-point-org/> (at the end of the page) Warm regards, Nicolas -- Nicolas Chagny Président @ Internet Society France - www.isoc.fr <http://www.isoc.fr/> Membre @ Commission Nationale Consultative des Droits de l'Homme Co-président @ Comité d'Organisation FGI France +33 6 74 97 82 23 twitter.com/nicochagny <https://twitter.com/nicochagny>

2 1

Re: [At-Large] [ALAC-Announce] EXTENSION / 48 Hours: Call for Expressions of Interest in At-Large Fellowship Mentor Position
by Roberto Gaetano Feb. 4, 2020

Feb. 4, 2020

Hi I have been asked about the procedure, can you confirm that it is just an email to Staff? Thanks! R. Inviato da iPhone Il giorno 4 feb 2020, alle ore 08:02, ICANN At-Large Staff <staff(a)atlarge.icann.org> ha scritto: Dear All, Please note the deadline for nominations and submitting EOI’s for the At-Large Fellowship Mentor has been extended to Wednesday, 05 February 2020 at 13:00 UTC The reason for the extension is due to Maureen’s sudden unavailability to attend Monday’s meeting due to travel. The ALAC Appointee Selection Subcommittee (AASC) Meeting has been postponed to give the AASC members 7 days to review EOIs. Kind Regards, ICANN Policy Staff in support of the At-Large Community ________________________________ From: ICANN At-Large Staff Sent: Wednesday, January 29, 2020 4:44 PM To: alac-announce(a)atlarge-lists.icann.org Cc: ICANN At-Large Staff Subject: 48 Hours: Call for Expressions of Interest in At-Large Fellowship Mentor Position Dear All, The recent ALAC Motion on the At-Large Fellowship Mentor resulted in a call for a new Fellowship Mentor selection: ALAC Motion on the At-Large Fellowship Mentor Number of voters: 15 · Group size: 15 · Percentage voted: 100.00 Rank Vote Option ID Vote Option Votes % 1 16030997 Call for a new Mentor selection (Sarah is prepared to re-stand for the position) 7 46.67 2 16030996 Allow Sarah Kiden to complete a full year as Mentor in 2020 6 40.00 3 16030999 Abstain 2 13.33 As a result of the poll, a request is being made for any expression of interest (EOI) in the position no later than Friday, 31 January at 13:00 UTC. A short extension to the appointment of the At-Large Fellowship mentor has been granted. This extension allows the ALAC Subcommittee on Appointee Selection (AASC) to review applicants and determine the selected Fellowship Mentor no later than Tuesday, 4 February. Following this, the ALAC will then hold a Consensus Call on the selected Fellowship Mentor. Kind Regards, ICANN Policy Staff in support of the At-Large Community _______________________________________________ ALAC-Announce mailing list ALAC-Announce(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-announce At-Large Official Site: http://www.atlarge.icann.org _______________________________________________ By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and the website Terms of Service (https://www.icann.org/privacy/tos) You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.

1 0