<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Times New Roman \(Body CS\)";
panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">In many ways I see this similarly to the consolidation of browsers, but less consolidated. I think about the advantages and disadvantages of the prominence of Chrome (65%),
Safari (20%), Firefox/Samsung/Edge/Opera/etc (15%). With Chrome we�ve seen Google move the browser and related standards forward through sheer marketshare. CSS/HTML/JS standards live and die by Chrome support and that�s both good and bad. They have made great
and opinionated strides when it comes to SSL/TLS. For example, Google effectively killed Symantec�s certificate business because it was mismanaged. They also effectively got rid of EV certs and pushed secure-by-default web server design where HTTPS appeared
normal, but warnings all over the place for non-encrypted connections. On the other hand, Google is fairly disliked in the privacy community and those communities prefer independent Firefox.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif">For email, I can see similar issues, mostly around security. If Microsoft were to decide security mechanism X is not worth the effort they can effectively decide to not implement
it. What will internet users do, block all Microsoft email services? Conversely they could come up with their own security mechanisms and effectively force the rest of the world to adopt it. I do think centralization of email providers provides little potential
for negative impact aside from operational issues. For example, outages probably have a wider impact due to number of users, but I can�t realistically see a scenario where Microsoft/Google does something �bad� with their email platform that affects the rest
of the ecosystem.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:black">Caesar Kabalan</span><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">NANOG <nanog-bounces+ckabalan=wlgore.com@nanog.org><br>
<b>Date: </b>Tuesday, September 8, 2020 at 4:47 AM<br>
<b>To: </b>Mike Hammett <nanog@ics-il.net>, NANOG <nanog@nanog.org><br>
<b>Subject: </b>Re: Consolidation of Email Platforms Bad for Email?<o:p></o:p></span></p>
</div>
<p>I'm sure Dave Crocker has thoughts about this, but it has come up elsewhere. There are both positives and negatives about having such a consolidation. The positive is that it a small club can establish ground rules for how they will handle various forms
of attacks, including BGP hijacking, DKIM, SPF, and other forms of validation to identify fraudulent mail, etc. Also, if you have a whole lot of postfixes and sendmails running around, that's a whole lot of code to patch when things go wrong. A small number
of MSPs can devote a lot of time and paid eyes on code. They can also very quickly spot new attack trends.</p>
<p><o:p> </o:p></p>
<p>On the other hand, that means that it becomes difficult to become a new entrant, because one doesn't easily get one's mail accepted. Lots of grey/blacklisting (forgive the use of the term). Also, when one of those systems fails, it takes down a vast number
of customers. Furthermore, it represents a <b>massive</b> concentration of private information that can be monetized.</p>
<p><o:p> </o:p></p>
<p>Eliot</p>
<p><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 08.09.20 00:27, Mike Hammett via NANOG wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">I originally asked on mailops, but here is a much wider net and I suspect there's a lot of overlap in interest.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">I had read an article one time, somewhere about the ongoing consolidation of e-mail into a handful of providers was bad for the Internet as a whole. It was some time
ago and thus, the details have escaped me, so I was looking to refresh my recollection.
<o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black">Have any of you read a similar article before? If so, can you link me to it?<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
<br>
-----<br>
Mike Hammett<br>
Intelligent Computing Solutions<br>
</span><a href="http://www.ics-il.com"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.ics-il.com</span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><br>
<br>
Midwest-IX<br>
</span><a href="http://www.midwest-ix.com"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">http://www.midwest-ix.com</span></a><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black"><o:p> </o:p></span></p>
</div>
</blockquote>
</div>
<img src="https://www.gore.com/sites/g/files/ypyipe116/files/2017-03/Gore_logo_0.png" ;alt="logo">
<DIV>
This email may contain trade secrets or privileged, undisclosed or otherwise confidential information. If you have received this email in error, you are hereby notified that any review, copying or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.<BR>
</DIV></body>
</html>