REMINDER | Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 06 October 2021 at 13:00 UTC
***If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org<mailto:staff@atlarge.icann.org> with your preferred number*** Dear All, The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 06 October 2021 at 13:00 UTC for 90 mins. For other times:https://tinyurl.com/3377wmsa The agenda and call details can be found at: https://community.icann.org/x/FwiHCg Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/ Passcode: #CPWG2345* Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN ADIGO Conference Bridge: EN: 1638 ES: 1738 FR: 1838 Toll-free access number (US and Canada): 800 550 686 Other toll-free numbers: https://www.adigo.com/icann At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org<mailto:staff@atlarge.icann.org> Thank you. Kind Regards, At-Large Staff ICANN Policy Staff in support of the At-Large Community Website: atlarge.icann.org<https://atlarge.icann.org/> Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>atlarge<https://www.facebook.com/icannatlarge> Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<https://twitter.com/ICANNAtLarge>
Good evening: Thankyou. Noted. Please add to the agenda (first point): "The DNS and Social Media - what lessons to be learnt from the current situation?" By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users. If so, that requires an official response from ICANN, now. CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org> wrote:
***If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org <mailto:staff@atlarge.icann.org> with your preferred number***
Dear All,
The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 06 October 2021 at 13:00 UTC for 90 mins.
For other times:https://tinyurl.com/3377wmsa <https://tinyurl.com/3377wmsa>
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg <https://community.icann.org/x/FwiHCg>
Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/ <https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/> Passcode: #CPWG2345*
Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN <https://www.streamtext.net/player?event=ICANN>
ADIGO Conference Bridge: EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann <https://www.adigo.com/icann>
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB <https://community.icann.org/x/jYDpB>
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org <mailto:staff@atlarge.icann.org> Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org <https://atlarge.icann.org/> Facebook: facebook.com/icann <https://www.facebook.com/icannatlarge>atlarge <https://www.facebook.com/icannatlarge> Twitter: @ <https://twitter.com/ICANNAtLarge>ICANNAtLarge <https://twitter.com/ICANNAtLarge>
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics>_______________________________________________ CPWG mailing list CPWG@icann.org <mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg>
_______________________________________________ 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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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.
I agree. My thinking: The DNS uses “resource records”, which are "persistently stored [non-volatile]", formatted data structures that include information relevant to performing DNS tasks. The recent rise of byte-addressable non-volatile memory technologies allow programmers to have direct access to persistent data instead of relying on traditional interfaces such as file and database systems. This simply implies that the distinction between store [non-volatile] and Memory [Volatile] is blurring and seemingly complex objects are now readily persistent. The quest for high - performance for social media sites even when the bandwidth is not so encouraging makes one resort to "saving data for future access" even after the access to a complex object is deemed complete. Today, we have "persistence / repository layer" that tailors the performance/durability trade off for data to a specific enterprise application. There are many challenges and some emerging solutions / best practices. A part of the answer to the question may be in addressing it from this viewpoint. I will wait for other views and opinions. Sincerely, Gopal T V 0 9840121302 https://vidwan.inflibnet.ac.in/profile/57545 https://www.facebook.com/gopal.tadepalli ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Dr. T V Gopal Professor Department of Computer Science and Engineering College of Engineering Anna University Chennai - 600 025, INDIA Ph : (Off) 22351723 Extn. 3340 (Res) 24454753 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On 2021-10-05 03:09, lists--- via CPWG wrote:
Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org> wrote:
_***IF YOU REQUIRE A DIAL OUT OR NEED TO STATE AN APOLOGY, PLEASE CONTACT AT-LARGE STAFF AT STAFF@ATLARGE.ICANN.ORG__ __WITH YOUR PREFERRED NUMBER***_
Dear All,
The next AT-LARGE CONSOLIDATED POLICY WORKING GROUP (CPWG) CALL is scheduled for WEDNESDAY, 06 OCTOBER 2021 AT 13:00 UTC for 90 mins.
For other times:https://tinyurl.com/3377wmsa
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg
ZOOM ROOM:
https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/
[1]
PASSCODE: #CPWG2345*
REAL TIME TRANSCRIPTION (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN [2]
ADIGO CONFERENCE BRIDGE: EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann [3]
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB [4]
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org
Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org [5]
Facebook: facebook.com/icann [6]atlarge [6]
Twitter: @ [7]ICANNAtLarge [7]
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics>_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
Links: ------ [1] https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/ [2] https://www.streamtext.net/player?event=ICANN [3] https://www.adigo.com/icann [4] https://community.icann.org/x/jYDpB [5] https://atlarge.icann.org/ [6] https://www.facebook.com/icannatlarge [7] https://twitter.com/ICANNAtLarge _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
I agree. My thinking: The DNS uses “resource records”, which are "persistently stored [non-volatile]", formatted data structures that include information relevant to performing DNS tasks. The recent rise of byte-addressable non-volatile memory technologies allow programmers to have direct access to persistent data instead of relying on traditional interfaces such as file and database systems. This simply implies that the distinction between store [non-volatile] and Memory [Volatile] is blurring and seemingly complex objects are now readily persistent. The quest for high - performance for social media sites even when the bandwidth is not so encouraging makes one resort to "saving data for future access" even after the access to a complex object is deemed complete. Today, we have "persistence / repository layer" that tailors the performance/durability trade off for data to a specific enterprise application. There are many challenges and some emerging solutions / best practices. A part of the answer to the question may be in addressing it from this viewpoint. I will wait for other views and opinions. Sincerely, Gopal T V 0 9840121302 https://vidwan.inflibnet.ac.in/profile/57545 https://www.facebook.com/gopal.tadepalli ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Dr. T V Gopal Professor Department of Computer Science and Engineering College of Engineering Anna University Chennai - 600 025, INDIA Ph : (Off) 22351723 Extn. 3340 (Res) 24454753 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On 2021-10-05 03:09, lists--- via CPWG wrote:
Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org> wrote:
_***IF YOU REQUIRE A DIAL OUT OR NEED TO STATE AN APOLOGY, PLEASE CONTACT AT-LARGE STAFF AT STAFF@ATLARGE.ICANN.ORG__ __WITH YOUR PREFERRED NUMBER***_
Dear All,
The next AT-LARGE CONSOLIDATED POLICY WORKING GROUP (CPWG) CALL is scheduled for WEDNESDAY, 06 OCTOBER 2021 AT 13:00 UTC for 90 mins.
For other times:https://tinyurl.com/3377wmsa
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg
ZOOM ROOM:
https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/
[1]
PASSCODE: #CPWG2345*
REAL TIME TRANSCRIPTION (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN [2]
ADIGO CONFERENCE BRIDGE: EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann [3]
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB [4]
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org
Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org [5]
Facebook: facebook.com/icann [6]atlarge [6]
Twitter: @ [7]ICANNAtLarge [7]
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics>_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
Links: ------ [1] https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/ [2] https://www.streamtext.net/player?event=ICANN [3] https://www.adigo.com/icann [4] https://community.icann.org/x/jYDpB [5] https://atlarge.icann.org/ [6] https://www.facebook.com/icannatlarge [7] https://twitter.com/ICANNAtLarge _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
Dear Christopher, what is ICANN to do? Is it in its mission to be the "Defender of the DNS"? I wonder... Perhaps ISOC could write something but from memory I can't recall ICANN making such a statement when such incidents happened in the past. Or perhaps it did? We could ask OCTO what's his point of view on this. Kindest regards, Olivier On 05/10/2021 00:39, lists--- via CPWG wrote:
Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org <mailto:cpwg@icann.org>> wrote:
*/***If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org <mailto:staff@atlarge.icann.org>/**//**/with your preferred number***/*
Dear All,
The next *At-Large Consolidated Policy Working Group (CPWG) Call *is scheduled for *Wednesday, 06 October 2021 at 13:00 UTC* for 90 mins.
For other times:https://tinyurl.com/3377wmsa <https://tinyurl.com/3377wmsa>
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg <https://community.icann.org/x/FwiHCg>
*Zoom Room: *https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/ <https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/>
*Passcode:* #CPWG2345*
*Real time transcription (RTT)* available at (subject to availability): https://www.streamtext.net/player?event=ICANN <https://www.streamtext.net/player?event=ICANN>
*ADIGO Conference Bridge:* EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann <https://www.adigo.com/icann>
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB <https://community.icann.org/x/jYDpB>
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org <mailto:staff@atlarge.icann.org>
Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org <https://atlarge.icann.org/>
Facebook: facebook.com/icann <https://www.facebook.com/icannatlarge>atlarge <https://www.facebook.com/icannatlarge>
Twitter: @ <https://twitter.com/ICANNAtLarge>ICANNAtLarge <https://twitter.com/ICANNAtLarge>
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics>_______________________________________________ CPWG mailing list CPWG@icann.org <mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg>
_______________________________________________ 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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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.
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html
On 05/10/2021 13:20, Olivier MJ Crépin-Leblond via CPWG wrote:
Dear Christopher,
what is ICANN to do? Is it in its mission to be the "Defender of the DNS"? I wonder... Perhaps ISOC could write something but from memory I can't recall ICANN making such a statement when such incidents happened in the past. Or perhaps it did? We could ask OCTO what's his point of view on this. Kindest regards,
Olivier
On 05/10/2021 00:39, lists--- via CPWG wrote:
Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
It isn't really an ICANN issue. The "technology" journalists seem to have confused what happened with FB with being simply a DNS issue. The DNS aspect was only a small part of the problem. Facebook effectively knocked itself off the Internet around 15:40 UTC on 04 October. Facebook basically withdrew its routes to the Internet and all services on the IP addresses became unreachable. Its DNS, mailservers and webservers were affected. Think of it like all roads to and from a capital city effectively disappearing within a few minutes. Both the city and its environs still exist but they are no longer connected by roads. This is a good explanation of the effects: https://blog.cloudflare.com/october-2021-facebook-outage/ Apart from FB screwing up like this, I don't think that ICANN can do much for the Dunning Kruger effect of "technology" journalists without a background in or understanding of Technology waffling about it. Perhaps ICANN can circulate yet another very simple explanation of how the Internet works and the role that DNS plays? It won't stop outages like this happening in the future and it won't stop "technology" journalists playing at being clueful. Regards...jmcc -- ********************************************************** John McCormac * e-mail: jmcc@hosterstats.com MC2 * web: http://www.hosterstats.com/ 22 Viewmount * Domain Registrations Statistics Waterford * Domnomics - the business of domain names Ireland * https://amzn.to/2OPtEIO IE * Skype: hosterstats.com ********************************************************** -- This email has been checked for viruses by AVG. https://www.avg.com
I'm afraid the initial reports by the mainstream media pointing a finger at DNS were a red herring. If you dig down a level, you'll see that the DNS system was prevented from working because of a bad BGP configuration change, i.e. Facebook's IP network failed. When It's not DNS, it's BGP -- Facebook, Instagram, Whatsapp and Oculus are Down <https://arstechnica.com/information-technology/2021/10/facebook-instagram-wh...> - Ars Technica
From what I understand, it appears Facebook's weak IP network architecture is to blame. It does not separate network admin traffic from service content traffic. It's common practice in telecom networks to build better, more robust failsafe mechanisms into their networks.
Conclusion: It's unlikely that the DNS system has anything to do with Facebook's outage. Facebook simply needs to improve it's networking infrastructure. That's definitely not an ICANN issue. Cheers David On Tue, Oct 5, 2021 at 8:21 AM Olivier MJ Crépin-Leblond via CPWG < cpwg@icann.org> wrote:
Dear Christopher,
what is ICANN to do? Is it in its mission to be the "Defender of the DNS"? I wonder... Perhaps ISOC could write something but from memory I can't recall ICANN making such a statement when such incidents happened in the past. Or perhaps it did? We could ask OCTO what's his point of view on this. Kindest regards,
Olivier
On 05/10/2021 00:39, lists--- via CPWG wrote:
Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org> wrote:
****If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org <staff@atlarge.icann.org>* *with your preferred number****
Dear All,
The next *At-Large Consolidated Policy Working Group (CPWG) Call *is scheduled for *Wednesday, 06 October 2021 at 13:00 UTC* for 90 mins.
For other times:https://tinyurl.com/3377wmsa
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg
*Zoom Room: * https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/
*Passcode:* #CPWG2345*
*Real time transcription (RTT)* available at (subject to availability): https://www.streamtext.net/player?event=ICANN
*ADIGO Conference Bridge:* EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org
Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org
Facebook: facebook.com/icann <https://www.facebook.com/icannatlarge> atlarge <https://www.facebook.com/icannatlarge>
Twitter: @ <https://twitter.com/ICANNAtLarge>ICANNAtLarge <https://twitter.com/ICANNAtLarge>
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics> _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing listCPWG@icann.orghttps://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
HI All, I agree with David. But what OCTO and At Large can do is publish the blogs such as cloudflare which is written for simple explanations or disseminate and OCTO Blog to explain what happened and how it is not really a DNS issue. Best, Judith Sent from my iPad judith@jhellerstein.com Skype ID:JudithHellerstein
On Oct 5, 2021, at 9:35 AM, David Mackey via CPWG <cpwg@icann.org> wrote:
I'm afraid the initial reports by the mainstream media pointing a finger at DNS were a red herring.
If you dig down a level, you'll see that the DNS system was prevented from working because of a bad BGP configuration change, i.e. Facebook's IP network failed.
When It's not DNS, it's BGP -- Facebook, Instagram, Whatsapp and Oculus are Down - Ars Technica
From what I understand, it appears Facebook's weak IP network architecture is to blame. It does not separate network admin traffic from service content traffic. It's common practice in telecom networks to build better, more robust failsafe mechanisms into their networks.
Conclusion: It's unlikely that the DNS system has anything to do with Facebook's outage. Facebook simply needs to improve it's networking infrastructure. That's definitely not an ICANN issue.
Cheers David
On Tue, Oct 5, 2021 at 8:21 AM Olivier MJ Crépin-Leblond via CPWG <cpwg@icann.org> wrote: Dear Christopher,
what is ICANN to do? Is it in its mission to be the "Defender of the DNS"? I wonder... Perhaps ISOC could write something but from memory I can't recall ICANN making such a statement when such incidents happened in the past. Or perhaps it did? We could ask OCTO what's his point of view on this. Kindest regards,
Olivier
On 05/10/2021 00:39, lists--- via CPWG wrote:
Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org> wrote:
***If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org with your preferred number***
Dear All,
The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 06 October 2021 at 13:00 UTC for 90 mins.
For other times:https://tinyurl.com/3377wmsa
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg
Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/
Passcode: #CPWG2345*
Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN
ADIGO Conference Bridge: EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org
Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org
Facebook: facebook.com/icannatlarge
Twitter: @ICANNAtLarge
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics>_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
Hi, just saw that David Conrad is no longer the CTO. Regards Ricardo El mar., 5 oct. 2021 16:18, Judith Hellerstein via CPWG <cpwg@icann.org> escribió:
HI All, I agree with David. But what OCTO and At Large can do is publish the blogs such as cloudflare which is written for simple explanations or disseminate and OCTO Blog to explain what happened and how it is not really a DNS issue.
Best, Judith
Sent from my iPad judith@jhellerstein.com Skype ID:JudithHellerstein
On Oct 5, 2021, at 9:35 AM, David Mackey via CPWG <cpwg@icann.org> wrote:
I'm afraid the initial reports by the mainstream media pointing a finger at DNS were a red herring.
If you dig down a level, you'll see that the DNS system was prevented from working because of a bad BGP configuration change, i.e. Facebook's IP network failed.
When It's not DNS, it's BGP -- Facebook, Instagram, Whatsapp and Oculus are Down <https://arstechnica.com/information-technology/2021/10/facebook-instagram-wh...> - Ars Technica
From what I understand, it appears Facebook's weak IP network architecture is to blame. It does not separate network admin traffic from service content traffic. It's common practice in telecom networks to build better, more robust failsafe mechanisms into their networks.
Conclusion: It's unlikely that the DNS system has anything to do with Facebook's outage. Facebook simply needs to improve it's networking infrastructure. That's definitely not an ICANN issue.
Cheers David
On Tue, Oct 5, 2021 at 8:21 AM Olivier MJ Crépin-Leblond via CPWG < cpwg@icann.org> wrote:
Dear Christopher,
what is ICANN to do? Is it in its mission to be the "Defender of the DNS"? I wonder... Perhaps ISOC could write something but from memory I can't recall ICANN making such a statement when such incidents happened in the past. Or perhaps it did? We could ask OCTO what's his point of view on this. Kindest regards,
Olivier
On 05/10/2021 00:39, lists--- via CPWG wrote:
Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org> wrote:
****If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org <staff@atlarge.icann.org>* *with your preferred number****
Dear All,
The next *At-Large Consolidated Policy Working Group (CPWG) Call *is scheduled for *Wednesday, 06 October 2021 at 13:00 UTC* for 90 mins.
For other times:https://tinyurl.com/3377wmsa
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg
*Zoom Room: * https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/
*Passcode:* #CPWG2345*
*Real time transcription (RTT)* available at (subject to availability): https://www.streamtext.net/player?event=ICANN
*ADIGO Conference Bridge:* EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org
Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org
Facebook: facebook.com/icann <https://www.facebook.com/icannatlarge> atlarge <https://www.facebook.com/icannatlarge>
Twitter: @ <https://twitter.com/ICANNAtLarge>ICANNAtLarge <https://twitter.com/ICANNAtLarge>
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics> _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing listCPWG@icann.orghttps://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
Good evening: Thankyou, all. I agree with Judith. As my original message indicated, today, this is not mainly about the technical interfaces between the DNS (ICANN) and the Social media neetworks (FB). It is about informed - or otherwise - public perception. So, i maintain my request for OCTO to say something concrete that we can use locally, soon. .(EN/FR/ES, please) Meanwhile, I ask to maintain the Social Media point on the CPWG agenda tomorrow. Themes: - Internet architecture: No single point of failure; That principle was one of the best proitections of users' interests; - DNS abuse - in the light of today's US Congressional Hearings on Facebook. Regards CW
On 5 Oct 2021, at 15:41, Judith Hellerstein via CPWG <cpwg@icann.org> wrote:
HI All, I agree with David. But what OCTO and At Large can do is publish the blogs such as cloudflare which is written for simple explanations or disseminate and OCTO Blog to explain what happened and how it is not really a DNS issue.
Best, Judith
Sent from my iPad judith@jhellerstein.com Skype ID:JudithHellerstein
On Oct 5, 2021, at 9:35 AM, David Mackey via CPWG <cpwg@icann.org> wrote:
I'm afraid the initial reports by the mainstream media pointing a finger at DNS were a red herring.
If you dig down a level, you'll see that the DNS system was prevented from working because of a bad BGP configuration change, i.e. Facebook's IP network failed.
When It's not DNS, it's BGP -- Facebook, Instagram, Whatsapp and Oculus are Down <https://arstechnica.com/information-technology/2021/10/facebook-instagram-wh...> - Ars Technica
From what I understand, it appears Facebook's weak IP network architecture is to blame. It does not separate network admin traffic from service content traffic. It's common practice in telecom networks to build better, more robust failsafe mechanisms into their networks.
Conclusion: It's unlikely that the DNS system has anything to do with Facebook's outage. Facebook simply needs to improve it's networking infrastructure. That's definitely not an ICANN issue.
Cheers David
On Tue, Oct 5, 2021 at 8:21 AM Olivier MJ Crépin-Leblond via CPWG <cpwg@icann.org <mailto:cpwg@icann.org>> wrote: Dear Christopher,
what is ICANN to do? Is it in its mission to be the "Defender of the DNS"? I wonder... Perhaps ISOC could write something but from memory I can't recall ICANN making such a statement when such incidents happened in the past. Or perhaps it did? We could ask OCTO what's his point of view on this. Kindest regards,
Olivier
On 05/10/2021 00:39, lists--- via CPWG wrote:
Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org <mailto:cpwg@icann.org>> wrote:
***If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org <mailto:staff@atlarge.icann.org> with your preferred number***
Dear All,
The next At-Large Consolidated Policy Working Group (CPWG) Call is scheduled for Wednesday, 06 October 2021 at 13:00 UTC for 90 mins.
For other times:https://tinyurl.com/3377wmsa <https://tinyurl.com/3377wmsa>
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg <https://community.icann.org/x/FwiHCg>
Zoom Room: https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/ <https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/> Passcode: #CPWG2345*
Real time transcription (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN <https://www.streamtext.net/player?event=ICANN>
ADIGO Conference Bridge: EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann <https://www.adigo.com/icann>
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB <https://community.icann.org/x/jYDpB>
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org <mailto:staff@atlarge.icann.org> Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org <https://atlarge.icann.org/> Facebook: facebook.com/icann <https://www.facebook.com/icannatlarge>atlarge <https://www.facebook.com/icannatlarge> Twitter: @ <https://twitter.com/ICANNAtLarge>ICANNAtLarge <https://twitter.com/ICANNAtLarge>
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics>_______________________________________________ CPWG mailing list CPWG@icann.org <mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg>
_______________________________________________ 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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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.
_______________________________________________ CPWG mailing list CPWG@icann.org <mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg>
_______________________________________________ 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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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.
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html <http://www.gih.com/ocl.html>_______________________________________________ CPWG mailing list CPWG@icann.org <mailto:CPWG@icann.org> https://mm.icann.org/mailman/listinfo/cpwg <https://mm.icann.org/mailman/listinfo/cpwg>
_______________________________________________ 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 <https://www.icann.org/privacy/policy>) and the website Terms of Service (https://www.icann.org/privacy/tos <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. _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
Thank you for the discussion on this thread. ICANN needs to take a position very quickly. Understandably, there are many articles, blogs on this very important and current topic. I look forward to the CPWG meeting later in the evening. Sincerely, Gopal T V 0 9840121302 https://vidwan.inflibnet.ac.in/profile/57545 https://www.facebook.com/gopal.tadepalli ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Dr. T V Gopal Professor Department of Computer Science and Engineering College of Engineering Anna University Chennai - 600 025, INDIA Ph : (Off) 22351723 Extn. 3340 (Res) 24454753 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On 2021-10-05 22:27, lists--- via CPWG wrote:
Good evening:
Thankyou, all. I agree with Judith. As my original message indicated, today, this is not mainly about the technical interfaces between the DNS (ICANN) and the Social media neetworks (FB). It is about informed - or otherwise - public perception. So, i maintain my request for OCTO to say something concrete that we can use locally, soon. .(EN/FR/ES, please)
Meanwhile, I ask to maintain the Social Media point on the CPWG agenda tomorrow. Themes:
- Internet architecture: No single point of failure; That principle was one of the best proitections of users' interests;
- DNS abuse - in the light of today's US Congressional Hearings on Facebook.
Regards
CW
On 5 Oct 2021, at 15:41, Judith Hellerstein via CPWG <cpwg@icann.org> wrote:
HI All, I agree with David. But what OCTO and At Large can do is publish the blogs such as cloudflare which is written for simple explanations or disseminate and OCTO Blog to explain what happened and how it is not really a DNS issue.
Best, Judith
Sent from my iPad judith@jhellerstein.com Skype ID:JudithHellerstein
On Oct 5, 2021, at 9:35 AM, David Mackey via CPWG <cpwg@icann.org> wrote:
I'm afraid the initial reports by the mainstream media pointing a finger at DNS were a red herring.
If you dig down a level, you'll see that the DNS system was prevented from working because of a bad BGP configuration change, i.e. Facebook's IP network failed.
When It's not DNS, it's BGP -- Facebook, Instagram, Whatsapp and Oculus are Down [1] - Ars Technica
From what I understand, it appears Facebook's weak IP network architecture is to blame. It does not separate network admin traffic from service content traffic. It's common practice in telecom networks to build better, more robust failsafe mechanisms into their networks.
Conclusion: It's unlikely that the DNS system has anything to do with Facebook's outage. Facebook simply needs to improve it's networking infrastructure. That's definitely not an ICANN issue.
Cheers David
On Tue, Oct 5, 2021 at 8:21 AM Olivier MJ Crépin-Leblond via CPWG <cpwg@icann.org> wrote:
Dear Christopher,
what is ICANN to do? Is it in its mission to be the "Defender of the DNS"? I wonder... Perhaps ISOC could write something but from memory I can't recall ICANN making such a statement when such incidents happened in the past. Or perhaps it did? We could ask OCTO what's his point of view on this. Kindest regards,
Olivier
On 05/10/2021 00:39, lists--- via CPWG wrote: Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org> wrote:
_***IF YOU REQUIRE A DIAL OUT OR NEED TO STATE AN APOLOGY, PLEASE CONTACT AT-LARGE STAFF AT STAFF@ATLARGE.ICANN.ORG__ __WITH YOUR PREFERRED NUMBER***_
Dear All,
The next AT-LARGE CONSOLIDATED POLICY WORKING GROUP (CPWG) CALL is scheduled for WEDNESDAY, 06 OCTOBER 2021 AT 13:00 UTC for 90 mins.
For other times:https://tinyurl.com/3377wmsa
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg
ZOOM ROOM:
https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/
[2]
PASSCODE: #CPWG2345*
REAL TIME TRANSCRIPTION (RTT) available at (subject to availability): https://www.streamtext.net/player?event=ICANN [3]
ADIGO CONFERENCE BRIDGE: EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann [4]
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB [5]
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org
Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org [6]
Facebook: facebook.com/icann [7]atlarge [7]
Twitter: @ [8]ICANNAtLarge [8]
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics>_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
-- Olivier MJ Crépin-Leblond, PhD http://www.gih.com/ocl.html _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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. _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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._______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
Links: ------ [1] https://arstechnica.com/information-technology/2021/10/facebook-instagram-wh... [2] https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/ [3] https://www.streamtext.net/player?event=ICANN [4] https://www.adigo.com/icann [5] https://community.icann.org/x/jYDpB [6] https://atlarge.icann.org/ [7] https://www.facebook.com/icannatlarge [8] https://twitter.com/ICANNAtLarge _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
Interesting, important topics, but apologies, I am on road. Sivasubramanian M On Tue, Oct 5, 2021, 22:29 lists--- via CPWG <cpwg@icann.org> wrote:
Good evening:
Thankyou, all. I agree with Judith. As my original message indicated, today, this is not mainly about the technical interfaces between the DNS (ICANN) and the Social media neetworks (FB). It is about informed - or otherwise - public perception. So, i maintain my request for OCTO to say something concrete that we can use locally, soon. .(EN/FR/ES, please)
Meanwhile, I ask to maintain the Social Media point on the CPWG agenda tomorrow. Themes:
- Internet architecture: No single point of failure; That principle was one of the best proitections of users' interests;
- DNS abuse - in the light of today's US Congressional Hearings on Facebook.
Regards
CW
On 5 Oct 2021, at 15:41, Judith Hellerstein via CPWG <cpwg@icann.org> wrote:
HI All, I agree with David. But what OCTO and At Large can do is publish the blogs such as cloudflare which is written for simple explanations or disseminate and OCTO Blog to explain what happened and how it is not really a DNS issue.
Best, Judith
Sent from my iPad judith@jhellerstein.com Skype ID:JudithHellerstein
On Oct 5, 2021, at 9:35 AM, David Mackey via CPWG <cpwg@icann.org> wrote:
I'm afraid the initial reports by the mainstream media pointing a finger at DNS were a red herring.
If you dig down a level, you'll see that the DNS system was prevented from working because of a bad BGP configuration change, i.e. Facebook's IP network failed.
When It's not DNS, it's BGP -- Facebook, Instagram, Whatsapp and Oculus are Down <https://arstechnica.com/information-technology/2021/10/facebook-instagram-wh...> - Ars Technica
From what I understand, it appears Facebook's weak IP network architecture is to blame. It does not separate network admin traffic from service content traffic. It's common practice in telecom networks to build better, more robust failsafe mechanisms into their networks.
Conclusion: It's unlikely that the DNS system has anything to do with Facebook's outage. Facebook simply needs to improve it's networking infrastructure. That's definitely not an ICANN issue.
Cheers David
On Tue, Oct 5, 2021 at 8:21 AM Olivier MJ Crépin-Leblond via CPWG < cpwg@icann.org> wrote:
Dear Christopher,
what is ICANN to do? Is it in its mission to be the "Defender of the DNS"? I wonder... Perhaps ISOC could write something but from memory I can't recall ICANN making such a statement when such incidents happened in the past. Or perhaps it did? We could ask OCTO what's his point of view on this. Kindest regards,
Olivier
On 05/10/2021 00:39, lists--- via CPWG wrote:
Good evening:
Thankyou. Noted.
Please add to the agenda (first point):
"The DNS and Social Media - what lessons to be learnt from the current situation?"
By way of explanation, this request is as much about perception and PR as about the eventaul facts-. Local Global Media (e.g. BBC) are attributing the collapse of Facebook, Whatsap and Instagram to issues with the Domain Nam System,. Affecting "billions" of users.
If so, that requires an official response from ICANN, now.
CW
On 4 Oct 2021, at 18:59, ICANN At-Large Staff via CPWG <cpwg@icann.org> wrote:
****If you require a dial out or need to state an apology, please contact At-Large staff at staff@atlarge.icann.org <staff@atlarge.icann.org>* *with your preferred number****
Dear All,
The next *At-Large Consolidated Policy Working Group (CPWG) Call *is scheduled for *Wednesday, 06 October 2021 at 13:00 UTC* for 90 mins.
For other times:https://tinyurl.com/3377wmsa
The agenda and call details can be found at: https://community.icann.org/x/FwiHCg
*Zoom Room: * https://icann.zoom.us/j/765717566?pwd=UTJCdWRSZVdJNEhOYW02OVBqQVQ1Zz09/
*Passcode:* #CPWG2345*
*Real time transcription (RTT)* available at (subject to availability): https://www.streamtext.net/player?event=ICANN
*ADIGO Conference Bridge:* EN: 1638
ES: 1738
FR: 1838
Toll-free access number (US and Canada): 800 550 686
Other toll-free numbers: https://www.adigo.com/icann
At-Large Consolidated Policy Working Group (CPWG) Wiki Space: https://community.icann.org/x/jYDpB
If you require a dial-out please contact At-Large staff at: staff@atlarge.icann.org
Thank you.
Kind Regards,
At-Large Staff
ICANN Policy Staff in support of the At-Large Community
Website: atlarge.icann.org
Facebook: facebook.com/icann <https://www.facebook.com/icannatlarge> atlarge <https://www.facebook.com/icannatlarge>
Twitter: @ <https://twitter.com/ICANNAtLarge>ICANNAtLarge <https://twitter.com/ICANNAtLarge>
<At-Large Consolidated Policy Working Group (CPWG) Call[2].ics> _______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing listCPWG@icann.orghttps://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
-- Olivier MJ Crépin-Leblond, PhDhttp://www.gih.com/ocl.html
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
_______________________________________________ CPWG mailing list CPWG@icann.org https://mm.icann.org/mailman/listinfo/cpwg
_______________________________________________ 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.
participants (9)
-
David Mackey -
gopal＠annauniv.edu -
ICANN At-Large Staff -
John McCormac -
Judith Hellerstein -
lists＠christopherwilkinson.eu -
Olivier MJ Crépin-Leblond -
Ricardo Holmquist -
sivasubramanian muthusamy