[CPWG] REMINDER | Meeting invitation: At-Large Consolidated Policy Working Group (CPWG) Call on Wednesday, 06 October 2021 at 13:00 UTC

[David Mackey]

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-whatsapp-and-oculus-are-down-heres-what-we-know/>
-
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 at 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 at icann.org>
> wrote:
>
> ****If you require a dial out or need to state an apology, please contact
> At-Large staff at staff at atlarge.icann.org <staff at 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 at 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 at 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 at 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 at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/cpwg/attachments/20211005/c2ab0032/attachment-0001.html>