File: rfc9075.html

package info (click to toggle)
doc-rfc 20230121-1
links: PTS, VCS
area: non-free
in suites: bookworm, forky, sid, trixie
size: 1,609,944 kB
file content (2403 lines) | stat: -rw-r--r-- 120,581 bytes
<!DOCTYPE html>
<html lang="en" class="RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 9075: Report from the IAB COVID-19 Network Impacts Workshop 2020</title>
<meta content="Jari Arkko" name="author">
<meta content="Stephen Farrell" name="author">
<meta content="Mirja Kühlewind" name="author">
<meta content="Colin Perkins" name="author">
<meta content="
       The Coronavirus disease (COVID-19) pandemic caused changes in Internet user behavior,
particularly during the introduction of initial quarantine and
work-from-home arrangements. These behavior changes drove changes
in Internet traffic. 
       The Internet Architecture Board (IAB) held a workshop to discuss network
impacts of the pandemic on November 9-13, 2020. The workshop was held
to convene interested researchers, network operators, network
management experts, and Internet technologists to share their
experiences. The meeting was held online given the ongoing travel and
contact restrictions at that time. 
       Note that this document is a report on the proceedings of the 
workshop.  The views and positions documented in this report are 
those of the workshop participants and do not necessarily reflect IAB 
views and positions. 
    " name="description">
<meta content="xml2rfc 3.9.1" name="generator">
<meta content="9075" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.9.1
    Python 3.6.10
    appdirs 1.4.4
    ConfigArgParse 1.2.3
    google-i18n-address 2.3.5
    html5lib 1.0.1
    intervaltree 3.0.2
    Jinja2 2.11.2
    kitchen 1.2.6
    lxml 4.4.2
    pycairo 1.19.0
    pycountry 19.8.18
    pyflakes 2.1.1
    PyYAML 5.3.1
    requests 2.22.0
    setuptools 40.6.2
    six 1.14.0
    WeasyPrint 51
-->
<link href="rfc9075.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*

  NOTE: Changes at the bottom of this file overrides some earlier settings.

  Once the style has stabilized and has been adopted as an official RFC style,
  this can be consolidated so that style settings occur only in one place, but
  for now the contents of this file consists first of the initial CSS work as
  provided to the RFC Formatter (xml2rfc) work, followed by itemized and
  commented changes found necssary during the development of the v3
  formatters.

*/

/* fonts */
@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */
@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */
@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */

@viewport {
  zoom: 1.0;
  width: extend-to-zoom;
}
@-ms-viewport {
  width: extend-to-zoom;
  zoom: 1.0;
}
/* general and mobile first */
html {
}
body {
  max-width: 90%;
  margin: 1.5em auto;
  color: #222;
  background-color: #fff;
  font-size: 14px;
  font-family: 'Noto Sans', Arial, Helvetica, sans-serif;
  line-height: 1.6;
  scroll-behavior: smooth;
}
.ears {
  display: none;
}

/* headings */
#title, h1, h2, h3, h4, h5, h6 {
  margin: 1em 0 0.5em;
  font-weight: bold;
  line-height: 1.3;
}
#title {
  clear: both;
  border-bottom: 1px solid #ddd;
  margin: 0 0 0.5em 0;
  padding: 1em 0 0.5em;
}
.author {
  padding-bottom: 4px;
}
h1 {
  font-size: 26px;
  margin: 1em 0;
}
h2 {
  font-size: 22px;
  margin-top: -20px;  /* provide offset for in-page anchors */
  padding-top: 33px;
}
h3 {
  font-size: 18px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h4 {
  font-size: 16px;
  margin-top: -36px;  /* provide offset for in-page anchors */
  padding-top: 42px;
}
h5, h6 {
  font-size: 14px;
}
#n-copyright-notice {
  border-bottom: 1px solid #ddd;
  padding-bottom: 1em;
  margin-bottom: 1em;
}
/* general structure */
p {
  padding: 0;
  margin: 0 0 1em 0;
  text-align: left;
}
div, span {
  position: relative;
}
div {
  margin: 0;
}
.alignRight.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignRight.art-text pre {
  padding: 0;
}
.alignRight {
  margin: 1em 0;
}
.alignRight > *:first-child {
  border: none;
  margin: 0;
  float: right;
  clear: both;
}
.alignRight > *:nth-child(2) {
  clear: both;
  display: block;
  border: none;
}
svg {
  display: block;
}
.alignCenter.art-text {
  background-color: #f9f9f9;
  border: 1px solid #eee;
  border-radius: 3px;
  padding: 1em 1em 0;
  margin-bottom: 1.5em;
}
.alignCenter.art-text pre {
  padding: 0;
}
.alignCenter {
  margin: 1em 0;
}
.alignCenter > *:first-child {
  border: none;
  /* this isn't optimal, but it's an existence proof.  PrinceXML doesn't
     support flexbox yet.
  */
  display: table;
  margin: 0 auto;
}

/* lists */
ol, ul {
  padding: 0;
  margin: 0 0 1em 2em;
}
ol ol, ul ul, ol ul, ul ol {
  margin-left: 1em;
}
li {
  margin: 0 0 0.25em 0;
}
.ulCompact li {
  margin: 0;
}
ul.empty, .ulEmpty {
  list-style-type: none;
}
ul.empty li, .ulEmpty li {
  margin-top: 0.5em;
}
ul.ulBare, li.ulBare {
  margin-left: 0em !important;
}
ul.compact, .ulCompact,
ol.compact, .olCompact {
  line-height: 100%;
  margin: 0 0 0 2em;
}

/* definition lists */
dl {
}
dl > dt {
  float: left;
  margin-right: 1em;
}
/* 
dl.nohang > dt {
  float: none;
}
*/
dl > dd {
  margin-bottom: .8em;
  min-height: 1.3em;
}
dl.compact > dd, .dlCompact > dd {
  margin-bottom: 0em;
}
dl > dd > dl {
  margin-top: 0.5em;
  margin-bottom: 0em;
}

/* links */
a {
  text-decoration: none;
}
a[href] {
  color: #22e; /* Arlen: WCAG 2019 */
}
a[href]:hover {
  background-color: #f2f2f2;
}
figcaption a[href],
a[href].selfRef {
  color: #222;
}
/* XXX probably not this:
a.selfRef:hover {
  background-color: transparent;
  cursor: default;
} */

/* Figures */
tt, code, pre, code {
  background-color: #f9f9f9;
  font-family: 'Roboto Mono', monospace;
}
pre {
  border: 1px solid #eee;
  margin: 0;
  padding: 1em;
}
img {
  max-width: 100%;
}
figure {
  margin: 0;
}
figure blockquote {
  margin: 0.8em 0.4em 0.4em;
}
figcaption {
  font-style: italic;
  margin: 0 0 1em 0;
}
@media screen {
  pre {
    overflow-x: auto;
    max-width: 100%;
    max-width: calc(100% - 22px);
  }
}

/* aside, blockquote */
aside, blockquote {
  margin-left: 0;
  padding: 1.2em 2em;
}
blockquote {
  background-color: #f9f9f9;
  color: #111; /* Arlen: WCAG 2019 */
  border: 1px solid #ddd;
  border-radius: 3px;
  margin: 1em 0;
}
cite {
  display: block;
  text-align: right;
  font-style: italic;
}

/* tables */
table {
  width: 100%;
  margin: 0 0 1em;
  border-collapse: collapse;
  border: 1px solid #eee;
}
th, td {
  text-align: left;
  vertical-align: top;
  padding: 0.5em 0.75em;
}
th {
  text-align: left;
  background-color: #e9e9e9;
}
tr:nth-child(2n+1) > td {
  background-color: #f5f5f5;
}
table caption {
  font-style: italic;
  margin: 0;
  padding: 0;
  text-align: left;
}
table p {
  /* XXX to avoid bottom margin on table row signifiers. If paragraphs should
     be allowed within tables more generally, it would be far better to select on a class. */
  margin: 0;
}

/* pilcrow */
a.pilcrow {
  color: #666; /* Arlen: AHDJ 2019 */
  text-decoration: none;
  visibility: hidden;
  user-select: none;
  -ms-user-select: none;
  -o-user-select:none;
  -moz-user-select: none;
  -khtml-user-select: none;
  -webkit-user-select: none;
  -webkit-touch-callout: none;
}
@media screen {
  aside:hover > a.pilcrow,
  p:hover > a.pilcrow,
  blockquote:hover > a.pilcrow,
  div:hover > a.pilcrow,
  li:hover > a.pilcrow,
  pre:hover > a.pilcrow {
    visibility: visible;
  }
  a.pilcrow:hover {
    background-color: transparent;
  }
}

/* misc */
hr {
  border: 0;
  border-top: 1px solid #eee;
}
.bcp14 {
  font-variant: small-caps;
}

.role {
  font-variant: all-small-caps;
}

/* info block */
#identifiers {
  margin: 0;
  font-size: 0.9em;
}
#identifiers dt {
  width: 3em;
  clear: left;
}
#identifiers dd {
  float: left;
  margin-bottom: 0;
}
#identifiers .authors .author {
  display: inline-block;
  margin-right: 1.5em;
}
#identifiers .authors .org {
  font-style: italic;
}

/* The prepared/rendered info at the very bottom of the page */
.docInfo {
  color: #666; /* Arlen: WCAG 2019 */
  font-size: 0.9em;
  font-style: italic;
  margin-top: 2em;
}
.docInfo .prepared {
  float: left;
}
.docInfo .prepared {
  float: right;
}

/* table of contents */
#toc  {
  padding: 0.75em 0 2em 0;
  margin-bottom: 1em;
}
nav.toc ul {
  margin: 0 0.5em 0 0;
  padding: 0;
  list-style: none;
}
nav.toc li {
  line-height: 1.3em;
  margin: 0.75em 0;
  padding-left: 1.2em;
  text-indent: -1.2em;
}
/* references */
.references dt {
  text-align: right;
  font-weight: bold;
  min-width: 7em;
}
.references dd {
  margin-left: 8em;
  overflow: auto;
}

.refInstance {
  margin-bottom: 1.25em;
}

.references .ascii {
  margin-bottom: 0.25em;
}

/* index */
.index ul {
  margin: 0 0 0 1em;
  padding: 0;
  list-style: none;
}
.index ul ul {
  margin: 0;
}
.index li {
  margin: 0;
  text-indent: -2em;
  padding-left: 2em;
  padding-bottom: 5px;
}
.indexIndex {
  margin: 0.5em 0 1em;
}
.index a {
  font-weight: 700;
}
/* make the index two-column on all but the smallest screens */
@media (min-width: 600px) {
  .index ul {
    -moz-column-count: 2;
    -moz-column-gap: 20px;
  }
  .index ul ul {
    -moz-column-count: 1;
    -moz-column-gap: 0;
  }
}

/* authors */
address.vcard {
  font-style: normal;
  margin: 1em 0;
}

address.vcard .nameRole {
  font-weight: 700;
  margin-left: 0;
}
address.vcard .label {
  font-family: "Noto Sans",Arial,Helvetica,sans-serif;
  margin: 0.5em 0;
}
address.vcard .type {
  display: none;
}
.alternative-contact {
  margin: 1.5em 0 1em;
}
hr.addr {
  border-top: 1px dashed;
  margin: 0;
  color: #ddd;
  max-width: calc(100% - 16px);
}

/* temporary notes */
.rfcEditorRemove::before {
  position: absolute;
  top: 0.2em;
  right: 0.2em;
  padding: 0.2em;
  content: "The RFC Editor will remove this note";
  color: #9e2a00; /* Arlen: WCAG 2019 */
  background-color: #ffd; /* Arlen: WCAG 2019 */
}
.rfcEditorRemove {
  position: relative;
  padding-top: 1.8em;
  background-color: #ffd; /* Arlen: WCAG 2019 */
  border-radius: 3px;
}
.cref {
  background-color: #ffd; /* Arlen: WCAG 2019 */
  padding: 2px 4px;
}
.crefSource {
  font-style: italic;
}
/* alternative layout for smaller screens */
@media screen and (max-width: 1023px) {
  body {
    padding-top: 2em;
  }
  #title {
    padding: 1em 0;
  }
  h1 {
    font-size: 24px;
  }
  h2 {
    font-size: 20px;
    margin-top: -18px;  /* provide offset for in-page anchors */
    padding-top: 38px;
  }
  #identifiers dd {
    max-width: 60%;
  }
  #toc {
    position: fixed;
    z-index: 2;
    top: 0;
    right: 0;
    padding: 0;
    margin: 0;
    background-color: inherit;
    border-bottom: 1px solid #ccc;
  }
  #toc h2 {
    margin: -1px 0 0 0;
    padding: 4px 0 4px 6px;
    padding-right: 1em;
    min-width: 190px;
    font-size: 1.1em;
    text-align: right;
    background-color: #444;
    color: white;
    cursor: pointer;
  }
  #toc h2::before { /* css hamburger */
    float: right;
    position: relative;
    width: 1em;
    height: 1px;
    left: -164px;
    margin: 6px 0 0 0;
    background: white none repeat scroll 0 0;
    box-shadow: 0 4px 0 0 white, 0 8px 0 0 white;
    content: "";
  }
  #toc nav {
    display: none;
    padding: 0.5em 1em 1em;
    overflow: auto;
    height: calc(100vh - 48px);
    border-left: 1px solid #ddd;
  }
}

/* alternative layout for wide screens */
@media screen and (min-width: 1024px) {
  body {
    max-width: 724px;
    margin: 42px auto;
    padding-left: 1.5em;
    padding-right: 29em;
  }
  #toc {
    position: fixed;
    top: 42px;
    right: 42px;
    width: 25%;
    margin: 0;
    padding: 0 1em;
    z-index: 1;
  }
  #toc h2 {
    border-top: none;
    border-bottom: 1px solid #ddd;
    font-size: 1em;
    font-weight: normal;
    margin: 0;
    padding: 0.25em 1em 1em 0;
  }
  #toc nav {
    display: block;
    height: calc(90vh - 84px);
    bottom: 0;
    padding: 0.5em 0 0;
    overflow: auto;
  }
  img { /* future proofing */
    max-width: 100%;
    height: auto;
  }
}

/* pagination */
@media print {
  body {

    width: 100%;
  }
  p {
    orphans: 3;
    widows: 3;
  }
  #n-copyright-notice {
    border-bottom: none;
  }
  #toc, #n-introduction {
    page-break-before: always;
  }
  #toc {
    border-top: none;
    padding-top: 0;
  }
  figure, pre {
    page-break-inside: avoid;
  }
  figure {
    overflow: scroll;
  }
  h1, h2, h3, h4, h5, h6 {
    page-break-after: avoid;
  }
  h2+*, h3+*, h4+*, h5+*, h6+* {
    page-break-before: avoid;
  }
  pre {
    white-space: pre-wrap;
    word-wrap: break-word;
    font-size: 10pt;
  }
  table {
    border: 1px solid #ddd;
  }
  td {
    border-top: 1px solid #ddd;
  }
}

/* This is commented out here, as the string-set: doesn't
   pass W3C validation currently */
/*
.ears thead .left {
  string-set: ears-top-left content();
}

.ears thead .center {
  string-set: ears-top-center content();
}

.ears thead .right {
  string-set: ears-top-right content();
}

.ears tfoot .left {
  string-set: ears-bottom-left content();
}

.ears tfoot .center {
  string-set: ears-bottom-center content();
}

.ears tfoot .right {
  string-set: ears-bottom-right content();
}
*/

@page :first {
  padding-top: 0;
  @top-left {
    content: normal;
    border: none;
  }
  @top-center {
    content: normal;
    border: none;
  }
  @top-right {
    content: normal;
    border: none;
  }
}

@page {
  size: A4;
  margin-bottom: 45mm;
  padding-top: 20px;
  /* The follwing is commented out here, but set appropriately by in code, as
     the content depends on the document */
  /*
  @top-left {
    content: 'Internet-Draft';
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-left {
    content: string(ears-top-left);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-center {
    content: string(ears-top-center);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @top-right {
    content: string(ears-top-right);
    vertical-align: bottom;
    border-bottom: solid 1px #ccc;
  }
  @bottom-left {
    content: string(ears-bottom-left);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-center {
    content: string(ears-bottom-center);
    vertical-align: top;
    border-top: solid 1px #ccc;
  }
  @bottom-right {
      content: '[Page ' counter(page) ']';
      vertical-align: top;
      border-top: solid 1px #ccc;
  }
  */

}

/* Changes introduced to fix issues found during implementation */
/* Make sure links are clickable even if overlapped by following H* */
a {
  z-index: 2;
}
/* Separate body from document info even without intervening H1 */
section {
  clear: both;
}


/* Top align author divs, to avoid names without organization dropping level with org names */
.author {
  vertical-align: top;
}

/* Leave room in document info to show Internet-Draft on one line */
#identifiers dt {
  width: 8em;
}

/* Don't waste quite as much whitespace between label and value in doc info */
#identifiers dd {
  margin-left: 1em;
}

/* Give floating toc a background color (needed when it's a div inside section */
#toc {
  background-color: white;
}

/* Make the collapsed ToC header render white on gray also when it's a link */
@media screen and (max-width: 1023px) {
  #toc h2 a,
  #toc h2 a:link,
  #toc h2 a:focus,
  #toc h2 a:hover,
  #toc a.toplink,
  #toc a.toplink:hover {
    color: white;
    background-color: #444;
    text-decoration: none;
  }
}

/* Give the bottom of the ToC some whitespace */
@media screen and (min-width: 1024px) {
  #toc {
    padding: 0 0 1em 1em;
  }
}

/* Style section numbers with more space between number and title */
.section-number {
  padding-right: 0.5em;
}

/* prevent monospace from becoming overly large */
tt, code, pre, code {
  font-size: 95%;
}

/* Fix the height/width aspect for ascii art*/
pre.sourcecode,
.art-text pre {
  line-height: 1.12;
}


/* Add styling for a link in the ToC that points to the top of the document */
a.toplink {
  float: right;
  margin-right: 0.5em;
}

/* Fix the dl styling to match the RFC 7992 attributes */
dl > dt,
dl.dlParallel > dt {
  float: left;
  margin-right: 1em;
}
dl.dlNewline > dt {
  float: none;
}

/* Provide styling for table cell text alignment */
table td.text-left,
table th.text-left {
  text-align: left;
}
table td.text-center,
table th.text-center {
  text-align: center;
}
table td.text-right,
table th.text-right {
  text-align: right;
}

/* Make the alternative author contact informatio look less like just another
   author, and group it closer with the primary author contact information */
.alternative-contact {
  margin: 0.5em 0 0.25em 0;
}
address .non-ascii {
  margin: 0 0 0 2em;
}

/* With it being possible to set tables with alignment
  left, center, and right, { width: 100%; } does not make sense */
table {
  width: auto;
}

/* Avoid reference text that sits in a block with very wide left margin,
   because of a long floating dt label.*/
.references dd {
  overflow: visible;
}

/* Control caption placement */
caption {
  caption-side: bottom;
}

/* Limit the width of the author address vcard, so names in right-to-left
   script don't end up on the other side of the page. */

address.vcard {
  max-width: 30em;
  margin-right: auto;
}

/* For address alignment dependent on LTR or RTL scripts */
address div.left {
  text-align: left;
}
address div.right {
  text-align: right;
}

/* Provide table alignment support.  We can't use the alignX classes above
   since they do unwanted things with caption and other styling. */
table.right {
 margin-left: auto;
 margin-right: 0;
}
table.center {
 margin-left: auto;
 margin-right: auto;
}
table.left {
 margin-left: 0;
 margin-right: auto;
}

/* Give the table caption label the same styling as the figcaption */
caption a[href] {
  color: #222;
}

@media print {
  .toplink {
    display: none;
  }

  /* avoid overwriting the top border line with the ToC header */
  #toc {
    padding-top: 1px;
  }

  /* Avoid page breaks inside dl and author address entries */
  .vcard {
    page-break-inside: avoid;
  }

}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
  font-variant: small-caps;
  font-weight: bold;
  font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
 h2 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 31px;
 }
 h3 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
 h4 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
/* Float artwork pilcrow to the right */
@media screen {
  .artwork a.pilcrow {
    display: block;
    line-height: 0.7;
    margin-top: 0.15em;
  }
}
/* Make pilcrows on dd visible */
@media screen {
  dd:hover > a.pilcrow {
    visibility: visible;
  }
}
/* Make the placement of figcaption match that of a table's caption
   by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
   margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
  margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
   possibly even requiring a new line */
@media print {
  a.pilcrow {
    display: none;
  }
}
/* Styling for the external metadata */
div#external-metadata {
  background-color: #eee;
  padding: 0.5em;
  margin-bottom: 0.5em;
  display: none;
}
div#internal-metadata {
  padding: 0.5em;                       /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
  clear: both;
  margin: 0 0 -1em;
  padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
  margin-bottom: 0.25em;
  min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
  border-left: 1px solid #ddd;
  margin: 1em 0 1em 2em;
  padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
  margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
  figcaption, table caption {
    page-break-before: avoid;
  }
}
/* Font size adjustments for print */
@media print {
  body  { font-size: 10pt;      line-height: normal; max-width: 96%; }
  h1    { font-size: 1.72em;    padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
  h2    { font-size: 1.44em;    padding-top: 1.5em; } /* 1*1.2*1.2 */
  h3    { font-size: 1.2em;     padding-top: 1.5em; } /* 1*1.2 */
  h4    { font-size: 1em;       padding-top: 1.5em; }
  h5, h6 { font-size: 1em;      margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
  .artwork,
  .sourcecode {
    margin-bottom: 1em;
  }
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
  border: 1px solid #ddd;
}
td {
  border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
  background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
  #toc nav { display: none; }
  #toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
  break-after: avoid-page;
  break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
  break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode  {
  break-before: avoid-page;
  break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
  break-before: auto;
  break-inside: auto;
}
dt {
  break-before: auto;
  break-after: avoid-page;
}
dd {
  break-before: avoid-page;
  break-after: auto;
  orphans: 3;
  widows: 3
}
span.break, dd.break {
  margin-bottom: 0;
  min-height: 0;
  break-before: auto;
  break-inside: auto;
  break-after: auto;
}
/* Undo break-before ToC */
@media print {
  #toc {
    break-before: auto;
  }
}
/* Text in compact lists should not get extra bottim margin space,
   since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
 margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
  margin-bottom: 1em;                    /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
   backgrounds.  Changed to something a bit more selective. */
tt, code {
  background-color: transparent;
}
p tt, p code, li tt, li code {
  background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
   margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
  line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
  margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
  clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
  content: "\00a0";
}
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
li > p {
  margin-bottom: 0.5em
}
/* Don't let p margin spill out from inside list items */
li > p:last-of-type {
  margin-bottom: 0;
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc9075" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-iab-covid19-workshop-03" rel="prev">
  </head>
<body>
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
<table class="ears">
<thead><tr>
<td class="left">RFC 9075</td>
<td class="center">IAB COVID-19 Workshop 2020</td>
<td class="right">July 2021</td>
</tr></thead>
<tfoot><tr>
<td class="left">Arkko, et al.</td>
<td class="center">Informational</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-stream">Stream:</dt>
<dd class="stream">Internet Architecture Board (IAB)</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9075" class="eref">9075</a></dd>
<dt class="label-category">Category:</dt>
<dd class="category">Informational</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2021-07" class="published">July 2021</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">J. Arkko</div>
</div>
<div class="author">
      <div class="author-name">S. Farrell</div>
</div>
<div class="author">
      <div class="author-name">M. Kühlewind</div>
</div>
<div class="author">
      <div class="author-name">C. Perkins</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 9075</h1>
<h1 id="title">Report from the IAB COVID-19 Network Impacts Workshop 2020</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">The Coronavirus disease (COVID-19) pandemic caused changes in Internet user behavior,
particularly during the introduction of initial quarantine and
work-from-home arrangements. These behavior changes drove changes
in Internet traffic.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
<p id="section-abstract-2">The Internet Architecture Board (IAB) held a workshop to discuss network
impacts of the pandemic on November 9-13, 2020. The workshop was held
to convene interested researchers, network operators, network
management experts, and Internet technologists to share their
experiences. The meeting was held online given the ongoing travel and
contact restrictions at that time.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
<p id="section-abstract-3">Note that this document is a report on the proceedings of the 
workshop.  The views and positions documented in this report are 
those of the workshop participants and do not necessarily reflect IAB 
views and positions.<a href="#section-abstract-3" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This document is not an Internet Standards Track specification; it is
            published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-2">
            This document is a product of the Internet Architecture Board
            (IAB) and represents information that the IAB has deemed valuable
            to provide for permanent record.  It represents the consensus of the Internet
            Architecture Board (IAB).  Documents approved for publication
            by the IAB are not candidates for any level of Internet Standard; see
            Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <span><a href="https://www.rfc-editor.org/info/rfc9075">https://www.rfc-editor.org/info/rfc9075</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
        <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
        </h2>
<p id="section-boilerplate.2-1">
            Copyright (c) 2021 IETF Trust and the persons identified as the
            document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
        <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
        </h2>
<nav class="toc"><ul class="ulBare compact ulEmpty toc">
<li class="ulBare compact ulEmpty toc" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-scope" class="xref">Scope</a></p>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-workshop-topics-and-discuss" class="xref">Workshop Topics and Discussion</a></p>
<ul class="toc compact ulBare ulEmpty">
<li class="toc compact ulBare ulEmpty" id="section-toc.1-1.3.2.1">
                <p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-measurement-based-observati" class="xref">Measurement-Based Observations on Network Traffic Dynamics</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1.2.1">
                    <p id="section-toc.1-1.3.2.1.2.1.1" class="keepWithNext"><a href="#section-3.1.1" class="xref">3.1.1</a>.  <a href="#name-overall-traffic-growth" class="xref">Overall Traffic Growth</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1.2.2">
                    <p id="section-toc.1-1.3.2.1.2.2.1"><a href="#section-3.1.2" class="xref">3.1.2</a>.  <a href="#name-changes-in-application-use" class="xref">Changes in Application Use</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1.2.3">
                    <p id="section-toc.1-1.3.2.1.2.3.1"><a href="#section-3.1.3" class="xref">3.1.3</a>.  <a href="#name-mobile-networks-and-mobilit" class="xref">Mobile Networks and Mobility</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1.2.4">
                    <p id="section-toc.1-1.3.2.1.2.4.1"><a href="#section-3.1.4" class="xref">3.1.4</a>.  <a href="#name-a-deeper-look-at-interconne" class="xref">A Deeper Look at Interconnections</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1.2.5">
                    <p id="section-toc.1-1.3.2.1.2.5.1"><a href="#section-3.1.5" class="xref">3.1.5</a>.  <a href="#name-cloud-platforms" class="xref">Cloud Platforms</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1.2.6">
                    <p id="section-toc.1-1.3.2.1.2.6.1"><a href="#section-3.1.6" class="xref">3.1.6</a>.  <a href="#name-last-mile-congestion" class="xref">Last-Mile Congestion</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.1.2.7">
                    <p id="section-toc.1-1.3.2.1.2.7.1"><a href="#section-3.1.7" class="xref">3.1.7</a>.  <a href="#name-user-behavior" class="xref">User Behavior</a></p>
</li>
                </ul>
</li>
              <li class="toc compact ulBare ulEmpty" id="section-toc.1-1.3.2.2">
                <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-operational-practices-and-a" class="xref">Operational Practices and Architectural Considerations</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.1">
                    <p id="section-toc.1-1.3.2.2.2.1.1"><a href="#section-3.2.1" class="xref">3.2.1</a>.  <a href="#name-digital-divide" class="xref">Digital Divide</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.2">
                    <p id="section-toc.1-1.3.2.2.2.2.1"><a href="#section-3.2.2" class="xref">3.2.2</a>.  <a href="#name-applications" class="xref">Applications</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.3">
                    <p id="section-toc.1-1.3.2.2.2.3.1"><a href="#section-3.2.3" class="xref">3.2.3</a>.  <a href="#name-observability" class="xref">Observability</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.4">
                    <p id="section-toc.1-1.3.2.2.2.4.1"><a href="#section-3.2.4" class="xref">3.2.4</a>.  <a href="#name-security" class="xref">Security</a></p>
</li>
                  <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3.2.2.2.5">
                    <p id="section-toc.1-1.3.2.2.2.5.1"><a href="#section-3.2.5" class="xref">3.2.5</a>.  <a href="#name-discussion" class="xref">Discussion</a></p>
</li>
                </ul>
</li>
              <li class="toc compact ulBare ulEmpty" id="section-toc.1-1.3.2.3">
                <p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-conclusions" class="xref">Conclusions</a></p>
</li>
            </ul>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.4">
            <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-feedback-on-meeting-format" class="xref">Feedback on Meeting Format</a></p>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-position-papers" class="xref">Position Papers</a></p>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-program-committee" class="xref">Program Committee</a></p>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#appendix-A" class="xref">Appendix A</a>.  <a href="#name-workshop-participants" class="xref">Workshop Participants</a></p>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#appendix-B" class="xref"></a><a href="#name-iab-members-at-the-time-of-" class="xref">IAB Members at the Time of Approval</a></p>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#appendix-C" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a></p>
</li>
          <li class="ulBare compact ulEmpty toc" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#appendix-D" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<div id="introduction">
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">The Internet Architecture Board (IAB) held a workshop to discuss
network impacts of the COVID-19 pandemic on November 9-13, 2020. The
workshop was held to convene interested researchers, network
operators, network management experts, and Internet technologists
to share their experiences. The meeting was held online given the
ongoing travel and contact restrictions at that time.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">COVID-19 has caused changes in user behavior, which in turn drove 
changes in Internet traffic. These changes in user behavior appeared rather abruptly 
and were significant, in particular during the introduction of initial quarantine and work-from-home arrangements. This caused changes in Internet traffic in terms of volume and location, as well as shifts in the types of
applications used. This shift in traffic and user behavior also
created a shift in security practices as well as attack patterns 
that made use of the attack surface, resulting from the shift to
working from home in a global crisis.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">An announcement for the workshop was sent out in July 2020 requesting
that interested parties submit position papers to the workshop program
committee. A total of 15 position papers were received from 33 authors in total. The papers are listed in <a href="#positionpapers" class="xref">Section 5</a>.
In addition, several other types of contributions and pointers to
existing work were provided. A number of position papers referred to
parallel work being published in measurement-related academic
conferences.<a href="#section-1-3" class="pilcrow">¶</a></p>
<p id="section-1-4">Invitations for the workshop were sent out based on the position
papers and other expressions of interest. On the workshop conference calls were 46
participants, listed in <a href="#participants" class="xref">Appendix A</a>.<a href="#section-1-4" class="pilcrow">¶</a></p>
<p id="section-1-5">The workshop was held over the course of one week and hosted three sessions covering
i) measurements and observations, ii) operational and security issues, and iii) future consideration
and conclusions. As these three sessions were scheduled on Monday, Wednesday, and Friday,
a positive side effect was that the time in between the sessions could be used for mailing
list discussion and compilation of additional workshop material.<a href="#section-1-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="scope">
<section id="section-2">
      <h2 id="name-scope">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-scope" class="section-name selfRef">Scope</a>
      </h2>
<p id="section-2-1">The COVID-19 pandemic has had a tremendous impact on people's lives
as well as societies and economies around the globe. But it also had a big
impact on networking. With large numbers of people working from home
or otherwise depending on the network for their daily lives, network
traffic volume has surged. Internet service providers and operators have
reported 20% or more traffic growth in a matter of weeks. Traffic at
Internet Exchange Points (IXPs) is similarly on the rise. Most forms
of network traffic have seen an increase, with conversational
multimedia traffic growing, in some cases, by more than 200%. And user time
spent on conferencing services has risen by an order of magnitude on
some conferencing platforms.<a href="#section-2-1" class="pilcrow">¶</a></p>
<p id="section-2-2">In general, the Internet has coped relatively well with this traffic
growth. The situation is not perfect: there have also been some outages,
video quality reduction, and other issues. Nevertheless,
it is interesting to see how the technology, operators, and service
providers have been able to respond to large changes in traffic
patterns.<a href="#section-2-2" class="pilcrow">¶</a></p>
<p id="section-2-3">Understanding what actually happened with Internet traffic is, of
course, interesting in its own right. How that impacted the user
experience or the intended function of the services is equally
interesting. Measurements of and reports on Internet traffic in 2020
are therefore valuable. But it would also be interesting to understand
what types of network management and capacity expansion actions were
taken in general. Anecdotal evidence points to Internet and service
providers tracking how their services are used and, in many cases,
adjusting services to accommodate the new traffic patterns, from
dynamic allocation of computing resources to more complex changes.<a href="#section-2-3" class="pilcrow">¶</a></p>
<p id="section-2-4">The impacts of this crisis are also a potential opportunity to
understand the impact of traffic shifts and growth more generally
to prepare for future situations -- crises or otherwise -- that impact
networking, or to allow us to adjust the technology to be even
better suited to respond to changes.<a href="#section-2-4" class="pilcrow">¶</a></p>
<p id="section-2-5">The scope of this workshop, based on the call for contributions, included:<a href="#section-2-5" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-2-6.1">measurements of traffic changes, user experience and problems, service performance, and other relevant aspects<a href="#section-2-6.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-2-6.2">discussion about the behind-the-scenes network management and expansion activities<a href="#section-2-6.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-2-6.3">sharing experiences in the fields of general Internet connectivity, conferencing, media/entertainment, and Internet infrastructure<a href="#section-2-6.3" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-2-6.4">lessons learned on preparedness and operations<a href="#section-2-6.4" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-2-6.5">lessons learned on Internet technology and architecture<a href="#section-2-6.5" class="pilcrow">¶</a>
</li>
      </ul>
</section>
</div>
<div id="discussion-topics">
<section id="section-3">
      <h2 id="name-workshop-topics-and-discuss">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-workshop-topics-and-discuss" class="section-name selfRef">Workshop Topics and Discussion</a>
      </h2>
<div id="measurement">
<section id="section-3.1">
        <h3 id="name-measurement-based-observati">
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-measurement-based-observati" class="section-name selfRef">Measurement-Based Observations on Network Traffic Dynamics</a>
        </h3>
<p id="section-3.1-1">The workshop started with a focus on measurements. A large portion of the submitted
papers presented and discussed measurement data, and these submissions provided a good
basis for a better understanding of the situation, covering different angles and
aspects of network traffic and different kinds of networks.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
<p id="section-3.1-2">Changes in Internet traffic due to the COVID-19 pandemic affected different networks 
in various ways. Yet all networks saw some form of change, be it a reduction 
in traffic, an increase in traffic, a change in workday and weekend diurnal patterns, or a change in traffic classes. Traffic volume, directionality ratios, and traffic origins 
and destinations were radically different than from before COVID-19.<a href="#section-3.1-2" class="pilcrow">¶</a></p>
<p id="section-3.1-3">At a high level, while traffic from home networks increased
  significantly, for the traffic in mobile networks different
  trends were observed. Either the traffic increased as well -- 
  for instance, in locations where use 
  of residential ISP services is less common -- traffic decreased as a result
  of reduced population mobility. This observed traffic decrease in mobile
  networks reflected rather the opposite trend than what was observed in
  residential ISPs.<a href="#section-3.1-3" class="pilcrow">¶</a></p>
<p id="section-3.1-4">While diurnal congestion at interconnect points as well in certain last-mile networks was reported, mainly in March,
no persistent congestion was observed. Further, a downward trend in download throughput to certain cloud regions
was measured, which can probably be explained by the increased use of cloud services. This gives another 
indication that the scaling of shared resources in the Internet is working reasonably well enough
to handle even larger changes in traffic as experienced during the first nearly global lockdown of the COVID-19 pandemic.<a href="#section-3.1-4" class="pilcrow">¶</a></p>
<div id="overall-traffic-growth">
<section id="section-3.1.1">
          <h4 id="name-overall-traffic-growth">
<a href="#section-3.1.1" class="section-number selfRef">3.1.1. </a><a href="#name-overall-traffic-growth" class="section-name selfRef">Overall Traffic Growth</a>
          </h4>
<p id="section-3.1.1-1">The global pandemic has significantly accelerated the growth of data traffic worldwide.
Based on the measurement data of one ISP, three IXPs, a metropolitan educational network,
and a mobile operator, it was observed at the beginning of the workshop <span>[<a href="#Feldmann2020" class="xref">Feldmann2020</a>]</span> that, overall, the
network was able to handle the situation well despite a significant and sudden increase in the traffic
growth rate in March and April. That is, after the lockdown was implemented in March, a traffic increase
of 15-20% was observed at the ISP as well as at the three IXPs.  This traffic growth, which would 
typically occur over a year, took place over a few weeks -- a substantial 
increase. At DE-CIX Frankfurt, the world's largest Internet Exchange Point in terms of data throughput,
the year 2020 saw the largest increase in peak traffic within a single year since the IXP was
founded in 1995. Additionally, mobile traffic has slightly receded. In access networks, the growth rate
of upstream traffic also exceeded the growth in downstream traffic, reflecting increased adoption
and use of videoconferencing and other remote work and school applications.<a href="#section-3.1.1-1" class="pilcrow">¶</a></p>
<p id="section-3.1.1-2">Most traffic increases happened outside of pre-pandemic peak hours. Before the first COVID-19 lockdowns, the main time
of use was in the evening hours during the week, whereas, since March, it has been spread more equally
across the day. That is, the increase in usage has mainly occurred outside the previous peak usage
times (e.g., during the day while working from home). This means that, for the first time, network
utilization on weekdays resembled that on weekends. The effects of the increased traffic volume could
easily be absorbed, either by using existing reserve capacity or by quickly switching additional bandwidth.
This is one reason why the Internet was able to cope well with the pandemic during the first lockdown period.<a href="#section-3.1.1-2" class="pilcrow">¶</a></p>
<p id="section-3.1.1-3">Some of the lockdowns were lifted or relaxed around May 2020. As people were allowed to resume some
of their daily activities outside of their home again, as expected, there was a decrease in the traffic
observed at the IXPs and the ISP; instead, mobile traffic began to grow again.<a href="#section-3.1.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="changes-in-application-use">
<section id="section-3.1.2">
          <h4 id="name-changes-in-application-use">
<a href="#section-3.1.2" class="section-number selfRef">3.1.2. </a><a href="#name-changes-in-application-use" class="section-name selfRef">Changes in Application Use</a>
          </h4>
<p id="section-3.1.2-1">The composition of data traffic has changed since the beginning of the pandemic: the use of
videoconferencing services and virtual private networks (VPNs) for access to company resources
from the home environment has risen sharply. In ISP and IXP networks, it was observed <span>[<a href="#Feldmann2020" class="xref">Feldmann2020</a>]</span>
that traffic associated with web conferencing, video, and gaming increased significantly in March 2020
as a result of the increasing user demand for solutions like Zoom or Microsoft Teams.
For example, the relative traffic share of many "essential" applications like VPN and conferencing tools
increased by more than 200%.<a href="#section-3.1.2-1" class="pilcrow">¶</a></p>
<p id="section-3.1.2-2">Also, as people spent more hours at home, they tended to watch videos or play games, thus increasing entertainment traffic demands.
At the same time, the traffic share for other traffic classes decreased
substantially, e.g., traffic related to education, social media, and, for some periods, content delivery networks (CDNs).
In April and June, web conferencing traffic was still high compared to the pre-pandemic scenario,
while a slight decrease in CDN and social media traffic was observed. During these months, many people
were still working from home, but restrictions had been lifted or relaxed, which likely led to an increase
in in-person social activities and a decrease in online social activities.<a href="#section-3.1.2-2" class="pilcrow">¶</a></p>
<div id="example-campus-networks">
<section id="section-3.1.2.1">
            <h5 id="name-example-campus-networks">
<a href="#section-3.1.2.1" class="section-number selfRef">3.1.2.1. </a><a href="#name-example-campus-networks" class="section-name selfRef">Example Campus Networks</a>
            </h5>
<p id="section-3.1.2.1-1">Changes in traffic have been observed at university campus networks as well, especially
due to the necessary adoption of remote teaching. The Politecnico di Torino (Italy) deployed its in-house solution for remote teaching, which caused the outgoing 
traffic to grow by 2.5 times, driven by more than 600 daily online classes. Incoming 
traffic instead decreased by a factor of 10 due to the cessation of any in-person 
activity. Based on their measurements, this change in traffic and network usage did not, however, lead to noticeable performance impairments, nor has significantly poor 
performance been observed in students in remote regions of Italy. Outgoing traffic
also increased due to other remote working solutions, such as collaboration platforms,
VPNs, and remote desktops.<a href="#section-3.1.2.1-1" class="pilcrow">¶</a></p>
<p id="section-3.1.2.1-2">Similar changes were observed by measuring REDIMadrid <span>[<a href="#Feldmann2020" class="xref">Feldmann2020</a>]</span>, a European 
educational and research network that connects 16 independent universities and research 
centers in the metropolitan region of Madrid. A drop of up to 55% in traffic volume on 
working days during the pandemic was observed. Similar to findings for ISP/IXP networks, 
it was observed that working days and weekend days are becoming more similar in terms of 
total traffic. The hourly traffic patterns reveal a traffic increase between 9 pm and 7 am.
This could be due to users working more frequently at unusual times but could also potentially be 
caused by overseas students (mainly from Latin America and East Asia as suggested by the 
Autonomous System (AS) numbers from which these connections came) who accessed university network resources 
from their home countries.<a href="#section-3.1.2.1-2" class="pilcrow">¶</a></p>
<p id="section-3.1.2.1-3">Given the fact that the users of the academic network (e.g., students and research staff) 
had to leave campus as a response to lockdown measures, the traffic in-and-out 
(i.e., ingress and egress) ratio also changed drastically. Prior to the lockdown, the incoming 
traffic volume was much larger than the outgoing traffic volume. This changed to a more balanced ratio. 
This change of traffic asymmetry can be explained by the nature of remote work. On the one
hand, users connected to the network services mainly to access resources, hence the increase
in outgoing traffic. On the other hand, all external (i.e., Internet-based) resources 
requested during work were no longer accessed from the educational network but from the
users' homes.<a href="#section-3.1.2.1-3" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="mobile-networks-and-mobility">
<section id="section-3.1.3">
          <h4 id="name-mobile-networks-and-mobilit">
<a href="#section-3.1.3" class="section-number selfRef">3.1.3. </a><a href="#name-mobile-networks-and-mobilit" class="section-name selfRef">Mobile Networks and Mobility</a>
          </h4>
<p id="section-3.1.3-1">Mobile network data usage appeared to decline following the imposition of localized 
lockdown measures as these reduced typical levels of mobility and roaming.<a href="#section-3.1.3-1" class="pilcrow">¶</a></p>
<p id="section-3.1.3-2"><span>[<a href="#Lutu2020" class="xref">Lutu2020</a>]</span> measured the cellular network of O2 UK to evaluate how the changes in 
people's mobility impacted traffic patterns. By analyzing cellular network signaling 
information regarding users' device mobility activity, they observed a decrease of 50% in 
mobility (according to different mobility metrics) in the UK during the lockdown period. 
As they found no correlation between this reduction in mobility and the number of 
confirmed COVID-19 cases, only the enforced government order was effective in significantly 
reducing mobility, and this reduction was more significant in densely populated urban areas 
than in rural areas. For London specifically, it could be observed from the mobile network 
data that approximately 10% of residents temporarily relocated during the lockdown.<a href="#section-3.1.3-2" class="pilcrow">¶</a></p>
<p id="section-3.1.3-3">These mobility changes had immediate implications in the traffic patterns of the cellular 
network. The downlink data traffic volume aggregated for all bearers (including 
conversational voice) decreased for the entire UK by up to 25% during the lockdown period. This 
correlates with the reduction in mobility that was observed countrywide, which likely resulted 
in people relying more on residential broadband Internet access to run download-intensive applications such as video streaming. The observed decrease in the radio cell 
load, with a reduction of approximately 15% across the UK after the stay-at-home order was enacted, 
further corroborates the drop in cellular connectivity usage.<a href="#section-3.1.3-3" class="pilcrow">¶</a></p>
<p id="section-3.1.3-4">The total uplink data traffic volume, on the other hand, experienced little change 
(between -7% and +1.5%) during lockdown. This was mainly due to the increase of 4G voice 
traffic (i.e., Voice over LTE (VoLTE)) across the UK that peaked at 150% after the lockdown compared to the 
national median value before the pandemic, thus compensating for the decrease in data traffic 
in the uplink.<a href="#section-3.1.3-4" class="pilcrow">¶</a></p>
<p id="section-3.1.3-5">Finally, it was also observed that mobility changes have a different impact on network usage 
in geodemographic area clusters. In densely populated urban areas, a significantly higher 
decrease of mobile network usage (i.e., downlink and uplink traffic volume, radio load, and 
active users) was observed compared to rural areas. In the case of London, this 
was likely due to the geodemographics of the central districts, which include many seasonal 
residents (e.g., tourists) and business and commercial areas.<a href="#section-3.1.3-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="a-deeper-look-at-interconnections">
<section id="section-3.1.4">
          <h4 id="name-a-deeper-look-at-interconne">
<a href="#section-3.1.4" class="section-number selfRef">3.1.4. </a><a href="#name-a-deeper-look-at-interconne" class="section-name selfRef">A Deeper Look at Interconnections</a>
          </h4>
<p id="section-3.1.4-1">Traffic at points of network interconnection noticeably increased, but most operators 
reacted quickly by rapidly adding additional capacity <span>[<a href="#Feldmann2020" class="xref">Feldmann2020</a>]</span>. The amount of 
increase varied, with some networks that hosted popular applications such as videoconferencing experiencing traffic growth of several hundred to several thousand percent. 
At the IXP level, it was observed that port utilization increased. This phenomenon is 
mostly explained by higher traffic demand from residential users.<a href="#section-3.1.4-1" class="pilcrow">¶</a></p>
<p id="section-3.1.4-2">Measurements of interconnection links at major US ISPs by the Center for Applied Internet Data Analysis (CAIDA) and the Massachusetts Institute of Technology (MIT) found some evidence 
of diurnal congestion around the March 2020 time frame <span>[<a href="#Clark2020" class="xref">Clark2020</a>]</span>, but most of this 
congestion disappeared in a few weeks, which suggests that operators indeed took steps 
to add capacity or otherwise mitigate the congestion.<a href="#section-3.1.4-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="cloud-platforms">
<section id="section-3.1.5">
          <h4 id="name-cloud-platforms">
<a href="#section-3.1.5" class="section-number selfRef">3.1.5. </a><a href="#name-cloud-platforms" class="section-name selfRef">Cloud Platforms</a>
          </h4>
<p id="section-3.1.5-1">Cloud infrastructure played a key role in supporting bandwidth-intensive videoconferencing 
and remote learning tools to practice social distancing during the COVID-19 pandemic. Network 
congestion between cloud platforms and access networks could impact the quality of 
experience of these cloud-based applications. CAIDA leveraged web-based speed test servers 
to take download and upload throughput measurements from virtual machines in public 
cloud platforms to various access ISPs in the United States <span>[<a href="#Mok2020" class="xref">Mok2020</a>]</span>.<a href="#section-3.1.5-1" class="pilcrow">¶</a></p>
<p id="section-3.1.5-2">The key findings included the following:<a href="#section-3.1.5-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-3.1.5-3.1">Persistent congestion events were not widely observed between cloud platforms and these networks, particular for large-scale ISPs, but we could observe large diurnal download throughput variations in peak hours from some locations to the cloud.<a href="#section-3.1.5-3.1" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.1.5-3.2">There was evidence of persistent congestion in the egress direction to regional ISPs serving suburban areas in the US. Their users could have suffered from poor video streaming or file download performance from the cloud.<a href="#section-3.1.5-3.2" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.1.5-3.3">The macroscopic analysis over 3 months (June-August 2020) revealed downward trends in download throughput from ISPs and educational networks to certain cloud regions. We believe that increased use of the cloud in the pandemic could be one of the factors that contributed to the decreased performance.<a href="#section-3.1.5-3.3" class="pilcrow">¶</a>
</li>
          </ul>
</section>
</div>
<div id="last-mile-congestion">
<section id="section-3.1.6">
          <h4 id="name-last-mile-congestion">
<a href="#section-3.1.6" class="section-number selfRef">3.1.6. </a><a href="#name-last-mile-congestion" class="section-name selfRef">Last-Mile Congestion</a>
          </h4>
<p id="section-3.1.6-1">The last mile is the centerpiece of broadband connectivity, where poor last-mile performance 
generally translates to poor quality of experience. In a recent Internet Measurement Conference (IMC '20) research paper, 
Fontugne et al. investigated last-mile latency using traceroute data from Reseaux IP Europeens (RIPE) Atlas 
probes located in 646 ASes and looked for recurrent performance degradation <span>[<a href="#Fontugne2020-1" class="xref">Fontugne2020-1</a>]</span>. 
They found that, in normal times, Atlas probes experience persistent 
last-mile congestion in only 10% of ASes, but they recorded 55% more congested ASes during the COVID-19 
outbreak. This deterioration caused by stay-at-home measures is particularly marked in 
networks with a very large number of users and in certain parts of the world. They found Japan to be the most 
impacted country in their study, looking specifically at the Nippon Telegraph and Telephone (NTT) Corporation Open Computer Network (OCN) but noting similar 
observations for several Japanese networks, including Internet Initiative Japan (IIJ) (AS2497).<a href="#section-3.1.6-1" class="pilcrow">¶</a></p>
<p id="section-3.1.6-2">From mid-2020 onward, however, they observed better performance than before the pandemic. 
In Japan, this was partly due to the deployments originally planned for accommodating the 
Tokyo Olympics, and, more generally, it reflects the efforts of network operators to cope 
with these exceptional circumstances. The pandemic has demonstrated that its adaptive design 
and proficient community can keep the Internet operational during such unprecedented events. 
Also, from the numerous research and operational reports recently published, the pandemic 
is apparently shaping a more resilient Internet; as Nietzsche wrote, "What does not kill me 
makes me stronger".<a href="#section-3.1.6-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="user-behaviour">
<section id="section-3.1.7">
          <h4 id="name-user-behavior">
<a href="#section-3.1.7" class="section-number selfRef">3.1.7. </a><a href="#name-user-behavior" class="section-name selfRef">User Behavior</a>
          </h4>
<p id="section-3.1.7-1">The type of traffic needed by the users also changed in 2020. Upstream
traffic increased due the use of videoconferences, remote schooling,
and similar applications. The National Cable &amp;
 Telecommunications Association (NCTA) and Comcast reported that while
downstream traffic grew 20%, upstream traffic grew by as much as 30-37% <span>[<a href="#NCTA2020" class="xref">NCTA2020</a>]</span> <span>[<a href="#Comcast2020" class="xref">Comcast2020</a>]</span>. Vodafone reported that upstream
traffic grew by 100% in some markets <span>[<a href="#Vodafone2020" class="xref">Vodafone2020</a>]</span>.<a href="#section-3.1.7-1" class="pilcrow">¶</a></p>
<p id="section-3.1.7-2">Ericsson's ConsumerLab surveyed users regarding their usage and experiences
during the crisis. Some of the key findings in <span>[<a href="#ConsumerlabReport2020" class="xref">ConsumerlabReport2020</a>]</span> were as follows:<a href="#section-3.1.7-2" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-3.1.7-3.1">9 in 10 users increased Internet activities, and time spent
connected increased. In addition, 1 in 5 started new online
activities; many in the older generation felt that they were helped
by video calling; parents felt that their children's education was
helped; and so on.<a href="#section-3.1.7-3.1" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.1.7-3.2">Network performance was, in general, found satisfactory. 6 in 10 were
very satisfied with fixed broadband, and 3 in 4 felt that mobile
broadband was the same or better compared to before the crisis.  Consumers valued
resilience and quality of service as the most important responsibility for
network operators.<a href="#section-3.1.7-3.2" class="pilcrow">¶</a>
</li>
            <li class="normal" id="section-3.1.7-3.3">Smartphone application usage changed, with the fastest growth in
apps related to COVID-19 tracking and information, remote working, e-learning, wellness, education, remote
health consultation, and social shared experience
applications. The biggest decreases were in travel
and booking, ride hailing, location, and parking applications.<a href="#section-3.1.7-3.3" class="pilcrow">¶</a>
</li>
          </ul>
<p id="section-3.1.7-4">Some of the behaviors are likely permanent changes
<span>[<a href="#ConsumerlabReport2020" class="xref">ConsumerlabReport2020</a>]</span>. The adoption of video calls and other new
services by many consumers, such as the older generation, is likely
going to have a long-lasting effect.  Surveys in various organizations
point to a likely long-term increase in the number of people
interested in remote work <span>[<a href="#WorkplaceAnalytics2020" class="xref">WorkplaceAnalytics2020</a>]</span> <span>[<a href="#McKinsey2020" class="xref">McKinsey2020</a>]</span>.<a href="#section-3.1.7-4" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="operational">
<section id="section-3.2">
        <h3 id="name-operational-practices-and-a">
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-operational-practices-and-a" class="section-name selfRef">Operational Practices and Architectural Considerations</a>
        </h3>
<p id="section-3.2-1">The second and third days of the workshop focused on open
discussions of arising operational and architectural issues and 
the conclusions that could be reached from previous discussions
and other issues raised in the position papers.<a href="#section-3.2-1" class="pilcrow">¶</a></p>
<div id="digital-divide">
<section id="section-3.2.1">
          <h4 id="name-digital-divide">
<a href="#section-3.2.1" class="section-number selfRef">3.2.1. </a><a href="#name-digital-divide" class="section-name selfRef">Digital Divide</a>
          </h4>
<p id="section-3.2.1-1">Measurements from Fastly confirmed that Internet traffic volume in
multiple countries rose rapidly while COVID cases were increasing and lockdown policies were coming into effect. Download speeds also decreased
but in a much less dramatic fashion than when overall bandwidth usage increased.
School closures led to a dramatic increase in traffic volume in many regions,
and other public policy announcements triggered large traffic shifts. This
suggests that governments should coordinate with operators to allow
time for preemptive operational changes in some cases.<a href="#section-3.2.1-1" class="pilcrow">¶</a></p>
<p id="section-3.2.1-2">Measurements from the US showed that download rates correlate with income
levels. However, download rates in the lowest income zip codes increased
as the pandemic progressed, closing the divide with higher income areas.
One possible reason for this in the data is decisions by some ISPs, such
as Comcast and Cox, that increased speeds for users on certain lower-cost plans and in
certain areas. This suggests that network capacity was available and that
the correlation between income and download rates was not necessarily due
to differences in the deployed infrastructure in different regions,
although it was noted that certain access link technologies provide more
flexibility than others in this regard.<a href="#section-3.2.1-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="applications">
<section id="section-3.2.2">
          <h4 id="name-applications">
<a href="#section-3.2.2" class="section-number selfRef">3.2.2. </a><a href="#name-applications" class="section-name selfRef">Applications</a>
          </h4>
<p id="section-3.2.2-1">Web conferencing systems (e.g., Microsoft Teams, Zoom, Webex) saw
incredible growth, with overnight traffic increases of 15-20% in response
to public policy changes, such as lockdowns. This required significant
and rapid changes in infrastructure provisioning.<a href="#section-3.2.2-1" class="pilcrow">¶</a></p>
<p id="section-3.2.2-2">Major video providers (YouTube, etc.) reduced bandwidth by 25% in some
regions. It was suggested that this had a huge impact on the quality of
videoconferencing systems until networks could scale to handle the full
bit rate, but other operators of some other services saw limited impact.<a href="#section-3.2.2-2" class="pilcrow">¶</a></p>
<p id="section-3.2.2-3">Updates to popular games have a significant impact on network load. Some
discussions were reported between ISPs, CDNs, and the gaming industry on
possibly coordinating various high-bandwidth update events, similar to what
was done for entertainment/video download speeds. There was an apparently
difficult interplay between bulk download and interactive real-time
applications, potentially due to buffer bloat and queuing delays.<a href="#section-3.2.2-3" class="pilcrow">¶</a></p>
<p id="section-3.2.2-4">It was noted that operators have experience with rapid growth of Internet
traffic. New applications with exponential growth are not that unusual in
the network, and the traffic spike due to the lockdown was not that
unprecedented for many. Many operators have tools and mechanisms to deal
with this. Ensuring that knowledge is shared is a challenge.<a href="#section-3.2.2-4" class="pilcrow">¶</a></p>
<p id="section-3.2.2-5">Following these observations, traffic prioritization was discussed, starting from Differentiated Services Code Point (DSCP) marking. The question arose as to whether
a minimal priority-marking scheme
would have helped during the pandemic, e.g., by allowing
marking of less-than-best-effort traffic.
That discussion quickly devolved into a more general QoS and
observability discussion and, as such, also touched on
the effects of increased encryption. The group 
was not, unsurprisingly, able to resolve the
different perspectives and interests involved,
but the discussion demonstrated that progress was made.<a href="#section-3.2.2-5" class="pilcrow">¶</a></p>
</section>
</div>
<div id="observability">
<section id="section-3.2.3">
          <h4 id="name-observability">
<a href="#section-3.2.3" class="section-number selfRef">3.2.3. </a><a href="#name-observability" class="section-name selfRef">Observability</a>
          </h4>
<p id="section-3.2.3-1">It is clear that there is a contrast in experience. Many operators reported
few problems in terms of metrics, such as measured download bandwidth, while
videoconferencing applications experienced significant usability problems
running on those networks. The interaction between application providers and
network providers worked very smoothly to resolve these issues, supported
by strong personal contacts and relationships. But it seems clear that the
metrics used by many operators to understand their network performance
don't fully capture the impact on certain applications, and there is an
observability gap. Do we need more tools to figure out the various impacts
on user experience?<a href="#section-3.2.3-1" class="pilcrow">¶</a></p>
<p id="section-3.2.3-2">These types of applications use surprising amounts of Forward Error Correction (FEC). 
Applications hide lots of loss to ensure a good user experience. This makes it harder to
observe problems. The network can be behaving poorly, but the experience can be
good enough. Resiliency measures can improve the user experience but hide
severe problems. There may be a missing feedback loop between application
developers and operators.<a href="#section-3.2.3-2" class="pilcrow">¶</a></p>
<p id="section-3.2.3-3">It's clear that it's difficult for application providers and operators to 
isolate problems. Is a problem due to the local Wi-Fi, the access network, the
cloud network, etc.?  Metrics from access points would help, but in general,
lack of observability into the network as a whole is a real concern when
it comes to debugging performance issues.<a href="#section-3.2.3-3" class="pilcrow">¶</a></p>
<p id="section-3.2.3-4">Further, it's clear that it can be difficult to route problem reports to
the person who can fix them, especially if the reported information needs 
to be shared across multiple networks in the Internet.
COVID-enhanced cooperation made it easier to debug problems; lines of
communication are important.<a href="#section-3.2.3-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="security">
<section id="section-3.2.4">
          <h4 id="name-security">
<a href="#section-3.2.4" class="section-number selfRef">3.2.4. </a><a href="#name-security" class="section-name selfRef">Security</a>
          </h4>
<p id="section-3.2.4-1">The increased threats and network security impacts arising from COVID-19
fall into two areas: (1) the agility of malicious actors to spin up new
campaigns using COVID-19 as a lure, and (2) the increased threat surface
from a rapid shift towards working from home.<a href="#section-3.2.4-1" class="pilcrow">¶</a></p>
<p id="section-3.2.4-2">During 2020, there was a shift to home working generally, and in the
way in which people used the network. IT departments rolled out new equipment
quickly and used technologies like VPNs for the first time, while others put existing solutions under much greater load. As VPN technology became more widespread and more widely used, it arguably became a more valuable target; one Advanced Persistent Threat group (APT29) was successful in using recently published exploits in a range of VPN software to gain initial footholds <span>[<a href="#Kirsty2020" class="xref">Kirsty2020</a>]</span>.<a href="#section-3.2.4-2" class="pilcrow">¶</a></p>
<p id="section-3.2.4-3">Of all scams detected by the United Kingdom National Cyber Security Centre (UK NCSC) that purported to originate from the UK Government, more related to COVID-19 than any other subject. There are other reports of a strong rise in phishing, fraud, and scams related to
COVID <span>[<a href="#Kirsty2020" class="xref">Kirsty2020</a>]</span>. Although the overall levels of cybercrime have not increased from the data seen to date, there was
certainly a shift in activity as both the NCSC and the Department of Homeland Security Cybersecurity and Infrastructure Security Agency (DHS CISA) saw growing use of COVID-19-related themes by malicious cyber actors as a lure. Attackers used COVID-19-related scams and phishing emails to target individuals, small and medium businesses, large organizations, and organizations involved in both national and international COVID-19 responses (healthcare bodies, pharmaceutical companies, academia, and medical research organizations). New targets (for example, organizations involved in COVID-19 vaccine development)
were attacked using VPN exploits, highlighting the potential consequences of vulnerable infrastructure.<a href="#section-3.2.4-3" class="pilcrow">¶</a></p>
<p id="section-3.2.4-4">It's unclear how to effectively detect and counter these attacks at scale.
Approaches such as using Indicators of Compromise and crowdsourced flagging of suspicious emails were found to be effective in response to COVID-19-related scams <span>[<a href="#Kirsty2020" class="xref">Kirsty2020</a>]</span>, and
observing the DNS to detect malicious use is widespread and effective. The use
of DNS over HTTPS offers privacy benefits, but current deployment models can bypass
these existing protective DNS measures.<a href="#section-3.2.4-4" class="pilcrow">¶</a></p>
<p id="section-3.2.4-5">It was also noted that when everyone moves to performing their job online,
lack of understanding of security becomes a bigger issue.
Is it reasonable to expect every user of the Internet to have
password training? Or is there a fundamental problem with a technical
solution? Modern advice advocates a layered approach to security defenses, with user education forming just one of those layers.<a href="#section-3.2.4-5" class="pilcrow">¶</a></p>
<p id="section-3.2.4-6">Communication platforms such as Zoom are not new: many people have used them
for years, but as COVID-19 saw an increasing number of organizations and individuals turning to these technologies, they became an attractive target due to increased usage. In turn, there was an increase in malicious cyber actor activity, either through hijacking online meetings that were not secured with passwords or leveraging unpatched software as an attack vector. How can new or existing measures protect users from the attacks levied against the next
vulnerable service?<a href="#section-3.2.4-6" class="pilcrow">¶</a></p>
<p id="section-3.2.4-7">Overall, it may be that there were fewer security
challenges than expected arising from many people suddenly working from home.
However, the agility of attackers, the importance of robust and scalable defense mechanisms, and some existing security problems and challenges may have become even
more obvious and acute with an increased use of Internet-based services, particularly in a pandemic situation and in times of uncertainty, where users can be more vulnerable to social engineering techniques and attacks.<a href="#section-3.2.4-7" class="pilcrow">¶</a></p>
</section>
</div>
<div id="discussion">
<section id="section-3.2.5">
          <h4 id="name-discussion">
<a href="#section-3.2.5" class="section-number selfRef">3.2.5. </a><a href="#name-discussion" class="section-name selfRef">Discussion</a>
          </h4>
<p id="section-3.2.5-1">There is a concern that we're missing observability for the network as a
whole. Each application provider and operator has their own little lens.
No one has the big-picture view of the network.<a href="#section-3.2.5-1" class="pilcrow">¶</a></p>
<p id="section-3.2.5-2">How much of a safety margin do we need? Some of the resiliency comes from
us not running the network too close to its limit. This allows traffic to
shift and gives headroom for the network to cope. The best-effort nature
of the network may help here. Using techniques to run the network closer to its
limits usually improves performance, but highly optimized networks 
may be less robust.<a href="#section-3.2.5-2" class="pilcrow">¶</a></p>
<p id="section-3.2.5-3">Finally, it was observed that we get what we measure. There may be an
argument for operators to perhaps shift their measurement focus away from
pure capacity to instead measure Quality of Experience (QoE) or resilience. The Internet is a
critical infrastructure, and people are realizing that now. We should use
this as a wake-up call to improve resilience, both in protocol design and
operational practice, not necessarily to optimize for absolute performance
or quality of experience.<a href="#section-3.2.5-3" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="conclusions">
<section id="section-3.3">
        <h3 id="name-conclusions">
<a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-conclusions" class="section-name selfRef">Conclusions</a>
        </h3>
<p id="section-3.3-1">There is a wealth of data about the performance of the Internet during
the COVID-19 crisis. The main conclusion from the various measurements is that
fairly large shifts occurred. 
And those shifts were not merely about
exchanging one application for another; they actually impacted traffic
flows and directions and caused, in many cases, a significant traffic
increase. Early reports also seem to indicate that the shifts have
gone relatively smoothly from the point of view of overall consumer
experience.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
<p id="section-3.3-2">An important but not so visible factor that led to running smoothly was that
many people and organizations were highly motivated to ensure good user
experience. A lot of collaboration happened in the background,
problems were corrected, many providers significantly increased their
capacity, and so on.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
<p id="section-3.3-3">On the security front, the COVID-19 crisis showcased the agility with 
which malicious actors can move in response to a shift in user 
Internet usage and the vast potential of the disruption and damage 
that they can inflict. Equally, it showed the agility of defenders when they have access to the tools and information they need to protect
users and networks, and it showcased the power of Indicators of Compromise
when defenders around the world are working together against the same 
problem.<a href="#section-3.3-3" class="pilcrow">¶</a></p>
<p id="section-3.3-4">In general, the Internet also seems well suited for
adapting to new situations, at least within some bounds.  The
Internet is designed for flexibility and extensibility, rather than
being optimized for today's particular traffic types. This makes it possible to
use it for many applications and in many deployment situations and to make
changes as needed. The generality is present in many parts of the
overall system, from basic Internet technology to browsers and from name
servers to content delivery networks and cloud platforms. When usage
changes, what is needed is often merely different services, perhaps
some reallocation of resources as well as consequent application and
continuation of existing security defenses, but not fundamental technology or
hardware changes.<a href="#section-3.3-4" class="pilcrow">¶</a></p>
<p id="section-3.3-5">On the other hand, this is not to say that no improvements are needed:<a href="#section-3.3-5" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-3.3-6.1">We need a better understanding of the health of the Internet. Going forward,
the critical nature that the Internet plays in our lives means that the
health of the Internet needs to receive significant
attention. Understanding how well networks work is not just a
technical matter; it is also of crucial importance to the people and
economies of the societies using it. Projects and research that
monitor Internet and services performance on a broad scale and
across different networks are therefore important.<a href="#section-3.3-6.1" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-3.3-6.2">We need to maintain defensive mechanisms to be used in times of crisis.
Malicious cyber actors are continually adjusting their tactics to take
advantage of new situations, and the COVID-19 pandemic is no exception.
Malicious actors used the strong appetite for COVID-19-related information
as an opportunity to deliver malware and ransomware and to steal user 
credentials. Against the landscape of a shift to working from home and 
an increase in users vulnerable to attack, and as IT departments were 
often overwhelmed by rolling out new infrastructure and devices, sharing  Indicators of Compromise (IoC) was a vital part of the response to COVID-19-related scams and 
attacks.<a href="#section-3.3-6.2" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-3.3-6.3">We need to ensure that broadband is available to all and that Internet
services equally serve different groups. The pandemic has shown how the
effects of the digital divide can be amplified during a crisis and has
further highlighted the importance of equitable Internet access.<a href="#section-3.3-6.3" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-3.3-6.4">We need to continue to work on all the other improvements that are seen
as necessary anyway, such as further improvements in security, the ability
for networks and applications to collaborate better, etc.<a href="#section-3.3-6.4" class="pilcrow">¶</a>
</li>
          <li class="normal" id="section-3.3-6.5">We need to ensure that informal collaboration between different parties 
involved in the operation of the network continues and is strengthened
to ensure continued operational resilience.<a href="#section-3.3-6.5" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
</section>
</div>
<div id="feedback-on-meeting-format">
<section id="section-4">
      <h2 id="name-feedback-on-meeting-format">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-feedback-on-meeting-format" class="section-name selfRef">Feedback on Meeting Format</a>
      </h2>
<p id="section-4-1">While there are frequently virtual participants in IAB workshops, the
IAB had no experience running workshops entirely virtually.<a href="#section-4-1" class="pilcrow">¶</a></p>
<p id="section-4-2">Feedback on this event format was largely positive, however. It was
particularly useful that as the three sessions were scheduled on Monday,
Wednesday, and Friday, the time in between the sessions could be used for mailing
list discussion and compilation of additional workshop material.
The positive feedback was likely at least partly due to the fact
that many of the workshop participants knew one another from
previous face-to-face events (primarily IETF meetings).<a href="#section-4-2" class="pilcrow">¶</a></p>
<p id="section-4-3">The process for sending invitations to the workshop should be improved
for next time, however, as a few invitations were initially lost. In a virtual meeting, it may be more reasonable to invite not just one
person but all coauthors of a paper, for instance. At least for this
workshop, we did not appear to suffer from having too many participants, and
in many cases, there may be some days when a particular participant may
not be able to attend a session.<a href="#section-4-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="positionpapers">
<section id="section-5">
      <h2 id="name-position-papers">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-position-papers" class="section-name selfRef">Position Papers</a>
      </h2>
<p id="section-5-1">The following position papers were received, in alphabetical order:<a href="#section-5-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="section-5-2.1">Afanasyev, A., Wang, L., Yeh, E., Zhang, B., and Zhang, L.: Identifying the Disease from the Symptoms: Lessons for Networking in the COVID-19 Era <span>[<a href="#Afxanasyev2020" class="xref">Afxanasyev2020</a>]</span><a href="#section-5-2.1" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.2">Arkko, J.: Observations on Network User Behaviour During COVID-19 <span>[<a href="#Arkko2020" class="xref">Arkko2020</a>]</span><a href="#section-5-2.2" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.3">Bronzino, F., Culley, E., Feamster, N., Liu, S., Livingood, J., and Schmitt, P.: IAB COVID-19 Workshop: Interconnection Changes in the United States <span>[<a href="#I-D.feamster-livingood-iab-covid19-workshop" class="xref">Bronzino2020</a>]</span><a href="#section-5-2.3" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.4">Campling, A. and Lazanski, D.: Will the Internet Still Be Resilient During the Next Black Swan Event? <span>[<a href="#Campling2020" class="xref">Campling2020</a>]</span><a href="#section-5-2.4" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.5">Cho, K.: On the COVID-19 Impact to broadband traffic in Japan <span>[<a href="#Cho2020" class="xref">Cho2020</a>]</span><a href="#section-5-2.5" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.6">Clark, D.: Measurement of congestion on ISP interconnection links <span>[<a href="#Clark2020" class="xref">Clark2020</a>]</span><a href="#section-5-2.6" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.7">Favale, T., Soro, F., Trevisan, M., Drago, I., and Mellia, M.: Campus traffic and e-Learning during COVID-19 pandemic <span>[<a href="#Favale2020" class="xref">Favale2020</a>]</span><a href="#section-5-2.7" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.8">Feldmann, A., Gasser, O., Lichtblau, F., Pujol, E., Poese, I., Dietzel, C., Wagner, D., Wichtlhuber, M., Tapiador, J., Vallina-Rodriguez, N., Hohlfeld, O., and Smaragdakis, G.: A view of Internet Traffic Shifts at ISP and IXPs during the COVID-19 Pandemic <span>[<a href="#Feldmann2020" class="xref">Feldmann2020</a>]</span><a href="#section-5-2.8" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.9">Fontugne, R., Shah, A., and Cho, K.: The Impact of COVID-19 on Last-mile Latency <span>[<a href="#Fontugne2020" class="xref">Fontugne2020</a>]</span><a href="#section-5-2.9" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.10">Gillmor, D.: Vaccines, Privacy, Software Updates, and Trust <span>[<a href="#Gillmor2020" class="xref">Gillmor2020</a>]</span><a href="#section-5-2.10" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.11">Gu, Y. and Li, Z.: Covid 19 Impact on China ISP's Network Traffic Pattern and Solution Discussion <span>[<a href="#Gu2020" class="xref">Gu2020</a>]</span><a href="#section-5-2.11" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.12">Jennings, C. and Kozanian, P.: WebEx Scaling During Covid <span>[<a href="#Jennings2020" class="xref">Jennings2020</a>]</span><a href="#section-5-2.12" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.13">Lutu, A., Perino, D., Bagnulo, M., Frias-Martinez, E., and Khangosstar, J.: A Characterization of the COVID-19 Pandemic Impact on a Mobile Network Operator Traffic <span>[<a href="#Lutu2020" class="xref">Lutu2020</a>]</span><a href="#section-5-2.13" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.14">Mok, R., and claffy, kc: Measuring the impact of COVID-19 on cloud network performance <span>[<a href="#Mok2020" class="xref">Mok2020</a>]</span><a href="#section-5-2.14" class="pilcrow">¶</a>
</li>
        <li class="normal" id="section-5-2.15">Paine, K.: IAB COVID-19 Network Impacts <span>[<a href="#Kirsty2020" class="xref">Kirsty2020</a>]</span><a href="#section-5-2.15" class="pilcrow">¶</a>
</li>
      </ul>
</section>
</div>
<div id="program-committee">
<section id="section-6">
      <h2 id="name-program-committee">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-program-committee" class="section-name selfRef">Program Committee</a>
      </h2>
<p id="section-6-1">The workshop program committee members were <span class="contact-name">Jari Arkko</span>, <span class="contact-name">Stephen Farrell</span>, <span class="contact-name">Cullen Jennings</span>, <span class="contact-name">Colin Perkins</span>, <span class="contact-name">Ben Campbell</span>, and <span class="contact-name">Mirja Kühlewind</span>.<a href="#section-6-1" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-7">
      <h2 id="name-informative-references">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
      </h2>
<dl class="references">
<dt id="Afxanasyev2020">[Afxanasyev2020]</dt>
      <dd>
<span class="refAuthor">Afanasyev, A.</span>, <span class="refAuthor">Wang, L.</span>, <span class="refAuthor">Yeh, E.</span>, <span class="refAuthor">Zhang, B.</span>, and <span class="refAuthor">L. Zhang</span>, <span class="refTitle">"Identifying the Disease from the Symptoms: Lessons for Networking in the COVID-19 Era"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/12/IAB-COVID-19-WS_102820.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/12/IAB-COVID-19-WS_102820.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Arkko2020">[Arkko2020]</dt>
      <dd>
<span class="refAuthor">Arkko, J.</span>, <span class="refTitle">"Observations on Network User Behaviour During COVID-19"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-arkko.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-arkko.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="I-D.feamster-livingood-iab-covid19-workshop">[Bronzino2020]</dt>
      <dd>
<span class="refAuthor">Bronzino, F.</span>, <span class="refAuthor">Culley, E.</span>, <span class="refAuthor">Feamster, N.</span>, <span class="refAuthor">Liu, S.</span>, <span class="refAuthor">Livingood, J.</span>, and <span class="refAuthor">P. Schmitt</span>, <span class="refTitle">"IAB COVID-19 Workshop: Interconnection Changes in the United States"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-feamster-livingood-iab-covid19-workshop-01</span>, <time datetime="2020-10-28" class="refDate">28 October 2020</time>, <span>&lt;<a href="https://datatracker.ietf.org/doc/html/draft-feamster-livingood-iab-covid19-workshop-01">https://datatracker.ietf.org/doc/html/draft-feamster-livingood-iab-covid19-workshop-01</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Campling2020">[Campling2020]</dt>
      <dd>
<span class="refAuthor">Campling, A.</span> and <span class="refAuthor">D. Lazanski</span>, <span class="refTitle">"Will the Internet Still Be Resilient During the Next Black Swan Event?"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-campling.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-campling.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Cho2020">[Cho2020]</dt>
      <dd>
<span class="refAuthor">Cho, K.</span>, <span class="refTitle">"On the COVID-19 Impact to broadband traffic in Japan"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-cho.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-cho.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Clark2020">[Clark2020]</dt>
      <dd>
<span class="refAuthor">Clark, D.</span>, <span class="refTitle">"Measurement of congestion on ISP interconnection links"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-clark.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-clark.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Comcast2020">[Comcast2020]</dt>
      <dd>
<span class="refAuthor">Comcast</span>, <span class="refTitle">"COVID-19 Network Update"</span>, <time datetime="2020-05" class="refDate">May 2020</time>, <span>&lt;<a href="https://corporate.comcast.com/covid-19/network/may-20-2020">https://corporate.comcast.com/covid-19/network/may-20-2020</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="ConsumerlabReport2020">[ConsumerlabReport2020]</dt>
      <dd>
<span class="refAuthor">Ericsson ConsumerLab</span>, <span class="refTitle">"Connectivity in a COVID-19 world: Keeping consumers connected in a global crisis"</span>, <span>&lt;<a href="https://www.ericsson.com/en/reports-and-papers/consumerlab/reports/keeping-consumers-connected-during-the-covid-19-crisis">https://www.ericsson.com/en/reports-and-papers/consumerlab/reports/keeping-consumers-connected-during-the-covid-19-crisis</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Favale2020">[Favale2020]</dt>
      <dd>
<span class="refAuthor">Favale, T.</span>, <span class="refAuthor">Soro, F.</span>, <span class="refAuthor">Trevisan, M.</span>, <span class="refAuthor">Drago, I.</span>, and <span class="refAuthor">M. Mellia</span>, <span class="refTitle">"Campus traffic and e-Learning during COVID-19 pandemic"</span>, <span class="seriesInfo">DOI 10.1016/j.comnet.2020.107290</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-favale.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-favale.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Feldmann2020">[Feldmann2020]</dt>
      <dd>
<span class="refAuthor">Feldmann, A.</span>, <span class="refAuthor">Gasser, O.</span>, <span class="refAuthor">Lichtblau, F.</span>, <span class="refAuthor">Pujol, E.</span>, <span class="refAuthor">Poese, I.</span>, <span class="refAuthor">Dietzel, C.</span>, <span class="refAuthor">Wagner, D.</span>, <span class="refAuthor">Wichtlhuber, M.</span>, <span class="refAuthor">Tapiador, J.</span>, <span class="refAuthor">Vallina-Rodriguez, N.</span>, <span class="refAuthor">Hohlfeld, O.</span>, and <span class="refAuthor">G. Smaragdakis</span>, <span class="refTitle">"A view of Internet Traffic Shifts at ISP and IXPs during the COVID-19 Pandemic"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-feldmann.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-feldmann.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Fontugne2020">[Fontugne2020]</dt>
      <dd>
<span class="refAuthor">Fontugne, R.</span>, <span class="refAuthor">Shah, A.</span>, and <span class="refAuthor">K. Cho</span>, <span class="refTitle">"The Impact of COVID-19 on Last-mile Latency"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-fontugne.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-fontugne.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Fontugne2020-1">[Fontugne2020-1]</dt>
      <dd>
<span class="refAuthor">Fontugne, R.</span>, <span class="refAuthor">Shah, A.</span>, and <span class="refAuthor">K. Cho</span>, <span class="refTitle">"Persistent Last-mile Congestion: Not so Uncommon"</span>, <span class="refContent">Proceedings of the ACM Internet Measurement Conference (IMC '20)</span>, <span class="seriesInfo">DOI 10.1145/3419394.3423648</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://doi.org/10.1145/3419394.3423648">https://doi.org/10.1145/3419394.3423648</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Gillmor2020">[Gillmor2020]</dt>
      <dd>
<span class="refAuthor">Gillmor, D.</span>, <span class="refTitle">"Vaccines, Privacy, Software Updates, and Trust"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-gillmor.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-gillmor.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Gu2020">[Gu2020]</dt>
      <dd>
<span class="refAuthor">Gu, Y.</span> and <span class="refAuthor">Z. Li</span>, <span class="refTitle">"Covid 19 Impact on China ISP's Network Traffic Pattern and Solution Discussion"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-gu.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-gu.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Jennings2020">[Jennings2020]</dt>
      <dd>
<span class="refAuthor">Jennings, C.</span> and <span class="refAuthor">P. Kozanian</span>, <span class="refTitle">"WebEx Scaling During Covid"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-jennings.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-jennings.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Kirsty2020">[Kirsty2020]</dt>
      <dd>
<span class="refAuthor">Paine, K.</span>, <span class="refTitle">"IAB COVID-19 Network Impacts"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-kirstyp.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-kirstyp.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Lutu2020">[Lutu2020]</dt>
      <dd>
<span class="refAuthor">Lutu, A.</span>, <span class="refAuthor">Perino, D.</span>, <span class="refAuthor">Bagnulo, M.</span>, <span class="refAuthor">Frias-Martinez, E.</span>, and <span class="refAuthor">J. Khangosstar</span>, <span class="refTitle">"A Characterization of the COVID-19 Pandemic Impact on a Mobile Network Operator Traffic"</span>, <span class="seriesInfo">DOI 10.1145/3419394.3423655</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-lutu.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-lutu.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="McKinsey2020">[McKinsey2020]</dt>
      <dd>
<span class="refAuthor">Boland, B.</span>, <span class="refAuthor">De Smet, A.</span>, <span class="refAuthor">Palter, R.</span>, and <span class="refAuthor">A. Sanghvi</span>, <span class="refTitle">"Reimagining the office and work life after COVID-19"</span>, <time datetime="2020-06" class="refDate">June 2020</time>, <span>&lt;<a href="https://www.mckinsey.com/~/media/McKinsey/Business%20Functions/Organization/Our%20Insights/Reimagining%20the%20office%20and%20work%20life%20after%20COVID%2019/Reimagining-the-office-and-work-life-after-COVID-19-final.pdf">https://www.mckinsey.com/~/media/McKinsey/Business%20Functions/Organization/Our%20Insights/Reimagining%20the%20office%20and%20work%20life%20after%20COVID%2019/Reimagining-the-office-and-work-life-after-COVID-19-final.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Mok2020">[Mok2020]</dt>
      <dd>
<span class="refAuthor">Mok, R.</span> and <span class="refAuthor">kc. claffy</span>, <span class="refTitle">"Measuring the impact of COVID-19 on cloud network performance"</span>, <time datetime="2020-10" class="refDate">October 2020</time>, <span>&lt;<a href="https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-mok.pdf">https://www.iab.org/wp-content/IAB-uploads/2020/10/covid19-mok.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="NCTA2020">[NCTA2020]</dt>
      <dd>
<span class="refAuthor">NCTA</span>, <span class="refTitle">"COVID-19: How Cable's Internet Networks Are Performing: Metrics, Trends &amp; Observations"</span>, <span>&lt;<a href="https://www.ncta.com/COVIDdashboard">https://www.ncta.com/COVIDdashboard</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="Vodafone2020">[Vodafone2020]</dt>
      <dd>
<span class="refAuthor">Vodafone</span>, <span class="refTitle">"An update on Vodafone's networks"</span>, <time datetime="2020-04" class="refDate">April 2020</time>, <span>&lt;<a href="https://www.vodafone.com/covid19/news/update-on-vodafone-networks">https://www.vodafone.com/covid19/news/update-on-vodafone-networks</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="WorkplaceAnalytics2020">[WorkplaceAnalytics2020]</dt>
    <dd>
<span class="refAuthor">Lister, K.</span>, <span class="refTitle">"Work-at-Home After Covid-19--Our Forecast"</span>, <time datetime="2020-03" class="refDate">March 2020</time>, <span>&lt;<a href="https://globalworkplaceanalytics.com/work-at-home-after-covid-19-our-forecast">https://globalworkplaceanalytics.com/work-at-home-after-covid-19-our-forecast</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<div id="participants">
<section id="appendix-A">
      <h2 id="name-workshop-participants">
<a href="#appendix-A" class="section-number selfRef">Appendix A. </a><a href="#name-workshop-participants" class="section-name selfRef">Workshop Participants</a>
      </h2>
<p id="appendix-A-1">The following is an alphabetical list of participants in the workshop.<a href="#appendix-A-1" class="pilcrow">¶</a></p>
<ul class="normal">
<li class="normal" id="appendix-A-2.1">
          <p id="appendix-A-2.1.1"><span class="contact-name">Jari Arkko</span> (Ericsson/IAB)<a href="#appendix-A-2.1.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.2">
          <p id="appendix-A-2.2.1"><span class="contact-name">Ben Campbell</span> (Independent/IAB)<a href="#appendix-A-2.2.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.3">
          <p id="appendix-A-2.3.1"><span class="contact-name">Andrew Campling</span> (419 Consulting)<a href="#appendix-A-2.3.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.4">
          <p id="appendix-A-2.4.1"><span class="contact-name">Kenjiro Cho</span> (IIJ)<a href="#appendix-A-2.4.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.5">
          <p id="appendix-A-2.5.1"><span class="contact-name">kc claffy</span> (CAIDA)<a href="#appendix-A-2.5.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.6">
          <p id="appendix-A-2.6.1"><span class="contact-name">David Clark</span> (MIT CSAIL)<a href="#appendix-A-2.6.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.7">
          <p id="appendix-A-2.7.1"><span class="contact-name">Chris Dietzel</span> (DE-CIX)<a href="#appendix-A-2.7.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.8">
          <p id="appendix-A-2.8.1"><span class="contact-name">Idilio Drago</span> (University of Turin)<a href="#appendix-A-2.8.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.9">
          <p id="appendix-A-2.9.1"><span class="contact-name">Stephen Farrell</span> (Trinity College Dublin/IAB)<a href="#appendix-A-2.9.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.10">
          <p id="appendix-A-2.10.1"><span class="contact-name">Nick Feamster</span> (University of Chicago)<a href="#appendix-A-2.10.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.11">
          <p id="appendix-A-2.11.1"><span class="contact-name">Anja Feldmann</span> (Max Planck Institute for Informatics)<a href="#appendix-A-2.11.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.12">
          <p id="appendix-A-2.12.1"><span class="contact-name">Romain Fontugne</span> (IIJ Research Lab)<a href="#appendix-A-2.12.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.13">
          <p id="appendix-A-2.13.1"><span class="contact-name">Oliver Gasser</span> (Max Planck Institute for Informatics)<a href="#appendix-A-2.13.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.14">
          <p id="appendix-A-2.14.1"><span class="contact-name">Daniel Kahn Gillmor</span> (ACLU)<a href="#appendix-A-2.14.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.15">
          <p id="appendix-A-2.15.1"><span class="contact-name">Yunan Gu</span> (Huawei)<a href="#appendix-A-2.15.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.16">
          <p id="appendix-A-2.16.1"><span class="contact-name">Oliver Hohlfeld</span> (Brandenburg University of Technology (BTU))<a href="#appendix-A-2.16.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.17">
          <p id="appendix-A-2.17.1"><span class="contact-name">Jana Iyengar</span> (Fastly)<a href="#appendix-A-2.17.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.18">
          <p id="appendix-A-2.18.1"><span class="contact-name">Cullen Jennings</span> (Cisco/IAB)<a href="#appendix-A-2.18.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.19">
          <p id="appendix-A-2.19.1"><span class="contact-name">Mirja Kühlewind</span> (Ericsson/IAB)<a href="#appendix-A-2.19.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.20">
          <p id="appendix-A-2.20.1"><span class="contact-name">Dominique Lazanski</span><a href="#appendix-A-2.20.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.21">
          <p id="appendix-A-2.21.1"><span class="contact-name">Zhenbin Li</span> (Huawei/IAB)<a href="#appendix-A-2.21.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.22">
          <p id="appendix-A-2.22.1"><span class="contact-name">Franziska Lichtblau</span> (Max Planck Institute for Informatics)<a href="#appendix-A-2.22.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.23">
          <p id="appendix-A-2.23.1"><span class="contact-name">Jason Livingood</span> (Comcast)<a href="#appendix-A-2.23.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.24">
          <p id="appendix-A-2.24.1"><span class="contact-name">Andra Lutu</span> (Telefonica Research)<a href="#appendix-A-2.24.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.25">
          <p id="appendix-A-2.25.1"><span class="contact-name">Vesna Manojlovic</span> (RIPE NCC)<a href="#appendix-A-2.25.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.26">
          <p id="appendix-A-2.26.1"><span class="contact-name">Rüdiger Martin</span> (EC)<a href="#appendix-A-2.26.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.27">
          <p id="appendix-A-2.27.1"><span class="contact-name">Larry Masinter</span> (Retired)<a href="#appendix-A-2.27.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.28">
          <p id="appendix-A-2.28.1"><span class="contact-name">Matt Matthis</span> (Google)<a href="#appendix-A-2.28.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.29">
          <p id="appendix-A-2.29.1"><span class="contact-name">Jared Mauch</span> (Akamai/IAB)<a href="#appendix-A-2.29.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.30">
          <p id="appendix-A-2.30.1"><span class="contact-name">Deep Medhi</span> (NSF)<a href="#appendix-A-2.30.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.31">
          <p id="appendix-A-2.31.1"><span class="contact-name">Marco Mellia</span> (Politecnico di Torino)<a href="#appendix-A-2.31.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.32">
          <p id="appendix-A-2.32.1"><span class="contact-name">Ricky Mok</span> (CAIDA)<a href="#appendix-A-2.32.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.33">
          <p id="appendix-A-2.33.1"><span class="contact-name">Karen O'Donoghue</span> (Internet Society)<a href="#appendix-A-2.33.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.34">
          <p id="appendix-A-2.34.1"><span class="contact-name">Kirsty Paine</span> (NCSC)<a href="#appendix-A-2.34.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.35">
          <p id="appendix-A-2.35.1"><span class="contact-name">Diego Perino</span> (Telefonica Research)<a href="#appendix-A-2.35.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.36">
          <p id="appendix-A-2.36.1"><span class="contact-name">Colin Perkins</span> (University of Glasgow/IRTF/IAB)<a href="#appendix-A-2.36.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.37">
          <p id="appendix-A-2.37.1"><span class="contact-name">Enric Pujol</span> (Benocs)<a href="#appendix-A-2.37.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.38">
          <p id="appendix-A-2.38.1"><span class="contact-name">Anant Shah</span> (Verizon Media Platform)<a href="#appendix-A-2.38.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.39">
          <p id="appendix-A-2.39.1"><span class="contact-name">Francesca Soro</span> (Politecnico di Torino)<a href="#appendix-A-2.39.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.40">
          <p id="appendix-A-2.40.1"><span class="contact-name">Brian Trammell</span> (Google)<a href="#appendix-A-2.40.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.41">
          <p id="appendix-A-2.41.1"><span class="contact-name">Martino Trevisan</span><a href="#appendix-A-2.41.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.42">
          <p id="appendix-A-2.42.1"><span class="contact-name">Georgios Tselentis</span> (European Commission)<a href="#appendix-A-2.42.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.43">
          <p id="appendix-A-2.43.1"><span class="contact-name">Lan Wang</span> (University of Memphis)<a href="#appendix-A-2.43.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.44">
          <p id="appendix-A-2.44.1"><span class="contact-name">Rob Wilton</span> (Cisco)<a href="#appendix-A-2.44.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.45">
          <p id="appendix-A-2.45.1"><span class="contact-name">Jiankang Yao</span> (CNNIC)<a href="#appendix-A-2.45.1" class="pilcrow">¶</a></p>
</li>
        <li class="normal" id="appendix-A-2.46">
          <p id="appendix-A-2.46.1"><span class="contact-name">Lixia Zhang</span> (UCLA)<a href="#appendix-A-2.46.1" class="pilcrow">¶</a></p>
</li>
      </ul>
</section>
</div>
<section id="appendix-B">
      <h2 id="name-iab-members-at-the-time-of-">
<a href="#name-iab-members-at-the-time-of-" class="section-name selfRef">IAB Members at the Time of Approval</a>
      </h2>
<p id="appendix-B-1">Internet Architecture Board members at the time this document was approved for publication were:<a href="#appendix-B-1" class="pilcrow">¶</a></p>
<ul class="ulEmpty compact">
<li class="ulEmpty compact" id="appendix-B-2.1">
          <p id="appendix-B-2.1.1"><span class="contact-name">Jari Arkko</span><a href="#appendix-B-2.1.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.2">
          <p id="appendix-B-2.2.1"><span class="contact-name">Deborah Brungard</span><a href="#appendix-B-2.2.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.3">
          <p id="appendix-B-2.3.1"><span class="contact-name">Ben Campbell</span><a href="#appendix-B-2.3.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.4">
          <p id="appendix-B-2.4.1"><span class="contact-name">Lars Eggert</span><a href="#appendix-B-2.4.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.5">
          <p id="appendix-B-2.5.1"><span class="contact-name">Wes Hardaker</span><a href="#appendix-B-2.5.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.6">
          <p id="appendix-B-2.6.1"><span class="contact-name">Cullen Jennings</span><a href="#appendix-B-2.6.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.7">
          <p id="appendix-B-2.7.1"><span class="contact-name">Mirja Kühlewind</span><a href="#appendix-B-2.7.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.8">
          <p id="appendix-B-2.8.1"><span class="contact-name">Zhenbin Li</span><a href="#appendix-B-2.8.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.9">
          <p id="appendix-B-2.9.1"><span class="contact-name">Jared Mauch</span><a href="#appendix-B-2.9.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.10">
          <p id="appendix-B-2.10.1"><span class="contact-name">Tommy Pauly</span><a href="#appendix-B-2.10.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.11">
          <p id="appendix-B-2.11.1"><span class="contact-name">David Schinazi</span><a href="#appendix-B-2.11.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.12">
          <p id="appendix-B-2.12.1"><span class="contact-name">Russ White</span><a href="#appendix-B-2.12.1" class="pilcrow">¶</a></p>
</li>
        <li class="ulEmpty compact" id="appendix-B-2.13">
          <p id="appendix-B-2.13.1"><span class="contact-name">Jiankang Yao</span><a href="#appendix-B-2.13.1" class="pilcrow">¶</a></p>
</li>
      </ul>
</section>
<div id="acknowledgments">
<section id="appendix-C">
      <h2 id="name-acknowledgments">
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
      </h2>
<p id="appendix-C-1">The authors would like to thank the workshop participants, the members
of the IAB, the program committee, the participants in the architecture discussion list
for the interesting discussions, and <span class="contact-name">Cindy Morgan</span> for the practical
arrangements.<a href="#appendix-C-1" class="pilcrow">¶</a></p>
<p id="appendix-C-2">Further special thanks to those participants who also
      contributed to this report: <span class="contact-name">Romain       Fontugne</span> provided text based on his blog post at
      <span>&lt;<a href="https://eng-blog.iij.ad.jp/archives/7722">https://eng-blog.iij.ad.jp/archives/7722</a>&gt;</span>; <span class="contact-name">Ricky Mok</span> for text on cloud platforms; <span class="contact-name">Martino Trevisan</span> for text on campus networks;
      <span class="contact-name">David Clark</span> on congestion measurements at
      interconnects; <span class="contact-name">Oliver Hohlfeld</span> for the text on traffic growth,
      changes in traffic shifts, campus networks, and
      interconnections; <span class="contact-name">Andra Lutu</span> on mobile networks; and <span class="contact-name">Kirsty Paine</span>
      for text on security impacts. Thanks to <span class="contact-name">Jason Livingood</span> for
      his review and additions.<a href="#appendix-C-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="appendix-D">
      <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Jari Arkko</span></div>
<div dir="auto" class="left"><span class="org">Ericsson</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:jari.arkko@ericsson.com" class="email">jari.arkko@ericsson.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Stephen Farrell</span></div>
<div dir="auto" class="left"><span class="org">Trinity College Dublin</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:stephen.farrell@cs.tcd.ie" class="email">stephen.farrell@cs.tcd.ie</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Mirja Kühlewind</span></div>
<div dir="auto" class="left"><span class="org">Ericsson</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:mirja.kuehlewind@ericsson.com" class="email">mirja.kuehlewind@ericsson.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Colin Perkins</span></div>
<div dir="auto" class="left"><span class="org">University of Glasgow</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:csp@csperkins.org" class="email">csp@csperkins.org</a>
</div>
</address>
</section>
</div>
<script>const toc = document.getElementById("toc");
toc.querySelector("h2").addEventListener("click", e => {
  toc.classList.toggle("active");
});
toc.querySelector("nav").addEventListener("click", e => {
  toc.classList.remove("active");
});
</script>
</body>
</html>