- At-Large - lists.icann.org

Internet Society Board of Trustees Statement on updated Mission and 2018 Action Plan
by Joly MacFie Nov. 21, 2017

Nov. 21, 2017

The current ISOC BoT, under Chair Gonzalo Camarillo, is a strong group, unafraid to make bold moves. They are keeping up with the evolving Internet landscape, as evidenced in the new mission statement and action plan. joly posted: "At the conclusion of its meeting in Singapore on November 17-19, 2017, the Internet Society Board of Trustees released the following statement: The Internet Society Board of Trustees congratulates our staff, our Chapters, and all of our members for coming" New post on *ISOC-NY NOTICE BOARD* Internet Society Board of Trustees Statement on updated Mission and 2018 Action Plan <http://isoc-ny.org/p2/9627> At the conclusion of its meeting in *Singapore* on *November 17-19, 2017*, the *Internet Society Board of Trustees <https://www.internetsociety.org/board-of-trustees/>* released the following *statement <https://www.internetsociety.org/news/statements/2017/internet-society-board…>* : The Internet Society Board of Trustees congratulates our staff, our Chapters, and all of our members for coming together during the* Internet Society’s 25th anniversary year <https://www.internetsociety.org/25th/>* to celebrate the past and to shape the future. This has been an important year with many accomplishments, including the global *InterCommunity event* <https://www.internetsociety.org/intercommunity/2017/>held in September, which connected people from around the world and shone a spotlight on our work together. We believe this past year has set a foundation for the Internet Society to be an even more effective community and organisation going forward. To prepare for the future, the Board — in consultation with the wider Internet Society community — refreshed our time-honoured and tested vision and mission statements. We believe the robust dialogue about our shared aspirations and goals reflected the passion and commitment of our community, and resulted in a reinvigorated statement of our vision and mission, consistent with our original commitment to an Internet that is for everyone. The updated *Internet Society Mission Statement* <https://www.internetsociety.org/mission/> that we approved at our meeting is as follows: ------------------------------ *The Internet Society supports and promotes the development of the Internet as a global technical infrastructure, a resource to enrich people’s lives, and a force for good in society.* *Our work aligns with our goals for the Internet to be open, globally-connected, secure, and trustworthy. We seek collaboration with all who share these goals.* *Together, we focus on:* - *Building and supporting the communities that make the Internet work;* - *Advancing the development and application of Internet infrastructure, technologies, and open standards; and* - *Advocating for policy that is consistent with our view of the Internet.* ------------------------------ We also approved the organisation’s *2018 Action Plan <https://www.internetsociety.org/action-plan/2018/>*, which focuses people and resources on innovative ways to make a difference in: 1. *assuring Internet access for the hardest to reach places on the globe;* 2. *addressing security challenges emerging from the growing Internet of Things;* 3. *strengthening the global Internet’s routing system; and* 4. *promoting collaborative governance as tool to address a range important issues.* We also strongly agree with the 2018 Action Plan’s emphases on building a strengthened global Internet Society community and organisation, and on fostering key new initiatives that amplify the organisation’s ability to bring about change. Finally, and importantly, as we work to *#shapetomorrow* <http://bit.ly/shapetomorrow> and keep the Internet Society’s commitment to openness, transparency, and community-driven processes, we began exploring how to allocate the people, resources, and energies of the Internet Society for the future. We agreed to work through a strategy for long term sustainability and impact. The Internet Society’s *2017 Global Internet Report: Paths to Our Digital Future <https://future.internetsociety.org/>*, created through an extensive process of input from our community and beyond, will serve as a starting point for further dialogue to create a future-looking plan for addressing emerging issues of concern to our community. It has been an eventful year, and we look forward to building on it in the coming years. We want to applaud our committed staff and its leadership for the good work they do every day to ensure that the Internet is for everyone. *Direct URLs:* - *Statement: https://www.internetsociety.org/news/statements/2017/internet-society-board… <https://www.internetsociety.org/news/statements/2017/internet-society-board…>* - *Internet Society Mission: https://www.internetsociety.org/mission/ <https://www.internetsociety.org/mission/>* - *2018 Action Plan: https://www.internetsociety.org/action-plan/2018/ <https://www.internetsociety.org/action-plan/2018/>* Comment <http://isoc-ny.org/p2/9627#respond> See all comments <http://isoc-ny.org/p2/9627#comments> *Trouble clicking?* Copy and paste this URL into your browser: http://isoc-ny.org/p2/9627

1 0

Re: [At-Large] [ALAC-Internal] Hurricane Maria Domain Registration protectionProtocol
by Kan Kaili Nov. 17, 2017

Nov. 17, 2017

Hi, As Maureen pointed out, this indeed would be a good joint activity of ALAC and ccNSO. According to the response collected, ccNSO's response is likely to be positive. On the other hand, it is also true that ICANN's Board cannot order the ccTLDs to do something beyond their contracts. This reminds me of the multi-stakeholder structure of ISC (Internet Society of China). Whenever there is something that harms consumers' interest, e.g., spam, the following happens: - ISC's academic people will go to the media and have it heard. - In response, a few ISC's industry members will respond with a voluntary solution. - ISC's scholars will compare different solutions and present a preferred one to ISC. - A number of ISC's corporate members adopt to this solution and comeup with a joint announcement, e.g., "Anti-Spam Declaration", making it the industry standard. - ISC will oversee the implementation of this standard, and publicly award industry members for good behaviors. (Companies not complying will be at a great disadvantage.) - The ministry (MIIT) closely observes the whole process, provides support, and makes the solution into regulation when it is widely followed. As ICANN is also a multistakeholder organization, I wonder if we could take a similar approach with ALAC playing the role of ISC or its scholars representing consumers' interests. As I see it, ccNSO is likely to first adopt to this "distress relief" measure, while GNSO will then have to follow. Thank you! Kaili ----- Original Message ----- From: Maureen Hilyard To: ALAC Internal List Sent: Friday, November 17, 2017 12:30 AM Subject: Re: [ALAC-Internal] Hurricane Maria Domain Registration protectionProtocol Hi everyone I have had a response from Katrina (CCNSO Chair) and she agrees that it would be worth exploring and discussing possibilities to help domain name registrants and registrars from affected areas. In response to some suggestions I gave as to how we might contribution to a solution, Katrina raised the concern that "ICANN would not be able to tell ccTLDs what to do, it would have to be their own decision, but this does not mean that the ccNSO shouldn't or can't do anything" Katrina, in conjunction with Alejandra who is their Meeting Programme Coordinator, have suggested: - We organise a discussion at ccNSO Members meeting on Tuesday or Wednesday - “How to help ccTLDs, registrars and registrants in case of severely damaged infrastructure?” (or a similar title) - We will ask Pablo and perhaps somebody from .us or other ccTLDs to tell what it means for people to be cut from the outside world and what they did to help - We would like to invite you (or somebody else from ALAC) and maybe from some other SO/ACs – would be nice if you could share your concerns and your ideas/proposals - We will invite ROs. They are the driving force and the ones who can help the most. For example, during the LACTLD Technical workshop they try to establish redundancy among fellow ccTLDs, especially for small registries. - Discussions It sounds like a great plan for our ALAC/ccNSO session, and very relevant that the meeting will be held in Puerto Rico. Alejandra and I could work together to negotiate a suitable time for the ALAC to participate in the session. Be a change if we went to their meeting place. We could encourage input from other SO/ACs. Comments? On Wed, Nov 15, 2017 at 8:24 PM, Javier Rua <javrua(a)gmail.com> wrote: Don’t leave out gTLDs ! Javier Rúa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua On Nov 16, 2017, at 2:19 AM, Maureen Hilyard <maureen.hilyard(a)gmail.com> wrote: I agree Seun And I have already reached out to Katrina and explained our discussion (and also commended her ccNSO Councillor Pablo Rodriguez's involvement in it). I have asked her how receptive the ccNSO might be to working with At-Large on developing some sort of advice with respect to a more general policy to cover all ccTLD managers who found themselves in a similar situation. Ill get back to the team when she responds. Maureen On Wed, Nov 15, 2017 at 7:53 PM, Seun Ojedeji <seun.ojedeji(a)gmail.com> wrote: Hello Alan, My personal feeling is that the PDP will be a long process and I have my doubts that this can survive a PDP process espcially because a possible solution will involve regiatrar/Registry sacrifice funds. However I think it's worth a try and I think we could check the temperature before even starting a PDP by sending a statement in form of advice to all concerned part of the community. So the kind of advice I am referring to is to send in a teaser to see the reaction from the community. Such advice would note and commend the action taken by .pr and will then encourage/request the respective parties to implement such. ccNSO for instance can take such advice back home to their ccTLD policy process. For GNSO we can then suggest a PDP and hear their initial reaction. For the RIR we can by that advice hear their view about the applicability of this to numbers. So it's kind of a call to action advice. Reese's Sent from my mobile Kindly excuse brevity and typos On Nov 15, 2017 8:46 PM, "Alan Greenberg" <alan.greenberg(a)mcgill.ca> wrote: Seun, what kind of advice are you thinking of? Advice should be actionable. The Board could take would be to enact emergency policy and immediately require that a PDP be initiated to permanently address the issue. I am not sure if the Board has ever used that power and I cannot imagine it doing so now without embarking on a longer study of what sort of mediation was really reasonable. To be clear, we cannot simply start a PDP. We can build a case clearly defining the issue and what a PDP should address, and request that staff create an Issue Report. Once that report is completed (having first issued a Preliminary Issue Report and then having it subjected to a Public Comment), the GNSO Council must then vote on whether or not to initiate a PDP. This is all layed out in detail in Annex A of the ICANN Bylaws - https://www.icann.org/resources/pages/governance/bylaws-en/#annexA. The Request for an Issue Report and the processes which should precede it are laid out in the GNSO PDP Manual ( https://gnso.icann.org/en/council/annex-2-pdp-manual-01sep16-en.pdf ). It is a long process, and includes all sorts of checks and balances. Alan At 15/11/2017 01:37 PM, Seun Ojedeji wrote: I like the idea of going the advice route for a start using the .PR as a case study. We may then include in the advice a recommendation for a PDP if necessary. Regards Sent from my mobile Kindly excuse brevity and typos On Nov 15, 2017 9:41 AM, "Sebicann Bachollet" <sebicann(a)bachollet.fr> wrote: Hello Great exchange, And very well done by .pr I am not sure that the first step is to jump into a PDP. At-Large can start to express a concerne about this situation, send an advice to both the Board, the gNSO and the ccNSO and the same as info to the GAC and other SO/AC, taking as a good practice (here even a best one ;)) what was done by .pr. Supporting cc and g to take actions for that purpose. Ask staff to gather info about any practice both in cc and g worlds (and yes it can become an issue paper at a latest stage). It i very important to frame it as a global issue for users (both individual, SME and NGO) what ever DN they are using. We may wish to involve the RIR if such issue is a problem for IP addresses or for any support. We may also take that into account as a possible exemple of good usage of some fund of the auction proceed (and it is in ICANN mission ;)). Can we ask At-Large staff to open a wiki page to have this exchange and start writing something on the issue? I will not be able to participate to the call organized by Ken as I will be in a plane to Montreal. All the best SeB Le 15 nov. 2017 Ã 07:59, Kan Kaili <kankaili(a)gmail.com> a Ã©crit : Hi, Alan and all, Javier's forwarded email says: "In an effort to protect .pr registrants from losing their domain names within the affected area by hurricane Maria, Puerto Rico Top Level Domain will extend the expiration date of all the domain names that expired on September 20th or thereafter to January 2, 2018. We will reassess the situation at the end of the previously mentioned period to determine whether or not it is necessary to take other preventive measures. " As I understand, if the registrant does not renew in time, the registry/registrar would terminate this registration and make the domain available to other potential buyers. This would take some manpower (and cost) to implement. However, if nothing is done for a period of time, there should not be much, if any, occuring costs. If my above understanding is correct, this should indeed be a rather straightforward PDP. As a matter of fact, I suspect some of the registries/registrars would prefer to include this in their contracts with the registrant in order to be more competitive. Thus, if nobody else, I would like to take the lead on this issue and try it out. Thank you! Kaili ----- Original Message ----- From: Alan Greenberg To: ALAC Internal List ; ALAC Internal List Sent: Wednesday, November 15, 2017 3:58 AM Subject: Re: [ALAC-Internal] Hurricane Maria Domain Registration protection Protocol Actually Seun, I think this could be a rather easy PDP, if approached properly and if we can propose a remediation that makes sense. One of the more interesting aspects is that any remediation implies registrars and registries providing service without being paid up-front, or potentially ever. Alan At 14/11/2017 01:47 PM, Seun Ojedeji wrote: Great gesture from .PR. I see why .pr could easily take this up and I hope future applicable ccTLD will learn from the gesture of .pr. That said, I wonder how this can be applicable globally for gtlds, except through a PDP but I do have my doubt if this can survive a GNSO PDP. Nevertheless perhaps it's worth a try. Regards Sent from my mobile Kindly excuse brevity and typos On Nov 14, 2017 7:09 PM, "Javier Rua" <javrua(a)gmail.com> wrote: Dear ALAC, On the important issue that has been diligently brought by John, and seconded by many, myself included, regarding potential risks of gTLD expirations (non-renewal) during and post natural disaster-related electricity, internet and general logistical failures, I share a bit of info that can be helpful (sent to me by our friends at .PR/ccNSO) to continue framing a discussion of possible ALAC recommendations on global ICANN/ARIN prevention and/or mitigation measures. Javier RÃƒÂºa-Jovet +1-787-396-6511 twitter: @javrua skype: javier.rua1 https://www.linkedin.com/in/javrua On Nov 14, 2017, at 1:23 PM, Pablo Rodriguez <pablo(a)nic.pr> wrote: Dear Javier, In 2011, Japan suferred two terrible disasters, an 9.0 earthquake followed by a Tsunami. Puerto Rico Top Level Domain (.pr) sprung into action and search our databases to find all the domain name registrations in which "Japan" appeared as the country in any of the three contacts (registrant, admin, or Tech). Several of our registrars in Japan were very pleased to learn when they were finally able to contact us that we had proactively extended their expiration dates to prevent domain name losses due to lack of connectivity as a result of the disasters. Below you will find a similar example to protect the cyber real estate of registrants who reside in Puerto Rico and the affected areas (AVI, BVI, etc) by hurricane Maria. Hurricane MarÃƒÂa Domain Registration protection Protocol Puerto Rico Top Level Domain (.pr) has been 100% operational pre-, during, and post hurricane Maria. In an effort to protect .pr registrants from losing their domain names within the affected area by hurricane Maria, Puerto Rico Top Level Domain will extend the expiration date of all the domain names that expired on September 20th or thereafter to January 2, 2018. We will reassess the situation at the end of the previously mentioned period to determine whether or not it is necessary to take other preventive measures. HuracÃƒÂ¡n MarÃƒÂa Protocolo de protecciÃƒÂ³n de registros de dominios Puerto Rico Top Level Domain ha estado 100% operacional previo a, durante, y post huracÃƒÂ¡n MarÃƒÂa. En una iniciativa para proteger los registros de d _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… At-Large Website: http://atlarge.icann.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Microsoft-Exchange-Diagnostics: 1;YQXPR0101MB1589;27:raBhEnfAMJQK4wDOm1IlxWVVwpJp+Dg0C5wgVnrS735mqr7nV2PJY5mpD8PCkL3jVCGhdcabIpVgTSg8PzXBKr8W07FfOt/LOau7AiM7k0B2uK67oGU/T3LPrIzm0RcQ _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… ) At-Large Website: http://atlarge.icann.org ------------------------------------------------------------------------ _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… At-Large Website: http://atlarge.icann.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Microsoft-Exchange-Diagnostics: 1;YQXPR0101MB1589;27:lyPeFsMR2LTmaP9avmNEF6jqNJ598Y+br+SsHKkIAjDu+lGgTNx7rt1tleHhx8p4RzNSvOInojFp9kpA8rUgsNDq2reLZaNotHxXgV/Y14faCFJ7u3u8T+umX+wQQtKZ _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… ) At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… At-Large Website: http://atlarge.icann.org _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… At-Large Website: http://atlarge.icann.org ------------------------------------------------------------------------------ _______________________________________________ ALAC-Internal mailing list ALAC-Internal(a)atlarge-lists.icann.org https://atlarge-lists.icann.org/mailman/listinfo/alac-internal ALAC Wiki: https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(AL… At-Large Website: http://atlarge.icann.org

6 13

Weekly posting summary for at-large@atlarge-lists.icann.org
by narten＠us.ibm.com Nov. 17, 2017

Nov. 17, 2017

Total of 5 messages in the last 7 days. script run at: Fri Nov 17 00:53:04 EST 2017 Messages | Bytes | Who --------+------+--------+----------+------------------------ 40.00% | 2 | 22.83% | 56905 | joly at punkcast.com 20.00% | 1 | 36.90% | 91949 | javrua at gmail.com 20.00% | 1 | 35.65% | 88839 | kankaili at gmail.com 20.00% | 1 | 4.62% | 11510 | narten at us.ibm.com --------+------+--------+----------+------------------------ 100.00% | 5 |100.00% | 249203 | Total

1 0

Join the Internet Society A11ySIG hangout 1pm ET today Weds Nov 15
by Joly MacFie Nov. 15, 2017

Nov. 15, 2017

Starts in 20 mins. Looking forward to hearing from Judith. The ICANN At-Large Tech Task Force Meeting, which we will no doubt discuss is at https://www.facebook.com/isocny/videos/10156593733753538/ Note that, because of the change from EDT to EST, we are an hour later on UTC. Very happy to have a discussion about adjusting call schedule. [image: a11ysig] <http://a11ysig.org/>The *Internet Society Accessibility Special Interest Group <https://zoom.us/j/623946888>* (in formation) will this week be at *1pm ET* on *Wednesday Nov 15 2017.* Please join and share your *#a11y <https://twitter.com/search?f=tweets&vertical=default&q=%23a11y&src=typd>* interests. This week we have *Judith Hellerstein* <https://icannwiki.org/Judith_Hellerstein>, fully recovered from her trip to Abu Dhabi, talking about *ICANN 60 <http://isoc-ny.org/p2/9534>*, plus an open mic for anyone else to step up and talk about their accessibility concerns. *What: Internet Society Accessibility Special Interest Group (A11ySIG) HangoutWhen: Wednesday Nov 15 2017 - 1pm-2pm EDT | 18:00-19:00 UTCJoin from PC, Mac, Linux, iOS or Android: https://zoom.us/j/665487975 <https://zoom.us/j/665487975>iPhone one-tap (US Toll): +14086380968 <(408)%20638-0968>,623946888# or +16465588656 <(646)%20558-8656>,623946888#Telephone: +1 408 638 0968 <(408)%20638-0968> (US Toll) or +1 646 558 8656 <(646)%20558-8656> (US Toll) - Meeting ID: 665-487-975International numbers available: https://zoom.us/zoomconference?m=GbFzjTFwFH1PFm1Ly8Nem33t7jnICnUn <https://zoom.us/zoomconference?m=GbFzjTFwFH1PFm1Ly8Nem33t7jnICnUn>* Comment <http://isoc-ny.org/p2/9594#respond> See all comments <http://isoc-ny.org/p2/9594#comments> *Permalink* http://isoc-ny.org/p2/9594 -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

1 1

Weekly posting summary for at-large@atlarge-lists.icann.org
by narten＠us.ibm.com Nov. 10, 2017

Nov. 10, 2017

Total of 9 messages in the last 7 days. script run at: Fri Nov 10 00:53:04 EST 2017 Messages | Bytes | Who --------+------+--------+----------+------------------------ 33.33% | 3 | 30.54% | 46626 | derek at aa419.org 22.22% | 2 | 38.29% | 58445 | joly at punkcast.com 11.11% | 1 | 10.81% | 16508 | dogwallah at gmail.com 11.11% | 1 | 7.62% | 11634 | narten at us.ibm.com 11.11% | 1 | 6.59% | 10060 | icann-list at sorehands.com 11.11% | 1 | 6.15% | 9383 | johnl at iecc.com --------+------+--------+----------+------------------------ 100.00% | 9 |100.00% | 152656 | Total

1 0

WEBCAST WED/THU: Indigenous Connectivity Summit in Santa Fe #indiginet17
by Joly MacFie Nov. 8, 2017

Nov. 8, 2017

This is underway. A lot of expertise in the room. This is essentially North America oriented but a lot of it will be applicable elsewhere. ICANN was already raised during Kathy Brown's session. [image: livestream] <https://livestream.com/internetsociety/indigenet17>Today and tomorrow Wednesday/Thursday November 8-9 2017 the *Internet Society North America Regional Bureau*, the* Internet Society New Mexico Chapter*, <https://www.internetsociety.org/regions/north-america/>the *1st-Mile Institute* <http://www.1st-mile.org/>, <https://www.internetsociety.org/regions/north-america/>*New Mexico Techworks* <http://www.nmtechworks.com/>, and <https://www.internetsociety.org/regions/north-america/>the *First Mile Connectivity Consortium* <http://firstmile.ca/> present the first ever *Indigenous Connectivity Summit <https://www.internetsociety.org/events/indigenous-connectivity-summit/>*. This community-led forum will showcase success stories of Indigenous community networks in Canada, the United States and around the globe to help find solutions to improve Internet access for all. Themes include community development and sustainability. Speakers include *Kathy Brown*, CEO, Internet Society and *Senator Tom Udall*, Honorary Co-Host. The vent will be webcast live on the* Internet Society Livestream Channel <https://livestream.com/internetsociety/indigenet17>*. Santa Fe is MST, 2 hours ahead of NYC (UTC-7) *What: Indigenous Connectivity Summit <https://www.internetsociety.org/events/indigenous-connectivity-summit/>Where: Santa Fe, NMWhen: Wednesday/Thursday November 8-9 2017Agenda: https://www.internetsociety.org/events/indigenous-connectivity-summit/agenda <https://www.internetsociety.org/events/indigenous-connectivity-summit/agenda>Webcast: https://livestream.com/internetsociety/indigenet17 <https://livestream.com/internetsociety/indigenet17>Twitter: #indigenet17 http://bit.ly/indigenet17 <http://bit.ly/indigenet17>* Comment <http://isoc-ny.org/p2/9561#respond> See all comments <http://isoc-ny.org/p2/9561#comments> *Permalink* http://isoc-ny.org/p2/9561 -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

1 0

Re: [At-Large] Godaddy & ICANN Compliance: Port 43 whois
by Bill Silverstein Nov. 7, 2017

Nov. 7, 2017

> An edited version of a post I made on the APWG. Certain parts have > been redacted to protect innocent victims. The rest is topical here. > > Certain parties at Godaddy were copied on the original. > > ============================================================== > > I'm not sure if here is anybody on list that can address this issue. I > have lodged an ICANN complaint on it, but this is extremely topical in > doing what we do, fighting fraud as this affects each of us. So I'll > share: > > http://blog.aa419.org/2017/09/08/an-open-letter-to-godaddy-whois-service/#O… > > I have reached out to folks in other communities fighting abuse. The > issue is global and complaints are sandbagged. > > To show what a harmful effect this has: > I have been trying to deal with both Godaddy and ICANN about GoDaddy's violation of the RAA requirements to provide port 43 access. The response from Godaddy is that you can go to the web site. ICANN's response is "However, please note that the registrar demonstrated to ICANN it was compliant with its Whois Service obligations at the time the complaint was received in accordance with Section 3.3.5 of the 2013 Registrar Accreditation Agreement (RAA) Additionally, please note, ICANN's authority is purely contractual, and limited to the RAA, the Registry Agreements (RA) and ICANNâs Consensus Policies." What crap! I had provided the proof, but they ignore it.

4 4

WEBCAST TODAY: Europe Regional Internet and Development Dialogue 2017 #RIDD
by Joly MacFie Nov. 7, 2017

Nov. 7, 2017

This is under way. Excellent keynote from Michael Boni. [image: livestream] <https://livestream.com/internetsociety2/riddeurope> .Today, *Tuesday November 7 2017*, the* Internet Society's European Regional Bureau <http://www.isoc.org/regions/europe/>*, *CEPS <https://www.ceps.eu/>*, and the *Committee of the Regions <http://cor.europa.eu/>* are hosting the *Europe Regional Internet and Development Dialogue 2017 <https://www.internetsociety.org/events/ridd/europe/2017/>* in Brussels, Belgium. The theme is 'Will the Internet Benefit All Europeans?'. The Internet is transforming Europe’s rich cities. The metropolises benefit from high speed connections and are the site of most start-ups and new tech jobs. But what are the consequences of this transformation? And what will happen to less populated regions and disadvantaged urban fringes? Speakers include MEP *Michal Boni* and *Vint Cerf*. The day-long event will be webcast via the *Internet Society Livestream Channel <https://livestream.com/internetsociety2/riddeurope>*. Brussels is UTC+1 = 6 hours ahead of NYC *What: Europe Regional Internet and Development Dialogue 2017 <https://www.internetsociety.org/events/ridd/europe/2017/>Where: Brussels, BelgiumWhen: 9:30am-5pm | 08:30-16:00 UTCAgenda: https://www.internetsociety.org/events/ridd/europe/2017/agenda <https://www.internetsociety.org/events/ridd/europe/2017/agenda>Webcast: https://livestream.com/internetsociety2/riddeurope <https://livestream.com/internetsociety2/riddeurope>Twitter: #RIDD http://bit.ly/2zpktpv <http://bit.ly/2zpktpv>* Comment <http://isoc-ny.org/p2/9554#respond> See all comments <http://isoc-ny.org/p2/9554#comments> *Permalink* http://isoc-ny.org/p2/9554 -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

1 0

Godaddy & ICANN Compliance: Port 43 whois
by Derek Smythe Nov. 5, 2017

Nov. 5, 2017

An edited version of a post I made on the APWG. Certain parts have been redacted to protect innocent victims. The rest is topical here. Certain parties at Godaddy were copied on the original. ============================================================== I'm not sure if here is anybody on list that can address this issue. I have lodged an ICANN complaint on it, but this is extremely topical in doing what we do, fighting fraud as this affects each of us. So I'll share: http://blog.aa419.org/2017/09/08/an-open-letter-to-godaddy-whois-service/#O… I have reached out to folks in other communities fighting abuse. The issue is global and complaints are sandbagged. To show what a harmful effect this has: Consider bogus courier (removed - revealing this leads to innocent victims losing their privacy) This domain is being used in international fraud targeting companies and consumers by an international Cameroonian syndicate. While local distinct members have been identified in law enforcement related operations, this blew into the international sphere. Many domains in this syndicate have been documented, all evidence fully captured for LE, in ongoing efforts since Thursday evening. A glimpse: http://www.angloamericanplatinum.com/media/press-releases/2016/17-11-2016.a… We were working hard at this, when we hit (removed-domain) on Godaddy - a simple issue of not being able to capture a "standards compliant" port 43 whois output format, something supposedly well defined as per ICANN policy that should be available, yet this became a time wasting stumbling block. It took me about 2 hours to get a usable format of whois for this domain. That's how stupid it gets ... (removed-domain) has been scamming and piling up victim companies and consumers since 2016. The targets (each separate) are in: 2016: Vietnam - 1 ton of waste paper Malaysia- 1 ton of waste paper USA - 100 GRAM Discrete parcel (Drug scam?) USA - 300 Kg lobster tail USA - 1.35 tons of skin care products Armenia - 1 ton nuts Thailand - 20ft container of seafood 2017: Ukraine - 5kg Wooden pellets Russia - 2500 reams of paper * Brussels - 2 x 40ft containers of wooden pellets USA - not much info, except from somebody selling "Legal Marijuana". USA - 1 oz purple kush India - 18 tons (20ft container) of ??? Turkey - 50 tons of old newspapers India - 25 tons of waste corrugated paperboard Dubai - 2kgs of red lentils, chick peas, mung beans USA - 50kg crayfish USA - Yacht Saudi Arabia - 10kgs round mullet Fiji - 5 cartons of BIC gas lighters, 1000 pcs/carton India - 2600 reams of paper * * https://www.doubleapaper.com/nl/fraud-alert Each scam leads to another fake supplier and more of these fake couriers. This is akin to "How long is a piece of string?". So now that we know how this $3 bill domain is being abused, we look at it's whois after much effort at getting it only to find another domain attributable to the same party, but suddenly in Thailand, shut down for involvement in paper scams. (removed-domain states an Indian address) While there is "so much concern for the privacy" of the owners of (removed-domain), the owners of this domain do not have any problem trivially leaking personal details of their targets onto the web. Simply search for (removed) and follow the directory up ... enough said. It's also the last issue on tel nr (removed), that leads to alerts such as: https://www.deadiversion.usdoj.gov/pubs/pressreleases/extortion_scam.htm I hope this sheds some light on which fight being fought by very few volunteers, is being hampered by ill advised non-policy conforming registrars blocking of whois details. It's not always LE that opens the "can of worms". LE deals with the result (hopefully) once it's made clear it is a "can of worms". But if LE is not shown the evidence and relevance, they have nothing to go on and it did not happen. Yet tell that to these parties targeted and exposed internationally. Sadly most such cases gather dust at local police stations or like. Yet the victim may be a mom-and-pop shop business, the livelihood of the owners and all associated with them destroyed by the scam. Privacy and protecting privacy is a delicate balancing act between protection and disclosure, very ill understood. I had some discussions with numerous expert who failed to understand how due diligence down to whois level protects all. In this case I used the loan scam nest from Benin as an example. Whois details were vital to untangling this nest and mess. They were either shocked or did a quick pass-the-buck exercise. Luckily EU Registrars did a stellar job mitigating the Benin nest, devastating it. But what about next time? I shudder to think we encounter such a nest on Godaddy. =============================== Hopefully this makes the people here think of exactly what effect whois, or the inability of obtaining whois details, has in a real world environment. Sweeping problematic whois under the carpet of blanket privacy in an environment where policies are weakly enforced, is a recipe for a bloodbath. We're already seeing the effects at one such US registrar who have become the go-to registrar for badness in the domain space. Derek Smythe Artists Against 419 http://www.aa419.org

1 0

Weekly posting summary for at-large@atlarge-lists.icann.org
by narten＠us.ibm.com Nov. 3, 2017

Nov. 3, 2017

Total of 9 messages in the last 7 days. script run at: Fri Nov 3 00:53:03 EDT 2017 Messages | Bytes | Who --------+------+--------+----------+------------------------ 22.22% | 2 | 35.96% | 127432 | salanieta.tamanikaiwaimaro at gmail.com 22.22% | 2 | 23.09% | 81827 | sala at pasifikanexus.nu 11.11% | 1 | 20.33% | 72026 | vanda at scartezini.org 11.11% | 1 | 9.21% | 32655 | joly at punkcast.com 11.11% | 1 | 5.29% | 18741 | carlton.samuels at gmail.com 11.11% | 1 | 3.25% | 11524 | narten at us.ibm.com 11.11% | 1 | 2.87% | 10163 | derek at aa419.org --------+------+--------+----------+------------------------ 100.00% | 9 |100.00% | 354368 | Total

1 0