<?xml version='1.0' encoding='utf-8'?>
<!-- This template is for creating an Internet Draft using xml2rfc,
    which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<!-- used by XSLT processors -->
<!-- For a complete list and description of processing instructions (PIs),
    please see http://xml.resource.org/authoring/README.html. -->
<rfc
      xmlns:xi="http://www.w3.org/2001/XInclude"
      category="info"
      docName="draft-feamster-livingood-iab-covid19-workshop-00"
      ipr="trust200902"
      obsoletes=""
      updates=""
      submissionType="IAB"
      xml:lang="en"
      tocInclude="true"
      tocDepth="4"
      symRefs="true"
      sortRefs="true"
      version="3">
  <!-- xml2rfc v2v3 conversion 2.38.1 -->
  <!-- category values: std, bcp, info, exp, and historic
    ipr values: trust200902, noModificationTrust200902, noDerivativesTrust200902,
       or pre5378Trust200902
    you can add the attributes updates="NNNN" and obsoletes="NNNN"
    they will automatically be output with "(if approved)" -->

 <!-- ***** FRONT MATTER ***** -->

 <front>
    <!-- The abbreviated title is used in the page header - it is only necessary if the
        full title is longer than 39 characters -->

   <title abbrev="COVID-19 Interconnection Traffic Effects">IAB COVID-19 Workshop: Interconnection Changes in the United States</title>
    <seriesInfo name="Internet-Draft" value="draft-feamster-livingood-iab-covid19-workshop-00"/>
    <!-- add 'role="editor"' below for the editors if appropriate -->

   <!-- Another author who claims to be an editor -->
	 
   <author fullname="Francesco Bronzino" initials="F." surname="Bronzino">
      <organization>Universite Savoie Mont Blanc</organization>
      <address>
        <postal>
         <city>Annecy-le-Vieux</city>
          <country>France</country>
        </postal>
        <email>francesco.bronzino@univ-smb.fr</email>
     </address>
    </author>

    <author fullname="Elizabeth Culley" initials="E" surname="Culley">
       <organization>Comcast</organization>
       <address>
         <postal>
          <city>Mount Laurel</city>
           <region>NJ</region>
           <country>USA</country>
         </postal>
         <email>elizabeth_culley@comcast.com</email>
      </address>
     </author>	 

   <author fullname="Nick Feamster" initials="N." surname="Feamster">
      <organization>University of Chicago</organization>
      <address>
          <postal>
         <city>Chicago</city>
          <region>IL</region>
          <country>USA</country>
        </postal>
        <email>feamster@uchicago.edu</email>
     </address>
    </author>

   <author fullname="Shinan Liu" initials="S." surname="Liu">
      <organization>University of Chicago</organization>
      <address>
          <postal>
         <city>Chicago</city>
          <region>IL</region>
          <country>USA</country>
        </postal>
        <email>shinanliu@uchicago.edu</email>
     </address>
    </author>
	 
     <author fullname="Jason Livingood" initials="J" surname="Livingood">
       <organization>Comcast</organization>
       <address>
         <postal>
          <city>Philadelphia</city>
           <region>PA</region>
           <country>USA</country>
         </postal>
         <email>jason_livingood@comcast.com</email>
      </address>
     </author>

  <author fullname="Paul Schmitt" initials="P." surname="Schmitt">
      <organization>Princeton University</organization>
      <address>
        <postal>
         <city>Princeton</city>
          <region>NJ</region>
          <country>USA</country>
        </postal>
        <email>pschmitt@cs.princeton.edu</email>
     </address>
    </author>
	 
    <date year="2020"/>
    <!-- If the month and year are both specified and are the current ones, xml2rfc will fill
        in the current day for you. If only the current year is specified, xml2rfc will fill
	 in the current day and month for you. If the year is not the current one, it is
	 necessary to specify at least a month (xml2rfc assumes day="1" if not specified for the
	 purpose of calculating the expiry date).  With drafts it is normally sufficient to
	 specify just the year. -->

   <!-- Meta-data Declarations -->

   <area>General</area>
    <workgroup>Internet Architecture Board</workgroup>
    <!-- WG name at the upperleft corner of the doc,
        IETF is fine for individual submissions.
	 If this element is not present, the default is "Network Working Group",
        which is used by the RFC Editor as a nod to the history of the IETF. -->

   <keyword>COVID, COVID-19, Coronavirus, Pandemic</keyword>
    <!-- Keywords will be incorporated into HTML output
        files in a meta tag but they have no effect on text or nroff
        output. If you submit your draft to the RFC Editor, the
        keywords will be used for the search engine. -->

   <abstract>
      <t>During the early weeks and months of the COVID-19 pandemic, significant changes to Internet usage occurred as a result of a sudden 
	   global shift to people working, studying and quarantining at home. One aspect that this affected was interconnection between 
        networks, which this paper studies. This paper explores some of the effects of these changes on Internet interconnection points, in terms of utilization, traffic ratios, and other performance characteristics such as latency.  </t>
    </abstract>
</front>
<middle>
    <!-- This PI places the pagebreak correctly (before the section title) in the text output. -->

    <section numbered="true" toc="default">
      <name>Introduction</name>
      
         <t>
            During the early weeks and months of the COVID-19 pandemic <xref target="WHO-Declaration" />, significant changes to Internet usage occurred as a result of a sudden global shift to people working, studying and quarantining at home. One aspect that this affected
                was interconnection between networks, which this paper studies.
            </t>
                
            <t>
                In 2016, the Interconnection Measurement Project
            <xref target="Tinker-Blog" />
            was launched. The IMP platform initially collected interconnection-related data from seven U.S.-based cable-based Internet Service Providers (ISPs) and an <xref target="ArXiv-Paper" /> shared some of the details and findings. The initial focus of the project was to explore utilization characteristics of interconnect links during a period of time when video traffic was steadily increasing. The project concluded that there was ample aggregate capacity on interconnect links between ISPs and peers (including content providers), and that ISPs continually added capacity to their interconnects to keep pace with the growth in traffic.
            </t> 
            
            <t>
            This IAB paper looks specifically at the long-term interconnection data from one of those ISPs, Comcast. We examine the long-term pre-COVID-19 trend as well as what occurred as COVID-19 impacted the Internet from February 2020 through August 2020. We also include observations from Comcast concerning interconnection changes during this timeframe.
            </t>
            <t>
                We hope that this information will be useful to the IAB workshop and the Internet community more broadly. It may serve as an interesting and useful historical reference in the future.
            </t>
    </section>
	  
    <section numbered="true" toc="default">
      <name>Long-Term Interconnection Data</name>

            <t>The IMP platform collected interconnection data starting in 2016, roughly four years prior to the COVID-19-driven shift in 
	    Internet usage. This provides an interesting capability for a before and after view of interconnection. A full explanation 
		    of the data can be found in Section 3 of the <xref target="ArXiv-Paper" />. At a high level, the maindata collected 
		    encompasses:</t>
		    <ul>
			    <li>Timestamp (representing a five-minute interval)</li>
			    <li>Region (representing an aggregated link group)</li>
			    <li>Anonymized partner network</li>
			    <li>Access ISP</li>
			    <li>Total ingress bytes</li>
			    <li>Total egress bytes</li>
			    <li>Capacity</li>
		    </ul>
            
            <t>Utilization is captured based on sampled IPFIX records, with a packet sampling rate of 1/1,000. SNMP polling data yields information about the capacity on each link. The IMP platform does not have direct access to partner network identities---this dataset only includes an anonymous identifier corresponding to that particular partner. However, in collaboration with Comcast, IMP has worked to identify specific partner networks in the dataset for specific peers in the interest of detail COVID-19-related study.</t>
	    
            <t>Focusing on Comcast within this dataset reveals several trends, in both aggregate capacity and utilization, as well as how utilization and capacity changed during the period of the COVID-19 pandemic. The data also reveals how traffic volumes changed for specific peers during this time period.</t>

            <t>The IMP data that tracks capacity shows Comcast steadily adding capacity from mid-2018 to present, with a significant increase in the rate of additional capacity from the beginning of 2020, increasing further in the second and third quarters of 2020. Specifically, we analyzed the rate at which capacity was added during these periods, on a month-by-month basis. We found that Comcast was adding aggregate capacity on its interconnects at *nearly twice* the rate as it was being added during 2019.</t>

            <t>Over a long timeframe, Comcast's daily peak hour interconnection port utilization has remained consistently around 90%. During the period at the end of March and the beginning of April 2020, daily peak utilization briefly increased to about 97% but steadily returned to normal levels in a matter of weeks by the end of April 2020, as Comcast quickly increased the rate at which it added capacity to keep pace with growing traffic demands.</t>
                
            <t>We also explored traffic volumes associated with each Comcast peer, comparing the ranks and volumes of each individual peer as measured on September 1, 2020 as compared to January 1, 2020, in both the upstream and downstream directions. Doing so allowed us to understand both the magnitude of changes in traffic volumes and ratios, as well as how specific individual peers deviated from normal baseline behavior, in terms of both upstream and downstream traffic rates and ratios. The data suggests that both the upstream and downstream directions saw some changes, although the deviations in upstream traffic patterns were greater: the Pearson coefficient for downstream traffic was 0.977, whereas for upstream traffic the Pearson correlation coefficient was only 0.935, indicating a more significant shift in upstream traffic ratios during this timeframe.</t>
                
    </section>
	  
    <section numbered="true" toc="default">
      <name>Comcast's COVID-19-Related Experiences</name>

            <t>Comcast observed a wide range of significant changes in Internet usage as residential users remained at home and 
	    shifted to working and studying from home. Changes in usage patterns observed in the access network in sum led to 
	    changes in the traffic flowing to interconnected networks. As the pandemic developed, there was a wide variety of changes in traffic volumes.  
	    At some locations in the network little change was detected while other locations saw a huge growth in the volume of traffic.</t>
	    
	    <t>At the peak of the surge, in March and April 2020, the average amount of growth observed across locations and types was 
		    roughly 33%. Voice &amp; video conferencing (conferencing hereafter) jumped as much as 
		    285% and Wi-Fi use increased 36% among our Xfinity Mobile (MVNO) customers 
		    <xref target="June-Blog" /> <xref target="July-Blog" />. As this continued 
		    into May 2020 we observed conferencing remained up roughly 210-285%, VPN traffic up 30-40% and gaming downloads 
		    up 20-80%, and web-based streaming video consumption up 20-40% 
		    <xref target="May-Blog" />. In this several week period, traffic essentially 
	    grew at or more than it had in the prior year, which was significant growth in a short period of time.</t>
	    
	    <t>In the months following the onset of the pandemic Comcast observed:</t>
		    <ul>
			    <li>Overall average downstream peak growth is up 13% (up as much as 20% at times).</li>
			    <li>Overall average upstream peak growth is up 36%.</li>
			    <li>In the access network, an average of 771 network augments per week were performed, peaking 
				    at over 1,800 in a single week and over with over 7 weeks with more than 1,000 per week. For 
			    comparison, the average earlier in the year was roughly 350 per week.</li>
			    <li>In the core network, over 500 augments were made in order to add 146 Tbps in capacity.</li>
			    <li>On a daily basis roughly 700,000 automated speed tests from customer homes were 
				    conducted in order to gauge the customer experience during this time. Average speeds 
				    to customers (both downstream and upstream) have generally 
				    remained at or above 105% of advertised speeds since March 1, 2020 in all regions. 
				    National average speeds have remained between 110% - 115% of advertised speeds over the same period. 
				    <xref target="NF-Paper-1" /> and <xref target="NF-Paper-2" /></li>
			    <li>The share of streaming video as a percentage of total traffic is declined slightly from 67% to 63%. 
				    Despite strong growth, conferencing occupies a small share of total traffic and grew from 1% share 
				    to 4%. But gaming software released have driven significant download spikes since late April 2020.</li>
			    <li>For interconnection, peering coordinators across operators worked cooperatively and quickly to cut through any red tape and add new capacity as quickly as possible.</li>
				<li>In 2019, settlement free interconnection capacity <xref target='SFI-Policy' /> - a subset of overall interconnect types - grew by 15%. Between January and August 2020, driven by COVID-19 changes, there was an overall 37% increase in capacity from that prior 2019 level. And between March and October 2020 one Settlement Free Peer alone increased 115%.</li>
				<li>Between March and October 2020 from Comcast observed other notable per-peer traffic increases of 245% and 3,900%.</li>
		    </ul>
	    
    </section>
	  
   <section numbered="true" toc="default">
      <name>Detailed Statistical Observations</name>

      <t>As briefly mentioned in previous sections, downstream traffic rates from many partners remained stable---the Pearson correlation coefficient for peak download rates between January 1, 2020 and September 2, 2020 is 0.977, indicating that the peak download rates to most peers was similar between these two time periods. On the other hand, certain peers experienced either a significant increase or decrease in peak download rates---often by two or three orders of magnitude. Similarly, other peers experienced a decrease in peak downstream rates by several orders of magnitude.</t>

  <t>On the other hand, upstream traffic rates were far less stable: In contrast, the Pearson coefficient for upload rates between January 1, 2020 and September 2, 2020 was only 0.935, suggesting more a more significant deviation in peak upstream rates. As with peak download rates, some peers experienced significant decreases, as well: in one outlier case, peak rate decreased by almost five orders of magnitude. A small handful of peers saw similar decreases. Yet, a far greater number of peers saw increases in peak upload rates by two to three orders of magnitude.</t>
	
	    
    </section>
	

   <section anchor="IANA" numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>This document includes no request to IANA.</t>
    </section>
    
    <section anchor="Security" numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>This document includes no security considerations.</t>
    </section>
  </middle>
  <!--  *****BACK MATTER ***** -->

 <back>

    <references title="Normative References">

   </references>

   <references title="Informative References">
   
   		<reference anchor="WHO-Declaration" target="https://www.who.int/dg/speeches/detail/who-director-general-s-opening-remarks-at-the-media-briefing-on-covid-19---11-march-2020">
   			<front>
   			<title>WHO Director-General's opening remarks at the media briefing on COVID-19 - 11 March 2020</title>
   			<author initials="TAG" surname="Adhanom Ghebreyesus" fullname="Dr. Tedros Adhanom Ghebreyesus">
				<organization>World Health Organization</organization>
   			</author>
   			<date day="11" month="March" year="2020"/>
   			</front>
   		</reference>
	   
	   	<reference anchor="Tinker-Blog" target="https://freedom-to-tinker.com/2016/05/09/the-interconnection-measurement-project/">
   			<front>
   			<title>Interconnection Measurement Project Website</title>
   			<author initials="NF" surname="Feamster" fullname="Nick Feamster">
   			</author>
   			<date day="9" month="May" year="2016"/>
   			</front>
   		</reference>
   		
   		<reference anchor="ArXiv-Paper" target="https://arxiv.org/pdf/1603.03656.pdf">
   			<front>
   			<title>Revealing Utilization at Internet Interconnection Points</title>
   			<author initials="NF" surname="Feamster" fullname="Nick Feamster">
   				<organization>Princeton University</organization>
   			</author>
   			<date day="5" month="September" year="2016"/>
   			</front>
   		</reference>
   		
   		<reference anchor="May-Blog" target="https://corporate.comcast.com/covid-19/network/may-20-2020">
   			<front>
   			<title>COVID-19 Network Update</title>
   			<author>
   				<organization>Comcast</organization>
   			</author>
   			<date day="20" month="May" year="2020"/>
   			</front>
   		</reference>
   		
   		<reference anchor="June-Blog" target="https://corporate.comcast.com/press/releases/cresting-the-wave-how-our-network-thrived-what-comes-next">
   			<front>
   			<title>Cresting the Wave: The Factors that Powered our Network Through the COVID-19 Surge</title>
   			<author initials="TW" surname="Werner" fullname="Tony Werner">
   				<organization>Comcast</organization>
   			</author>
   			<date day="15" month="June" year="2020"/>
   			</front>
   		</reference>
   		
   		<reference anchor="July-Blog" target="https://corporate.comcast.com/stories/covid-19-network-report-smart-network-speed-and-stability">
   			<front>
   			<title>COVID-19 Network Report: How A Smart Network Delivered Speed and Stability When it Mattered</title>
   			<author initials="EN" surname="Nafshi" fullname="Elad Nafshi">
   				<organization>Comcast</organization>
   			</author>
   			<date day="13" month="July" year="2020"/>
   			</front>
   		</reference>
   		
   		<reference anchor="NF-Paper-1" target="https://www.netforecast.com/netforecast-design-audit-report-of-comcasts-network-performance-measurement-system/">
   			<front>
   			<title>NetForecast Design Audit Report of Comcast's Network Performance Measurement System</title>
   			<author initials="AJ" surname="Jones" fullname="Alan Jones">
                <organization>NetForecast</organization>
   			</author>
   			<author initials="PS" surname="Sevcik" fullname="Peter Sevcik">
   				<organization>NetForecast</organization>
   			</author>
   			<author initials="AL" surname="Lacy" fullname="Andrew Lacy">
   				<organization>NetForecast</organization>
   			</author>	
   			<date month="April" year="2020"/>
   			</front>
   		</reference>
   		
   		<reference anchor="NF-Paper-2" target="https://www.netforecast.com/netforecasts-report-on-comcasts-network-performance-measurement-system-results-data/">
   			<front>
   			<title>NetForecast's Report on Comcast's Network Performance Measurement System Results Data</title>
   			<author initials="AJ" surname="Jones" fullname="Alan Jones">
                <organization>NetForecast</organization>
   			</author>
   			<author initials="PS" surname="Sevcik" fullname="Peter Sevcik">
   				<organization>NetForecast</organization>
   			</author>
   			<author initials="AL" surname="Lacy" fullname="Andrew Lacy">
   				<organization>NetForecast</organization>
   			</author>	
   			<date month="May" year="2020"/>
   			</front>
   		</reference>
	   
	   	<reference anchor="SFI-Policy" target="https://www.xfinity.com/peering/">
   			<front>
   			<title>Comcast Settlement-Free Interconnection (SFI) Policy</title>
   			<author>
                <organization>Comcast Cable Communications Management, LLC</organization>
   			</author>
   			<date month="October" year="2013"/>
   			</front>
	   	</reference>
	   
   		
   </references>

 </back>
</rfc>
