CINXE.COM

<!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 9446: Reflections on Ten Years Past the Snowden Revelations</title> <meta content="Stephen Farrell" name="author"> <meta content="Farzaneh Badii" name="author"> <meta content="Bruce Schneier" name="author"> <meta content="Steven M. Bellovin" name="author"> <meta content=" This memo contains the thoughts and recountings of events that transpired during and after the release of information about the United States National Security Agency (NSA) by Edward Snowden in 2013. There are four perspectives: that of someone who was involved with sifting through the information to responsibly inform the public, that of a security area director of the IETF, that of a human rights expert, and that of a computer science and affiliate law professor. The purpose of this memo is to provide some historical perspective, while at the same time offering a view as to what security and privacy challenges the technical community should consider. These essays do not represent a consensus view, but that of the individual authors. " name="description"> <meta content="xml2rfc 3.17.4" name="generator"> <meta content="pervasive monitoring" name="keyword"> <meta content="privacy" name="keyword"> <meta content="security" name="keyword"> <meta content="9446" name="rfc.number">  <link href="rfc9446.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 necessary 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 */ :root { --font-sans: 'Noto Sans', Arial, Helvetica, sans-serif; --font-serif: 'Noto Serif', 'Times', 'Times New Roman', serif; --font-mono: 'Roboto Mono', Courier, 'Courier New', monospace; } @viewport { zoom: 1.0; } @-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: var(--font-sans); 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; } svg[font-family~="serif" i], svg [font-family~="serif" i] { font-family: var(--font-serif); } svg[font-family~="sans-serif" i], svg [font-family~="sans-serif" i] { font-family: var(--font-sans); } svg[font-family~="monospace" i], svg [font-family~="monospace" i] { font-family: var(--font-mono); } .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 { display: table; border: none; 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, .iref + a[href].internal { color: #222; } /* XXX probably not this: a.selfRef:hover { background-color: transparent; cursor: default; } */ /* Figures */ tt, code, pre { background-color: #f9f9f9; font-family: var(--font-mono); } 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; } /* Fix PDF info block run off issue */ @media print { #identifiers dd { float: none; } } #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: var(--font-sans); 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; } .breakable pre { break-inside: auto; } 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 following 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 { font-size: 95%; } /* Fix the height/width aspect for ascii art*/ .sourcecode pre, .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 information 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, .artwork > pre, .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 slightly */ table { border: 1px solid #ddd; } td { border-top: 1px solid #ddd; } tr { break-inside: avoid; } 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: auto; 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 bottom 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 compact 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.sourcecode:first-child, 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:only-child { margin-bottom: 0; } </style> <link href="rfc-local.css" rel="stylesheet" type="text/css"> <link href="https://dx.doi.org/10.17487/rfc9446" rel="alternate"> <link href="urn:issn:2070-1721" rel="alternate"> <link href="https://datatracker.ietf.org/doc/draft-farrell-tenyearsafter-05" rel="prev"> </head> <body class="xml2rfc"> <script src="https://www.rfc-editor.org/js/metadata.min.js"></script> <table class="ears"> <thead><tr> <td class="left">RFC 9446</td> <td class="center">Ten Years After</td> <td class="right">July 2023</td> </tr></thead> <tfoot><tr> <td class="left">Farrell, 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">Independent Submission</dd> <dt class="label-rfc">RFC:</dt> <dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc9446" class="eref">9446</a></dd> <dt class="label-category">Category:</dt> <dd class="category">Informational</dd> <dt class="label-published">Published:</dt> <dd class="published"> <time datetime="2023-07" class="published">July 2023</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">S. Farrell</div> <div class="org">Trinity College, Dublin</div> </div> <div class="author"> <div class="author-name">F. Badii</div> <div class="org">Digital Medusa</div> </div> <div class="author"> <div class="author-name">B. Schneier</div> <div class="org">Harvard University</div> </div> <div class="author"> <div class="author-name">S. M. Bellovin</div> <div class="org">Columbia University</div> </div> </dd> </dl> </div> <h1 id="rfcnum">RFC 9446</h1> <h1 id="title">Reflections on Ten Years Past the Snowden Revelations</h1> <section id="section-abstract"> <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> This memo contains the thoughts and recountings of events that transpired during and after the release of information about the United States National Security Agency (NSA) by Edward Snowden in 2013. There are four perspectives: that of someone who was involved with sifting through the information to responsibly inform the public, that of a security area director of the IETF, that of a human rights expert, and that of a computer science and affiliate law professor. The purpose of this memo is to provide some historical perspective, while at the same time offering a view as to what security and privacy challenges the technical community should consider. These essays do not represent a consensus view, but that of the individual authors.<a href="#section-abstract-1" class="pilcrow">¶</a> </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> This document is not an Internet Standards Track specification; it is published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a> This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not candidates for any level of Internet Standard; see Section 2 of RFC 7841.<a href="#section-boilerplate.1-2" class="pilcrow">¶</a> Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at <a href="https://www.rfc-editor.org/info/rfc9446">https://www.rfc-editor.org/info/rfc9446</a>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a> </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> Copyright (c) 2023 IETF Trust and the persons identified as the document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a> This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) 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> </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="compact toc ulBare ulEmpty"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1"> <a href="#section-1" class="auto internal xref">1</a>. <a href="#name-introduction" class="internal xref">Introduction</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2"> <a href="#section-2" class="auto internal xref">2</a>. <a href="#name-bruce-schneier-snowden-ten-" class="internal xref">Bruce Schneier: Snowden Ten Years Later</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3"> <a href="#section-3" class="auto internal xref">3</a>. <a href="#name-stephen-farrell-ietf-and-in" class="internal xref">Stephen Farrell: IETF and Internet Technical Community Reaction</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4"> <a href="#section-4" class="auto internal xref">4</a>. <a href="#name-farzaneh-badii-did-snowdens" class="internal xref">Farzaneh Badii: Did Snowden's Revelations Help with Protecting Human Rights on the Internet?</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5"> <a href="#section-5" class="auto internal xref">5</a>. <a href="#name-steven-m-bellovin-governmen" class="internal xref">Steven M. Bellovin: Governments and Cryptography: The Crypto Wars</a> <ul class="compact toc ulBare ulEmpty"> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1"> <a href="#section-5.1" class="auto internal xref">5.1</a>. <a href="#name-historical-background" class="internal xref">Historical Background</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.2"> <a href="#section-5.2" class="auto internal xref">5.2</a>. <a href="#name-the-crypto-wars-begin" class="internal xref">The Crypto Wars Begin</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.3"> <a href="#section-5.3" class="auto internal xref">5.3</a>. <a href="#name-the-battle-is-joined" class="internal xref">The Battle Is Joined</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.4"> <a href="#section-5.4" class="auto internal xref">5.4</a>. <a href="#name-the-hidden-battle" class="internal xref">The Hidden Battle</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.5"> <a href="#section-5.5" class="auto internal xref">5.5</a>. <a href="#name-whither-the-ietf" class="internal xref">Whither the IETF?</a> </li> </ul> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6"> <a href="#section-6" class="auto internal xref">6</a>. <a href="#name-security-considerations" class="internal xref">Security Considerations</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7"> <a href="#section-7" class="auto internal xref">7</a>. <a href="#name-iana-considerations" class="internal xref">IANA Considerations</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8"> <a href="#section-8" class="auto internal xref">8</a>. <a href="#name-informative-references" class="internal xref">Informative References</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9"> <a href="#appendix-A" class="auto internal xref"></a><a href="#name-acknowledgments" class="internal xref">Acknowledgments</a> </li> <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10"> <a href="#appendix-B" class="auto internal xref"></a><a href="#name-authors-addresses" class="internal xref">Authors' Addresses</a> </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> On June 6th, 2013, an article appeared in The Guardian [<a href="#Guard2013" class="cite xref">Guard2013</a>] that was the beginning of a series of what have come to be known as the Snowden revelations, describing certain activities of the United States National Security Agency (NSA). These activities included, amongst others: secret court orders; secret agreements for the receipt of so-called "meta-information" that includes source, destination, and timing of communications; and tapping of communications lines. The breathtaking scope of the operations shocked the Internet technical community and resulted in a sea change within the IETF, IAB, and other standards organizations.<a href="#section-1-1" class="pilcrow">¶</a> Now that some years have passed, it seems appropriate to reflect on that period of time and to consider what effect the community's actions had, where security has improved, how the threat surface has evolved, what areas haven't improved, and where the community might invest future efforts.<a href="#section-1-2" class="pilcrow">¶</a> Bruce Schneier begins this compendium of individual essays by bringing us back to 2013, recalling how it was for him and others to report what was happening, and the mindset of those involved. Next, Stephen Farrell reviews the technical community's reactions and in particular the reactions of the IETF community, technical advances, and where threats remain. Then Farzaneh Badii discusses the impact of those advances -- or lack thereof -- on human rights. Finally Steven M. Bellovin puts the Snowden revelations into an ever-evolving historical context of secrets and secret stealing that spans centuries, closing with some suggestions for IETF.<a href="#section-1-3" class="pilcrow">¶</a> Readers are invited to consider what impact we as a community have had, what challenges remain, and what positive contribution the technical community can and should make to address security and privacy of citizens of the world.<a href="#section-1-4" class="pilcrow">¶</a> -- Eliot Lear, Independent Submissions Editor for the RFC Series<a href="#section-1-5" class="pilcrow">¶</a> </section> </div> <div id="bruce-schneier-snowden-ten-years-later"> <section id="section-2"> <h2 id="name-bruce-schneier-snowden-ten-"> <a href="#section-2" class="section-number selfRef">2. </a><a href="#name-bruce-schneier-snowden-ten-" class="section-name selfRef">Bruce Schneier: Snowden Ten Years Later</a> </h2> In 2013 and 2014, I wrote extensively about new revelations regarding NSA surveillance based on the documents provided by Edward Snowden. But I had a more personal involvement as well.<a href="#section-2-1" class="pilcrow">¶</a> I wrote the essay below in September 2013. The New Yorker agreed to publish it, but The Guardian asked me not to. It was scared of UK law enforcement and worried that this essay would reflect badly on it. And given that the UK police would raid its offices in July 2014, it had legitimate cause to be worried.<a href="#section-2-2" class="pilcrow">¶</a> Now, ten years later, I offer this as a time capsule of what those early months of Snowden were like.<a href="#section-2-3" class="pilcrow">¶</a> <blockquote id="section-2-4"> It's a surreal experience, paging through hundreds of top-secret NSA documents. You're peering into a forbidden world: strange, confusing, and fascinating all at the same time.<a href="#section-2-4.1" class="pilcrow">¶</a> I had flown down to Rio de Janeiro in late August at the request of Glenn Greenwald. He had been working on the Edward Snowden archive for a couple of months, and had a pile of more technical documents that he wanted help interpreting. According to Greenwald, Snowden also thought that bringing me down was a good idea.<a href="#section-2-4.2" class="pilcrow">¶</a> It made sense. I didn't know either of them, but I have been writing about cryptography, security, and privacy for decades. I could decipher some of the technical language that Greenwald had difficulty with, and understand the context and importance of various document. And I have long been publicly critical of the NSA's eavesdropping capabilities. My knowledge and expertise could help figure out which stories needed to be reported.<a href="#section-2-4.3" class="pilcrow">¶</a> I thought about it a lot before agreeing. This was before David Miranda, Greenwald's partner, was detained at Heathrow airport by the UK authorities; but even without that, I knew there was a risk. I fly a lot -- a quarter of a million miles per year -- and being put on a TSA list, or being detained at the US border and having my electronics confiscated, would be a major problem. So would the FBI breaking into my home and seizing my personal electronics. But in the end, that made me more determined to do it.<a href="#section-2-4.4" class="pilcrow">¶</a> I did spend some time on the phone with the attorneys recommended to me by the ACLU and the EFF. And I talked about it with my partner, especially when Miranda was detained three days before my departure. Both Greenwald and his employer, The Guardian, are careful about whom they show the documents to. They publish only those portions essential to getting the story out. It was important to them that I be a co-author, not a source. I didn't follow the legal reasoning, but the point is that The Guardian doesn't want to leak the documents to random people. It will, however, write stories in the public interest, and I would be allowed to review the documents as part of that process. So after a Skype conversation with someone at The Guardian, I signed a letter of engagement.<a href="#section-2-4.5" class="pilcrow">¶</a> And then I flew to Brazil.<a href="#section-2-4.6" class="pilcrow">¶</a> I saw only a tiny slice of the documents, and most of what I saw was surprisingly banal. The concerns of the top-secret world are largely tactical: system upgrades, operational problems owing to weather, delays because of work backlogs, and so on. I paged through weekly reports, presentation slides from status meetings, and general briefings to educate visitors. Management is management, even inside the NSA. Reading the documents, I felt as though I were sitting through some of those endless meetings.<a href="#section-2-4.7" class="pilcrow">¶</a> The meeting presenters try to spice things up. Presentations regularly include intelligence success stories. There were details -- what had been found, and how, and where it helped -- and sometimes there were attaboys from "customers" who used the intelligence. I'm sure these are intended to remind NSA employees that they're doing good. It definitely had an effect on me. Those were all things I want the NSA to be doing.<a href="#section-2-4.8" class="pilcrow">¶</a> There were so many code names. Everything has one: every program, every piece of equipment, every piece of software. Sometimes code names had their own code names. The biggest secrets seem to be the underlying real-world information: which particular company MONEYROCKET is; what software vulnerability EGOTISTICALGIRAFFE -- really, I am not making that one up -- is; how TURBINE works. Those secrets collectively have a code name -- ECI, for exceptionally compartmented information -- and almost never appear in the documents. Chatting with Snowden on an encrypted IM connection, I joked that the NSA cafeteria menu probably has code names for menu items. His response: "Trust me when I say you have no idea."<a href="#section-2-4.9" class="pilcrow">¶</a> Those code names all come with logos, most of them amateurish and a lot of them dumb. Note to the NSA: take some of that more than ten-billion-dollar annual budget and hire yourself a design firm. Really; it'll pay off in morale.<a href="#section-2-4.10" class="pilcrow">¶</a> Once in a while, though, I would see something that made me stop, stand up, and pace around in circles. It wasn't that what I read was particularly exciting, or important. It was just that it was startling. It changed -- ever so slightly -- how I thought about the world.<a href="#section-2-4.11" class="pilcrow">¶</a> Greenwald said that that reaction was normal when people started reading through the documents.<a href="#section-2-4.12" class="pilcrow">¶</a> Intelligence professionals talk about how disorienting it is living on the inside. You read so much classified information about the world's geopolitical events that you start seeing the world differently. You become convinced that only the insiders know what's really going on, because the news media is so often wrong. Your family is ignorant. Your friends are ignorant. The world is ignorant. The only thing keeping you from ignorance is that constant stream of classified knowledge. It's hard not to feel superior, not to say things like "If you only knew what we know" all the time. I can understand how General Keith Alexander, the director of the NSA, comes across as so supercilious; I only saw a minute fraction of that secret world, and I started feeling it.<a href="#section-2-4.13" class="pilcrow">¶</a> It turned out to be a terrible week to visit Greenwald, as he was still dealing with the fallout from Miranda's detention. Two other journalists, one from The Nation and the other from The Hindu, were also in town working with him. A lot of my week involved Greenwald rushing into my hotel room, giving me a thumb drive of new stuff to look through, and rushing out again.<a href="#section-2-4.14" class="pilcrow">¶</a> A technician from The Guardian got a search capability working while I was there, and I spent some time with it. Question: when you're given the capability to search through a database of NSA secrets, what's the first thing you look for? Answer: your name.<a href="#section-2-4.15" class="pilcrow">¶</a> It wasn't there. Neither were any of the algorithm names I knew, not even algorithms I knew that the US government used.<a href="#section-2-4.16" class="pilcrow">¶</a> I tried to talk to Greenwald about his own operational security. It had been incredibly stupid for Miranda to be traveling with NSA documents on the thumb drive. Transferring files electronically is what encryption is for. I told Greenwald that he and Laura Poitras should be sending large encrypted files of dummy documents back and forth every day.<a href="#section-2-4.17" class="pilcrow">¶</a> Once, at Greenwald's home, I walked into the backyard and looked for TEMPEST receivers hiding in the trees. I didn't find any, but that doesn't mean they weren't there. Greenwald has a lot of dogs, but I don't think that would hinder professionals. I'm sure that a bunch of major governments have a complete copy of everything Greenwald has. Maybe the black bag teams bumped into each other in those early weeks.<a href="#section-2-4.18" class="pilcrow">¶</a> I started doubting my own security procedures. Reading about the NSA's hacking abilities will do that to you. Can it break the encryption on my hard drive? Probably not. Has the company that makes my encryption software deliberately weakened the implementation for it? Probably. Are NSA agents listening in on my calls back to the US? Very probably. Could agents take control of my computer over the Internet if they wanted to? Definitely. In the end, I decided to do my best and stop worrying about it. It was the agency's documents, after all. And what I was working on would become public in a few weeks.<a href="#section-2-4.19" class="pilcrow">¶</a> I wasn't sleeping well, either. A lot of it was the sheer magnitude of what I saw. It's not that any of it was a real surprise. Those of us in the information security community had long assumed that the NSA was doing things like this. But we never really sat down and figured out the details, and to have the details confirmed made a big difference. Maybe I can make it clearer with an analogy. Everyone knows that death is inevitable; there's absolutely no surprise about that. Yet it arrives as a surprise, because we spend most of our lives refusing to think about it. The NSA documents were a bit like that. Knowing that it is surely true that the NSA is eavesdropping on the world, and doing it in such a methodical and robust manner, is very different from coming face-to-face with the reality that it is and the details of how it is doing it.<a href="#section-2-4.20" class="pilcrow">¶</a> I also found it incredibly difficult to keep the secrets. The Guardian's process is slow and methodical. I move much faster. I drafted stories based on what I found. Then I wrote essays about those stories, and essays about the essays. Writing was therapy; I would wake up in the wee hours of the morning, and write an essay. But that put me at least three levels beyond what was published.<a href="#section-2-4.21" class="pilcrow">¶</a> Now that my involvement is out, and my first essays are out, I feel a lot better. I'm sure it will get worse again when I find another monumental revelation; there are still more documents to go through.<a href="#section-2-4.22" class="pilcrow">¶</a> I've heard it said that Snowden wants to damage America. I can say with certainty that he does not. So far, everyone involved in this incident has been incredibly careful about what is released to the public. There are many documents that could be immensely harmful to the US, and no one has any intention of releasing them. The documents the reporters release are carefully redacted. Greenwald and I repeatedly debated with The Guardian editors the newsworthiness of story ideas, stressing that we would not expose government secrets simply because they're interesting.<a href="#section-2-4.23" class="pilcrow">¶</a> The NSA got incredibly lucky; this could have ended with a massive public dump like Chelsea Manning's State Department cables. I suppose it still could. Despite that, I can imagine how this feels to the NSA. It's used to keeping this stuff behind multiple levels of security: gates with alarms, armed guards, safe doors, and military-grade cryptography. It's not supposed to be on a bunch of thumb drives in Brazil, Germany, the UK, the US, and who knows where else, protected largely by some random people's opinions about what should or should not remain secret. This is easily the greatest intelligence failure in the history of ever. It's amazing that one person could have had so much access with so little accountability, and could sneak all of this data out without raising any alarms. The odds are close to zero that Snowden is the first person to do this; he's just the first person to make public that he did. It's a testament to General Alexander's power that he hasn't been forced to resign.<a href="#section-2-4.24" class="pilcrow">¶</a> It's not that we weren't being careful about security, it's that our standards of care are so different. From the NSA's point of view, we're all major security risks, myself included. I was taking notes about classified material, crumpling them up, and throwing them into the wastebasket. I was printing documents marked "TOP SECRET/COMINT/NOFORN" in a hotel lobby. And once, I took the wrong thumb drive with me to dinner, accidentally leaving the unencrypted one filled with top-secret documents in my hotel room. It was an honest mistake; they were both blue.<a href="#section-2-4.25" class="pilcrow">¶</a> If I were an NSA employee, the policy would be to fire me for that alone.<a href="#section-2-4.26" class="pilcrow">¶</a> Many have written about how being under constant surveillance changes a person. When you know you're being watched, you censor yourself. You become less open, less spontaneous. You look at what you write on your computer and dwell on what you've said on the telephone, wonder how it would sound taken out of context, from the perspective of a hypothetical observer. You're more likely to conform. You suppress your individuality. Even though I have worked in privacy for decades, and already knew a lot about the NSA and what it does, the change was palpable. That feeling hasn't faded. I am now more careful about what I say and write. I am less trusting of communications technology. I am less trusting of the computer industry.<a href="#section-2-4.27" class="pilcrow">¶</a> After much discussion, Greenwald and I agreed to write three stories together to start. All of those are still in progress. In addition, I wrote two commentaries on the Snowden documents that were recently made public. There's a lot more to come; even Greenwald hasn't looked through everything.<a href="#section-2-4.28" class="pilcrow">¶</a> Since my trip to Brazil (one month before), I've flown back to the US once and domestically seven times -- all without incident. I'm not on any list yet. At least, none that I know about.<a href="#section-2-4.29" class="pilcrow">¶</a> </blockquote> As it happened, I didn't write much more with Greenwald or The Guardian. Those two had a falling out, and by the time everything settled and both began writing about the documents independently -- Greenwald at the newly formed website The Intercept -- I got cut out of the process somehow. I remember hearing that Greenwald was annoyed with me, but I never learned the reason. We haven't spoken since.<a href="#section-2-5" class="pilcrow">¶</a> Still, I was happy with the one story I was part of: how the NSA hacks Tor. I consider it a personal success that I pushed The Guardian to publish NSA documents detailing QUANTUM. I don't think that would have gotten out any other way. And I still use those pages today when I teach cybersecurity to policymakers at the Harvard Kennedy School.<a href="#section-2-6" class="pilcrow">¶</a> Other people wrote about the Snowden files, and wrote a lot. It was a slow trickle at first, and then a more consistent flow. Between Greenwald, Bart Gellman, and The Guardian reporters, there ended up being steady stream of news. (Bart brought in Ashkan Soltani to help him with the technical aspects, which was a great move on his part, even if it cost Ashkan a government job later.) More stories were covered by other publications.<a href="#section-2-7" class="pilcrow">¶</a> It started getting weird. Both Greenwald and Gellman held documents back so they could publish them in their books. Jake Appelbaum, who had not yet been accused of sexual assault by multiple women, was working with Poitras. He partnered with Der Spiegel to release an implant catalog from the NSA's Tailored Access Operations group. To this day, I am convinced that the document was not in the Snowden archives: that Jake got it somehow, and it was released with the implication that it was from Edward Snowden. I thought it was important enough that I started writing about each item in that document in my blog: "NSA Exploit of the Week." That got my website blocked by the DoD: I keep a framed print of the censor's message on my wall.<a href="#section-2-8" class="pilcrow">¶</a> Perhaps the most surreal document disclosures were when artists started writing fiction based on the documents. This was in 2016, when Laura Poitras built a secure room in New York to house the documents. By then, the documents were years out of date. And now they're over a decade out of date. (They were leaked in 2013, but most of them were from 2012 or before.)<a href="#section-2-9" class="pilcrow">¶</a> I ended up being something of a public ambassador for the documents. When I got back from Rio, I gave talks at a private conference in Woods Hole, the Berkman Center at Harvard, something called the Congress on Privacy and Surveillance in Geneva, events at both CATO and New America in DC, an event at the University of Pennsylvania, an event at EPIC, a "Stop Watching Us" rally in DC, the RISCS conference in London, the ISF in Paris, and...then...at the IETF meeting in Vancouver in November 2013. (I remember little of this; I am reconstructing it all from my calendar.)<a href="#section-2-10" class="pilcrow">¶</a> What struck me at the IETF was the indignation in the room, and the calls to action. And there was action, across many fronts. We technologists did a lot to help secure the Internet, for example.<a href="#section-2-11" class="pilcrow">¶</a> The government didn't do its part, though. Despite the public outcry, investigations by Congress, pronouncements by President Obama, and federal court rulings, I don't think much has changed. The NSA canceled a program here and a program there, and it is now more public about defense. But I don't think it is any less aggressive about either bulk or targeted surveillance. Certainly its government authorities haven't been restricted in any way. And surveillance capitalism is still the business model of the Internet.<a href="#section-2-12" class="pilcrow">¶</a> And Edward Snowden? We were in contact for a while on Signal. I visited him once in Moscow, in 2016. And I had him do a guest lecture to my class at Harvard for a few years, remotely by Jitsi. Afterwards, I would hold a session where I promised to answer every question he would evade or not answer, explain every response he did give, and be candid in a way that someone with an outstanding arrest warrant simply cannot. Sometimes I thought I could channel Snowden better than he could.<a href="#section-2-13" class="pilcrow">¶</a> But now it's been a decade. Everything he knows is old and out of date. Everything we know is old and out of date. The NSA suffered an even worse leak of its secrets by the Russians, under the guise of the Shadow Brokers, in 2016 and 2017. The NSA has rebuilt. It again has capabilities we can only surmise.<a href="#section-2-14" class="pilcrow">¶</a> </section> </div> <div id="stephen-farrell-ietf-and-internet-technical-community-reaction"> <section id="section-3"> <h2 id="name-stephen-farrell-ietf-and-in"> <a href="#section-3" class="section-number selfRef">3. </a><a href="#name-stephen-farrell-ietf-and-in" class="section-name selfRef">Stephen Farrell: IETF and Internet Technical Community Reaction</a> </h2> In 2013, the IETF and, more broadly, the Internet technical, security, and privacy research communities, were surprised by the surveillance and attack efforts exposed by the Snowden revelations [<a href="#Timeline" class="cite xref">Timeline</a>]. While the potential for such was known, it was the scale and pervasiveness of the activities disclosed that was alarming and, I think it fair to say, quite annoying, for very many Internet engineers.<a href="#section-3-1" class="pilcrow">¶</a> As for the IETF's reaction, informal meetings during the July 2013 IETF meeting in Berlin indicated that IETF participants considered that these revelations showed that we needed to do more to improve the security and privacy properties of IETF protocols, and to help ensure deployments made better use of the security and privacy mechanisms that already existed. In August, the IETF set up a new mailing list [<a href="#Perpass" class="cite xref">Perpass</a>], which became a useful venue for triaging proposals for work on these topics. At the November 2013 IETF meeting, there was a lively and very well attended plenary session [<a href="#Plenary-video" class="cite xref">Plenary-video</a>] on "hardening the Internet" against such attacks, followed by a "birds of a feather" session [<a href="#Perpass-BoF" class="cite xref">Perpass-BoF</a>] devoted to more detailed discussion of possible actions in terms of new working groups, protocols, and Best Current Practice (BCP) documents that could help improve matters. This was followed in February/March 2014 by a joint IAB/W3C workshop on "strengthening the Internet against pervasive monitoring" [<a href="#STRINT" class="cite xref">STRINT</a>] held in London and attended by 150 engineers (still the only IAB workshop in my experience where we needed a waiting list for people after capacity for the venue was reached!). The STRINT workshop report was eventually published as [<a href="#RFC7687" class="cite xref">RFC7687</a>] in 2015, but in the meantime, work proceeded on a BCP document codifying that the IETF community considered that "pervasive monitoring is an attack" [<a href="#RFC7258" class="cite xref">RFC7258</a>] (aka BCP 188). The IETF Last Call discussion for that short document included more than 1000 emails -- while there was broad agreement on the overall message, a number of IETF participants considered enshrining that message in the RFC Series and IETF processes controversial. In any case, the BCP was published in May 2014. The key statement on which rough consensus was reached is in the abstract of RFC 7258 and says "Pervasive monitoring is a technical attack that should be mitigated in the design of IETF protocols, where possible." That document has since been referenced [<a href="#Refs-to-7258" class="cite xref">Refs-to-7258</a>] by many IETF working groups and RFCs as justifying additional work on security and privacy. Throughout that period and beyond, the repercussions of the Snowden revelations remained a major and ongoing agenda item for both of the IETF's main technical management bodies, the IAB and the IESG (on which I served at the time).<a href="#section-3-2" class="pilcrow">¶</a> So far, I've only described the processes with which the IETF dealt with the attacks, but there was, of course, also much technical work started by IETF participants that was at least partly motivated by the Snowden revelations.<a href="#section-3-3" class="pilcrow">¶</a> In November 2013, a working group was established to document better practices for using TLS in applications [<a href="#UTA" class="cite xref">UTA</a>] so that deployments would be less at risk in the face of some of the attacks related to stripping TLS or having applications misuse TLS APIs or parameters. Similar work was done later to update recommendations for use of cryptography in other protocols in the CURDLE Working Group [<a href="#CURDLE" class="cite xref">CURDLE</a>]. The CURDLE Working Group was, to an extent, created to enable use of a set of new elliptic curves that had been documented by the IRTF Crypto Forum Research Group [<a href="#CFRG" class="cite xref">CFRG</a>]. That work in turn had been partly motivated by (perhaps ultimately unfounded) concerns about elliptic curves defined in NIST standards, following the DUAL_EC_DRBG debacle [<a href="#Dual-EC" class="cite xref">Dual-EC</a>] (described further below) where a NIST random number generator had been deliberately engineered to produce output that could be vulnerable to NSA attack.<a href="#section-3-4" class="pilcrow">¶</a> Work to develop a new version of TLS was started in 2014, mainly due to concerns that TLS 1.2 and earlier version implementations had been shown to be vulnerable to a range of attacks over the years. The work to develop TLS 1.3 [<a href="#RFC8446" class="cite xref">RFC8446</a>] also aimed to encrypt more of the handshake so as to expose less information to network observers -- a fairly direct result of the Snowden revelations. Work to further improve TLS in this respect continues today using the so-called Encrypted Client Hello (ECH) mechanism [<a href="#I-D.ietf-tls-esni" class="cite xref">TLS-ECH</a>] to remove one of the last privacy leaks present in current TLS.<a href="#section-3-5" class="pilcrow">¶</a> Work on ECH was enabled by significant developments to encrypt DNS traffic, using DNS over TLS (DoT) [<a href="#RFC7858" class="cite xref">RFC7858</a>] or DNS Queries over HTTPS (DoH) [<a href="#RFC8484" class="cite xref">RFC8484</a>], which also started as a result of the Snowden revelations. Prior to that, privacy hadn't really been considered when it came to DNS data or (more importantly) the act of accessing DNS data. The trend towards encrypting DNS traffic represents a significant change for the Internet, both in terms of reducing cleartext, but also in terms of moving points-of-control. The latter aspect was, and remains, controversial, but the IETF did its job of defining new protocols that can enable better DNS privacy. Work on HTTP version 2 [<a href="#RFC9113" class="cite xref">RFC9113</a>] and QUIC [<a href="#RFC9000" class="cite xref">RFC9000</a>] further demonstrates the trend in the IETF towards always encrypting protocols as the new norm, at least at and above the transport layer.<a href="#section-3-6" class="pilcrow">¶</a> Of course, not all such initiatives bore fruit; for example, attempts to define a new MPLS encryption mechanism [<a href="#I-D.ietf-mpls-opportunistic-encrypt" class="cite xref">MPLS-OPPORTUNISTIC-ENCRYPT</a>] foundered due to a lack of interest and the existence of the already deployed IEEE Media Access Control Security (MACsec) scheme. But there has been a fairly clear trend towards trying to remove cleartext from the Internet as a precursor to provide improved privacy when considering network observers as attackers.<a href="#section-3-7" class="pilcrow">¶</a> The IETF, of course, forms only one part of the broader Internet technical community, and there were many non-IETF activities triggered by the Snowden revelations, a number of which also eventually resulted in new IETF work to standardise better security and privacy mechanisms developed elsewhere.<a href="#section-3-8" class="pilcrow">¶</a> In 2013, the web was largely unencrypted despite HTTPS being relatively usable, and that was partly due to problems using the Web PKI at scale. The Let's Encrypt initiative [<a href="#LE" class="cite xref">LE</a>] issued its first certificates in 2015 as part of its aim to try to move the web towards being fully encrypted, and it has been extremely successful in helping achieve that goal. Subsequently, the automation protocols developed for Let's Encrypt were standardised in the IETF's ACME Working Group [<a href="#ACME" class="cite xref">ACME</a>].<a href="#section-3-9" class="pilcrow">¶</a> In 2013, most email transport between mail servers was cleartext, directly enabling some of the attacks documented in the Snowden documents. Significant effort by major mail services and MTA software developers since then have resulted in more than 90% of email being encrypted between mail servers, and various IETF protocols have been defined in order to improve that situation, e.g., SMTP MTA Strict Transport Security (MTA-STS) [<a href="#RFC8461" class="cite xref">RFC8461</a>].<a href="#section-3-10" class="pilcrow">¶</a> Lastly, MAC addresses have historically been long-term fixed values visible to local networks (and beyond), which enabled some tracking attacks that were documented in the Snowden documents [<a href="#Toronto" class="cite xref">Toronto</a>]. Implementers, vendors, and the IEEE 802 standards group recognised this weakness and started work on MAC address randomisation that in turn led to the IETF's MADINAS Working Group [<a href="#MADINAS" class="cite xref">MADINAS</a>], which aims to ensure randomised MAC addresses can be used on the Internet without causing unintentional harm. There is also a history of IETF work on deprecating MAC-address-based IPv6 interface identifiers and advocating pseudorandom identifiers and temporary addresses, some of which pre-dates Snowden [<a href="#RFC7217" class="cite xref">RFC7217</a>] [<a href="#RFC8064" class="cite xref">RFC8064</a>] [<a href="#RFC8981" class="cite xref">RFC8981</a>].<a href="#section-3-11" class="pilcrow">¶</a> In summary, the significantly large volume of technical work pursued in the IETF and elsewhere as a result of the Snowden revelations has focussed on two main things: decreasing the amount of plaintext that remains visible to network observers and secondly reducing the number of long-term identifiers that enable unexpected identification or re-identification of devices or users. This work is not by any means complete, nor is deployment universal, but significant progress has been made, and the work continues even if the level of annoyance at the attack has faded somewhat over time.<a href="#section-3-12" class="pilcrow">¶</a> One should also note that there has been pushback against these improvements in security and privacy and the changes they cause for deployments. That has come from more or less two camps: those on whom these improvements force change tend to react badly, but later figure out how to adjust, and those who seemingly prefer not to strengthen security so as to, for example, continue to achieve what they call "visibility" even in the face of the many engineers who correctly argue that such an anti-encryption approach inevitably leads to worse security overall. The recurring nature of this kind of pushback is nicely illustrated by [<a href="#RFC1984" class="cite xref">RFC1984</a>]. That informational document was published in 1996 as an IETF response to an early iteration of the perennial "encryption is bad" argument. In 2015, the unmodified 1996 text was upgraded to a BCP (BCP 200) as the underlying arguments have not changed, and will not change.<a href="#section-3-13" class="pilcrow">¶</a> Looking back on all the above from a 2023 vantage point, I think that, as a community of Internet engineers, we got a lot right, but that today there's way more that needs to be done to better protect the security and privacy of people who use the Internet. In particular, we (the technical community) haven't done nearly as good a job at countering surveillance capitalism [<a href="#Zubhoff2019" class="cite xref">Zubhoff2019</a>], which has exploded in the last decade. In part, that's because many of the problems are outside of the scope of bodies such as the IETF. For example, intrusive backend sharing of people's data for advertising purposes can't really be mitigated via Internet protocols.<a href="#section-3-14" class="pilcrow">¶</a> However, I also think that the real annoyance felt with respect to the Snowden revelations is (in general) not felt nearly as much when it comes to the legal but hugely privacy-invasive activities of major employers of Internet engineers.<a href="#section-3-15" class="pilcrow">¶</a> It's noteworthy that RFC 7258 doesn't consider that bad actors are limited to governments, and personally, I think many advertising industry schemes for collecting data are egregious examples of pervasive monitoring and hence ought also be considered an attack on the Internet that ought be mitigated where possible. However, the Internet technical community clearly hasn't acted in that way over the last decade.<a href="#section-3-16" class="pilcrow">¶</a> Perhaps that indicates that Internet engineers and the bodies in which they congregate need to place much more emphasis on standards for ethical behaviour than has been the case for the first half-century of the Internet. And while it would be good to see the current leaders of Internet bodies work to make progress in that regard, at the time of writing, it sadly seems more likely that government regulators will be the ones to try force better behaviour. That of course comes with a significant risk of having regulations that stymie the kind of permissionless innovation that characterised many earlier Internet successes.<a href="#section-3-17" class="pilcrow">¶</a> So while we got a lot right in our reaction to Snowden's revelations, currently, we have a "worse" Internet. Nonetheless, I do still hope to see a sea change there, as the importance of real Internet security and privacy for people becomes utterly obvious to all, even the most hard-core capitalists and government signals intelligence agencies. That may seem naive, but I remain optimistic that, as a fact-based community, we (and eventually our employers) will recognise that the lesser risk is to honestly aim to provide the best security and privacy practically possible.<a href="#section-3-18" class="pilcrow">¶</a> </section> </div> <div id="farzaneh-badii-did-snowdens-revelations-help-with-protecting-human-rights-on-the-internet"> <section id="section-4"> <h2 id="name-farzaneh-badii-did-snowdens"> <a href="#section-4" class="section-number selfRef">4. </a><a href="#name-farzaneh-badii-did-snowdens" class="section-name selfRef">Farzaneh Badii: Did Snowden's Revelations Help with Protecting Human Rights on the Internet?</a> </h2> It is very difficult to empirically measure the effect of Snowden's revelations on human rights and the Internet. Anecdotally, we have been witnessing dominant regulatory and policy approaches that impact technologies and services that are at the core of protecting human rights on the Internet. (A range of European Union laws aims to address online safety or concentration of data. There are many more regulations that have an impact on the Internet [<a href="#Masnick2023" class="cite xref">Masnick2023</a>].) There has been little progress in fixing technical and policy issues that help enable human rights. The Snowden revelations did not revolutionize the Internet governance and technical approaches to support human rights such as freedom of expression, freedom of association and assembly, and privacy. It did not decrease the number of Internet shutdowns nor the eagerness of authoritarian (and even to some extent democratic) countries to territorialize the Internet. In some cases, the governments argued that they should have more data sovereignty or Internet sovereignty. Perhaps the revelations helped with the evolution of some technical and policy aspects.<a href="#section-4-1" class="pilcrow">¶</a> After Snowden's revelations 10 years ago, engineers and advocates at the IETF responded in a few ways. One prominent response was the issuance of a BCP document, "Pervasive Monitoring Is an Attack" [<a href="#RFC7258" class="cite xref">RFC7258</a>] by Farrell and Tschofenig. The responses to the Snowden revelations did not mean that IETF had lost sight of issues such as privacy and surveillance. There were instances of resistance to surveillance in the past by engineers (we do not delve into how successful that was in protecting human rights). However, historically, many engineers believed that widespread and habitual surveillance was too expensive to be practical. The revelations proved them wrong.<a href="#section-4-2" class="pilcrow">¶</a> Rights-centered activists were also involved with the IETF before the revelations. For example, staff from Center for Democracy and Technology (CDT) was undertaking work at the IETF (and was a member of the Internet Architecture Board) and held workshops about the challenges of creating privacy-protective protocols and systems. The technical shortcomings that were exploited by the National Security Agency to carry out mass-scale surveillance were recognized by the IETF before the Snowden revelations [<a href="#Garfinkel1995" class="cite xref">Garfinkel1995</a>] [<a href="#RFC6462" class="cite xref">RFC6462</a>]. In 2012, Joy Liddicoat and Avri Doria wrote a report for the Internet Society that extensively discussed the processes and principles of human rights and Internet protocols [<a href="#Doria2012" class="cite xref">Doria2012</a>].<a href="#section-4-3" class="pilcrow">¶</a> Perhaps the Snowden revelations brought more attention to the IETF and its work as it related to important issues, such as privacy and freedom of expression. It might have also expedited and helped with more easily convening the Human Rights Protocol Considerations Research Group (HRPC) in the Internet Research Task Force (IRTF) in July 2015. The HRPC RG was originally co-chaired by Niels ten Oever (who worked at Article 19 at the time) and Internet governance activist Avri Doria. The charter of the HRPC RG states that the group was established: "to research whether standards and protocols can enable, strengthen or threaten human rights, as defined in the Universal Declaration of Human Rights (UDHR) and the International Covenant on Civil and Political Rights (ICCPR)."<a href="#section-4-4" class="pilcrow">¶</a> During the past decade, a few successful strides were made to create protocols that, when and if implemented, aim at protecting privacy of the users, as well as help with reducing pervasive surveillance. These efforts were in keeping with the consensus of the IETF found in RFC 7258. Sometimes these protocols have anti-censorship qualities as well. A few examples immediately come to mind: 1) the encryption of DNS queries (for example, DNS over HTTPS), 2) ACME protocol underpinning the Let's Encrypt initiative, and 3) Registration Data Access Protocol (RDAP) [<a href="#RFC7480" class="cite xref">RFC7480</a>] [<a href="#RFC7481" class="cite xref">RFC7481</a>] [<a href="#RFC8056" class="cite xref">RFC8056</a>] [<a href="#RFC9082" class="cite xref">RFC9082</a>] [<a href="#RFC9083" class="cite xref">RFC9083</a>] [<a href="#RFC9224" class="cite xref">RFC9224</a>]. (It is debatable that RDAP had anything to do with the Snowden revelations, but it is still a good example and is finally being implemented.)<a href="#section-4-5" class="pilcrow">¶</a> The DNS Queries over HTTPS protocol aimed to encrypt DNS queries. Four years after RFC 7258, DoH was developed to tackle both active and passive monitoring of DNS queries. It is also a tool that can help with combatting censorship. Before the revelations, DNS query privacy would have been controversial due to being expensive or unnecessary, but the Snowden revelations made it more plausible. Let's Encrypt was not an Internet protocol, but it was an initiative that aimed to encrypt the web, and later on some of the automation protocols were standardized in the IETF ACME Working Group. RDAP could solve a long-term problem: redacting the domain name registrants' (and IP address holders') sensitive, personal data but at the same time enabling legitimate access to the information. As to the work of HRPC Research Group, it has so far issued [<a href="#RFC8280" class="cite xref">RFC8280</a>] by ten Oever and Cath and a number of informational Internet-Drafts.<a href="#section-4-6" class="pilcrow">¶</a> While we cannot really argue that all the movements and privacy-preserving protocols and initiatives that enable protecting human rights at the infrastructure layer solely or directly result from the Snowden revelations, I think it is safe to say that the revelations helped with expediting the resolution of some of the "technical" hesitations that had an effect on fixing Internet protocols that enabled protection of human rights.<a href="#section-4-7" class="pilcrow">¶</a> Unfortunately, the Snowden revelations have not yet helped us meaningfully with adopting a human rights approach. We can't agree on prioritizing human rights in our Internet communities for a host of reasons. This could be due to: 1) human rights are sometimes in conflict with each other; 2) it is simply not possible to mitigate the human right violation through the Internet protocol; 3) it is not obvious for the engineers in advance how the Internet protocol contributes to enabling human rights protections, or precisely what they ought to do; 4) the protocol is already there, but market, law, and a host of other societal and political issues do not allow for widespread implementation.<a href="#section-4-8" class="pilcrow">¶</a> IETF did not purposefully take a long time to adopt and implement protocols that enabled human rights. There were technical and political issues that created barriers. For example, as WHOIS was not capable of accommodating a tiered-access option, the IETF community attempted a few times before to create a protocol that would disclose the necessary information of IP holders and domain name registrants while at the same time protecting their data (Cross Registry Internet Service Protocol (CRISP) and later on Internet Registry Information Service (IRIS) are the examples). However, IRIS was technically very difficult to implement. It was not until RDAP was developed and the General Data Protection Regulation (GDPR) was enacted that Internet Corporation for Assigned Names and Numbers had to consider instructing registries and registrars to implement RDAP and its community had to come up with a privacy-compliant policy. Overall, a host of regulatory and market incentives can halt or slow down the implementation of human-rights-enabling protocols and implementation could depend on other organizations with their own political and stakeholder conflicts. Sometimes the protocol is available, but the regulatory framework and the market do not allow for implementation. Sometimes the surrounding context includes practical dimensions that are easy to overlook in a purely engineering-focused argument.<a href="#section-4-9" class="pilcrow">¶</a> A curious example of this is sanctions regimes that target transactions involving economically valuable assets. As a result, sanctions might limit sanctioned nations' and entities' access to IPv4 resources (because the existence of a resale market for these addresses causes acquiring them to be interpreted as buying something of value), though the same consideration may not apply to IPv6 address resources. But IPv6 adoption itself depends on a host of complex factors that are by no means limited to technical comparisons of the properties of IPv4 and IPv6. Someone focused only on technical features of protocols may devise an elegant solution but be surprised both by deployment challenges and unintended downstream effects. Sometimes there are arguments over implementation of a protocol because as it is perceived, while it can protect freedom of expression and reduce surveillance, it can hamper other human rights. For instance, the technical community and some network operators still have doubts about the implementation of DNS over HTTPS, despite its potential to circumvent censorship and its ability to encrypt DNS queries. The arguments against implementation of DoH include protection of children online and lack of law enforcement access to data.<a href="#section-4-10" class="pilcrow">¶</a> We must acknowledge that sometimes the technical solutions that we use that protect one right (for example, encryption to protect the right to privacy or to prevent surveillance) could potentially affect technical and policy solutions that try to protect other human rights (for example, encryption could prevent financial institutions from monitoring employees' network activities to detect fraudulent behavior). Acknowledging and identifying these conflicts can help us come up with alternative techniques that could protect human rights while not hampering other technical solutions such as encryption. Where such alternative techniques are not possible, acknowledging the shortcoming could clarify and bring to light the trade-offs that we have accepted in our Internet system.<a href="#section-4-11" class="pilcrow">¶</a> Ironically, we advocate for connectivity and believe expressing oneself on the Internet is a human right, but when a war erupts, we resort to tools that impact that very concept. For example, some believe that, by imposing sanctions on critical properties of the Internet, we can punish the perpetrators of a war. The Regional Internet Registries that are in charge of registration of IP addresses have shown resilience to these requests. However, some tech companies (for example, Cogent [<a href="#Roth2022" class="cite xref">Roth2022</a>]) decided not to serve sanctioned countries and overcomplied with sanctions. Overcompliance with sanctions could hamper ordinary people's access to the Internet [<a href="#Badii2023" class="cite xref">Badii2023</a>].<a href="#section-4-12" class="pilcrow">¶</a> Perhaps we can solve some of these problems by undertaking a thorough impact assessment and contextualization to reveal how and why Internet protocols affect human rights (something Fidler and I argued for [<a href="#Badii2021" class="cite xref">Badii2021</a>]). Contextualization and impact assessment can reveal how each Internet protocol or each line of code, in which systems, have an impact on which and whose human rights.<a href="#section-4-13" class="pilcrow">¶</a> The HRPC RG (which I am a part of) and the larger human rights and policy analyst communities are still struggling to analyze legal, social, and market factors alongside the protocols to have a good understanding of what has an impact and what has to be changed. It is hard, but it is not impossible. If we thoroughly document and research the lifecycle of an Internet protocol and contextualize it, we might have a better understanding of which parts of the protocol to fix and how to fix them in order to protect human rights.<a href="#section-4-14" class="pilcrow">¶</a> Overall, the revelations did, to some extent, contribute to the evolution of our ideas and perspectives. Our next step should be to undertake research on the impact of Internet systems (including Internet protocols) on human rights, promote the implementation of protocols good for human rights through policy and advocacy, and focus on which technical parts we can standardize to help with more widespread implementation of human-rights-enabling Internet protocols.<a href="#section-4-15" class="pilcrow">¶</a> </section> </div> <div id="steven-m-bellovin-governments-and-cryptography-the-crypto-wars"> <section id="section-5"> <h2 id="name-steven-m-bellovin-governmen"> <a href="#section-5" class="section-number selfRef">5. </a><a href="#name-steven-m-bellovin-governmen" class="section-name selfRef">Steven M. Bellovin: Governments and Cryptography: The Crypto Wars</a> </h2> <div id="historical-background"> <section id="section-5.1"> <h3 id="name-historical-background"> <a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-historical-background" class="section-name selfRef">Historical Background</a> </h3> It's not a secret: many governments in the world don't like it when people encrypt their traffic. More precisely, they like strong cryptography for themselves but not for others, whether those others are private citizens or other countries. But the history is longer and more complex than that.<a href="#section-5.1-1" class="pilcrow">¶</a> For much of written history, both governments and individuals used cryptography to protect their messages. To cite just one famous example, Julius Caesar is said to have encrypted messages by shifting letters in the alphabet by 3 [<a href="#Kahn1996" class="cite xref">Kahn1996</a>]. In modern parlance, 3 was the key, and each letter was encrypted with<a href="#section-5.1-2" class="pilcrow">¶</a> C[i] = (P[i] + 3) mod 23<a href="#section-5.1-3" class="pilcrow">¶</a> (The Latin alphabet of his time had only 23 letters.) Known Arabic writings on cryptanalysis go back to at least the 8th century; their sophistication shows that encryption was reasonably commonly used. In the 9th century, Abū Yūsuf Yaʻqūb ibn ʼIsḥāq aṣ-Ṣabbāḥ al-Kindī developed and wrote about frequency analysis as a way to crack ciphers [<a href="#Borda2011" class="cite xref">Borda2011</a>] [<a href="#Kahn1996" class="cite xref">Kahn1996</a>].<a href="#section-5.1-4" class="pilcrow">¶</a> In an era of minimal literacy, though, there wasn't that much use of encryption, simply because most people could neither read nor write. Governments used encryption for diplomatic messages, and cryptanalysts followed close behind. The famed Black Chambers of the Renaissance era read messages from many different governments, while early cryptographers devised stronger and stronger ciphers [<a href="#Kahn1996" class="cite xref">Kahn1996</a>]. In Elizabethan times in England, Sir Francis Walsingham's intelligence agency intercepted and decrypted messages from Mary, Queen of Scots; these messages formed some of the strongest evidence against her and eventually led to her execution [<a href="#Kahn1996" class="cite xref">Kahn1996</a>].<a href="#section-5.1-5" class="pilcrow">¶</a> This pattern continued for centuries. In the United States, Thomas Jefferson invented the so-called wheel cipher in the late 18th century; it was reinvented about 100 years later by Étienne Bazeries and used as a standard American military cipher well into World War II [<a href="#Kahn1996" class="cite xref">Kahn1996</a>]. Jefferson and other statesmen of the late 18th and early 19th centuries regularly used cryptography when communicating with each other. An encrypted message was even part of the evidence introduced in Aaron Burr's 1807 trial for treason [<a href="#Kerr2020" class="cite xref">Kerr2020</a>] [<a href="#Kahn1996" class="cite xref">Kahn1996</a>]. Edgar Allan Poe claimed that he could cryptanalyze any message sent to him [<a href="#Kahn1996" class="cite xref">Kahn1996</a>].<a href="#section-5.1-6" class="pilcrow">¶</a> The telegraph era upped the ante. In the US, just a year after Samuel Morse deployed his first telegraph line between Baltimore and Washington, his business partner, Francis Smith, published a codebook to help customers protect their traffic from prying eyes [<a href="#Smith1845" class="cite xref">Smith1845</a>]. In 1870, Britain nationalized its domestic telegraph network; in response, Robert Slater published a more sophisticated codebook [<a href="#Slater1870" class="cite xref">Slater1870</a>]. On the government side, Britain took advantage of its position as the central node in the world's international telegraphic networks to read a great deal of traffic passing through the country [<a href="#Headrick1991" class="cite xref">Headrick1991</a>] [<a href="#Kennedy1971" class="cite xref">Kennedy1971</a>]. They used this ability strategically, too -- when war broke out in 1914, the British Navy cut Germany's undersea telegraph cables, forcing them to use radio; an intercept of the so-called Zimmermann telegram, when cryptanalyzed, arguably led to American entry into the war and thence to Germany's defeat. Once the US entered the war, it required users of international telegraph lines to deposit copies of the codebooks they used for compression, so that censors could check messages for prohibited content [<a href="#Kahn1996" class="cite xref">Kahn1996</a>].<a href="#section-5.1-7" class="pilcrow">¶</a> In Victorian Britain, private citizens, often lovers, used encryption in newspapers' personal columns to communicate without their parents' knowledge. Charles Wheatstone and Charles Babbage used to solve these elementary ciphers routinely for their own amusement [<a href="#Kahn1996" class="cite xref">Kahn1996</a>].<a href="#section-5.1-8" class="pilcrow">¶</a> This pattern continued for many years. Governments regularly used ciphers and codes, while other countries tried to break them; private individuals would sometimes use encryption but not often, and rarely well. But the two World Wars marked a sea change, one that would soon reverberate into the civilian world.<a href="#section-5.1-9" class="pilcrow">¶</a> The first World War featured vast troop movements by all parties; this in turn required a lot of encrypted communications, often by telegraph or radio. These messages were often easily intercepted in bulk. Furthermore, the difficulty of encrypting large volumes of plaintext led to the development of a variety of mechanical encryption devices, including Germany's famed Enigma machine. World War II amplified both trends. It also gave rise to machine-assisted cryptanalysis, such as the United Kingdom's bombes (derived from an earlier Polish design) and Colossus machine, and the American's device for cracking Japan's PURPLE system. The US also used punch card-based tabulators to assist in breaking other Japanese codes, such as the Japanese Imperial Navy's JN-25 [<a href="#Kahn1996" class="cite xref">Kahn1996</a>] [<a href="#Rowlett1998" class="cite xref">Rowlett1998</a>].<a href="#section-5.1-10" class="pilcrow">¶</a> These developments set the stage for the postwar SIGINT (Signals Intelligence) environment. Many intragovernmental messages were sent by radio, making them easy to intercept; advanced cryptanalytic machines made cryptanalysis easier. Ciphers were getting stronger, though, and government SIGINT agencies did not want to give up their access to data. While there were undoubtedly many developments, two are well known.<a href="#section-5.1-11" class="pilcrow">¶</a> The first involved CryptoAG, a Swedish (and later Swiss) manufacturer of encryption devices. The head of that company, Boris Hagelin, was a friend of William F. Friedman, a pioneering American cryptologist. During the 1950s, CryptoAG sold its devices to other governments; apparently at Friedman's behest, Hagelin weakened the encryption in a way that let the NSA read the traffic [<a href="#Miller2020" class="cite xref">Miller2020</a>].<a href="#section-5.1-12" class="pilcrow">¶</a> The story involving the British is less well-documented and less clear. When some of Britain's former colonies gained their independence, the British government gave them captured, war-surplus Enigma machines to protect their own traffic. Some authors contend that this was deceptive, in that these former colonies did not realize that the British could read Enigma-protected traffic; others claim that this was obvious but that these countries didn't care: Britain was no longer their enemy; it was neighboring countries they were worried about. Again, though, this concerned governmental use of encryption [<a href="#Kahn1996" class="cite xref">Kahn1996</a>] [<a href="#Baldwin2022" class="cite xref">Baldwin2022</a>]. There was still little private use.<a href="#section-5.1-13" class="pilcrow">¶</a> </section> </div> <div id="the-crypto-wars-begin"> <section id="section-5.2"> <h3 id="name-the-crypto-wars-begin"> <a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-the-crypto-wars-begin" class="section-name selfRef">The Crypto Wars Begin</a> </h3> The modern era of conflict between an individual's desire for privacy and the government desires to read traffic began around 1972. The grain harvest in the USSR had failed; since relations between the Soviet Union and the United States were temporarily comparatively warm, the Soviet grain company -- an arm of the Soviet government, of course -- entered into negotiations with private American companies. Unknown to Americans at the time, Soviet intelligence was intercepting the phone calls of the American negotiating teams. In other words, private companies had to deal with state actors as a threat. Eventually, US intelligence learned of this and came to a realization: the private sector needed strong cryptography, too, to protect American national interests [<a href="#Broad1982" class="cite xref">Broad1982</a>] [<a href="#Johnson1998" class="cite xref">Johnson1998</a>]. This underscored the need for strong cryptography to protect American civilian traffic -- but the SIGINT people were unhappy at the thought of more encryption that they couldn't break.<a href="#section-5.2-1" class="pilcrow">¶</a> Meanwhile, the US was concerned about protecting unclassified data [<a href="#Landau2014" class="cite xref">Landau2014</a>]. In 1973 and again in 1974, the National Bureau of Standards (NBS) put out a call for a strong, modern encryption algorithm. IBM submitted Lucifer, an internally developed algorithm based on what has become known as a 16-round Feistel network. The original version used a long key. It seemed quite strong, so NBS sent it off to the NSA to get their take. The eventual design, which was adopted in 1976 as the Data Encryption Standard (DES), differed in some important ways from Lucifer. First, the so-called S-boxes, the source of the cryptologic strength of DES, were changed, and were now demonstrably not composed of random integers. Many researchers alleged that the S-boxes contained an NSA back door. It took nearly 20 years for the truth to come out: the S-boxes were in fact strengthened, not weakened. Most likely, IBM independently discovered the attack now known as differential cryptanalysis, though some scholars suspect that the NSA told them about it. The nonrandom S-boxes protected against this attack. The second change, though, was clearly insisted on by the NSA: the key size was shortened, from Lucifer's 112 bits to DES's 56 bits. We now know that the NSA wanted a 48-bit key size, while IBM wanted 64 bits; they compromised at 56 bits.<a href="#section-5.2-2" class="pilcrow">¶</a> Whitfield Diffie and Martin Hellman, at Stanford University, wondered about the 56-bit keys. In 1979, they published a paper demonstrating that the US government, but few others, could afford to build a brute-force cracking machine, one that could try all 256 possible keys to crack a message. NSA denied tampering with the design; a Senate investigating committee found that assertion to be correct, but did not discuss the shortened key length issue.<a href="#section-5.2-3" class="pilcrow">¶</a> This, however, was not Diffie and Hellman's greatest contribution to cryptology. A few years earlier, they had published a paper inventing what is now known as public key cryptography. (In fact, public key encryption had been invented a few years earlier at UK Government Communications Headquarters (GCHQ), but they kept their discovery classified until 1997.) In 1978, Ronald Rivest, Adi Shamir, and Leonard Adleman devised the RSA algorithm, which made it usable. (An NSA employee, acting on his own, sent a letter warning that academic conferences on cryptology might violate US export laws.)<a href="#section-5.2-4" class="pilcrow">¶</a> Around the same time, George Davida at the University of Wisconsin applied for a patent on a stream cipher; the NSA slapped a secrecy order on the application. This barred him from even talking about his invention. The publicity was devastating; the NSA had to back down.<a href="#section-5.2-5" class="pilcrow">¶</a> The Crypto Wars had thus begun: civilians were inventing strong encryption systems, and the NSA was tampering with them or trying to suppress them. Bobby Inman, the then-director of the NSA, tried creating a voluntary review process for academic papers, but very few researchers were interested in participating [<a href="#Landau1988" class="cite xref">Landau1988</a>].<a href="#section-5.2-6" class="pilcrow">¶</a> There were few major public battles during the 1980s because there were few new major use cases for civilian cryptography during that time. There was one notable incident, though: Shamir, Amos Fiat, and Uriel Feige invented zero-knowledge proofs and applied for a US patent. In response, the US Army slapped a secrecy order on the patent. After a great deal of public outrage and intervention by, of all organizations, the NSA, the order was lifted on very narrow grounds: the inventors were not American, and they had been discussing their work all over the world [<a href="#Landau1988" class="cite xref">Landau1988</a>].<a href="#section-5.2-7" class="pilcrow">¶</a> In the 1990s, though, everything changed.<a href="#section-5.2-8" class="pilcrow">¶</a> </section> </div> <div id="the-battle-is-joined"> <section id="section-5.3"> <h3 id="name-the-battle-is-joined"> <a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-the-battle-is-joined" class="section-name selfRef">The Battle Is Joined</a> </h3> There were three major developments in cryptography in the early 1990s. First, Phil Zimmermann released PGP (Pretty Good Privacy), a package to encrypt email messages. In 1993, AT&T planned to release the TSD-3600, an easy-to-use phone encryptor aimed at business travelers. Shortly after that, the Netscape Communications Corporation released SSL (Secure Socket Layer) as a way to enable web-based commerce using their browser and web server. All of these were seen as threats by the NSA and the FBI.<a href="#section-5.3-1" class="pilcrow">¶</a> PGP was, at least arguably, covered by what was known as ITAR, the International Trafficking in Arms Regulations -- under American law, encryption software was regarded as a weapon, so exports required a license. It was also alleged to infringe the patents on the RSA algorithm. Needless to say, both issues were problematic for what was intended to be open source software. Eventually, the criminal investigation into Zimmermann's role in the spread of PGP overseas was dropped, but the threat of such investigations remained to deter others [<a href="#Levy2001" class="cite xref">Levy2001</a>].<a href="#section-5.3-2" class="pilcrow">¶</a> The TSD-3600 was another matter. AT&T was a major corporation that did not want to pick a fight with the US government, but international business travelers were seen as a major market for the device. At the government's "request", the DES chip was replaced with what was known as the Clipper chip. The Clipper chip used Skipjack, a cipher with 80-bit keys; it was thus much stronger against brute-force attacks than DES. However, it provided "key escrow". Without going into any details, the key escrow mechanism allowed US government eavesdroppers to consult a pair of (presumably secure) internal databases and decrypt all communications protected by the chip. The Clipper chip proved to be extremely unpopular with industry; that AT&T Bell Labs' Matt Blaze found a weakness in the design [<a href="#Blaze1994" class="cite xref">Blaze1994</a>], one that let you use Skipjack without the key escrow feature, didn't help its reputation.<a href="#section-5.3-3" class="pilcrow">¶</a> The third major development, SSL, was even trickier. SSL was aimed at e-commerce, and of course Netscape wanted to be able to sell its products outside the US. That would require an export license, so they made a deal with the government: non-American users would receive a version that used 40-bit keys, a key length far shorter than what the NSA had agreed to 20 years earlier. (To get ahead of the story: there was a compromise mode of operation, wherein an export-grade browser could use strong encryption when talking to a financial institution. This hybrid mode led to cryptographic weaknesses discovered some 20 years later [<a href="#Adrian2015" class="cite xref">Adrian2015</a>].)<a href="#section-5.3-4" class="pilcrow">¶</a> Technologists and American industry pushed back. The IETF adopted the Danvers Doctrine, described in [<a href="#RFC3365" class="cite xref">RFC3365</a>]:<a href="#section-5.3-5" class="pilcrow">¶</a> <blockquote id="section-5.3-6"> At the 32cd [sic] IETF held in Danvers, Massachusetts during April of 1995 the IESG asked the plenary for a consensus on the strength of security that should be provided by IETF standards. Although the immediate issue before the IETF was whether or not to support "export" grade security (which is to say weak security) in standards the question raised the generic issue of security in general.<a href="#section-5.3-6.1" class="pilcrow">¶</a> The overwhelming consensus was that the IETF should standardize on the use of the best security available, regardless of national policies. This consensus is often referred to as the "Danvers Doctrine".<a href="#section-5.3-6.2" class="pilcrow">¶</a> </blockquote> Then American companies started losing business to their overseas competitors, who did not have to comply with US export laws. All of this led to what seemed like a happy conclusion: the US government drastically loosened its export rules for cryptographic software. All was well -- or so it seemed...<a href="#section-5.3-7" class="pilcrow">¶</a> </section> </div> <div id="the-hidden-battle"> <section id="section-5.4"> <h3 id="name-the-hidden-battle"> <a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-the-hidden-battle" class="section-name selfRef">The Hidden Battle</a> </h3> Strong cryptography was here to stay, and it was no longer an American monopoly, if indeed it ever was. The Information Assurance Directorate of the NSA, the part of the agency that is supposed to protect US data, was pleased by the spread of strong cryptography. When the Advanced Encryption Standard (AES) competition was held, there were no allegations of malign NSA interference; in fact, the winning entry was devised by two Europeans, Joan Daemen and Vincent Rijmen. But the NSA and its SIGINT needs did not go away -- the agency merely adopted other techniques.<a href="#section-5.4-1" class="pilcrow">¶</a> I have often noted that one doesn't go through strong security, one goes around it. When strong encryption became more common and much more necessary, the NSA started going around it, by targeting computers and the software that they run. And it seems clear that they believe that AES is quite strong; they've even endorsed its use for protecting TOP SECRET information. But there was an asterisk attached to that endorsement: AES is suitable if and only if properly used and implemented. Therein lies the rub.<a href="#section-5.4-2" class="pilcrow">¶</a> The first apparent attempt to tamper with outside cryptographic mechanisms was discovered in 2007, when two Microsoft researchers, Dan Shumow and Niels Ferguson, noted an odd property of a NIST-standardized random number generator, DUAL_EC_DRBG. (The NBS had been renamed to NIST, the National Institute of Standards and Technology.) Random numbers are vital for cryptography, but Shumow and Ferguson showed that if certain constants in DUAL_EC_DRBG were chosen in a particular way with a known-but-hidden other number, whoever knew that number could predict all future random numbers from a system given a few sample bytes to start from [<a href="#Kostyuk2022" class="cite xref">Kostyuk2022</a>]. These sample bytes could come from known keys, nonces, or anything else. Where did the constants in DUAL_EC_DRBG come from and how were they chosen or generated? No one who knows is talking. But although cryptographers and security specialists were very suspicious -- Bruce Schneier wrote in 2007, before more facts came out, that "both NIST and the NSA have some explaining to do"; I assigned my students reading on the topic -- the issue didn't really get any traction until six years later, when among the papers that Edward Snowden disclosed was the information that the NSA had indeed tampered with a major cryptographic standard, though published reports did not specifically name DUAL_EC_DRBG or explain what the purpose was.<a href="#section-5.4-3" class="pilcrow">¶</a> The revelations didn't stop there. There have been allegations that the NSA paid some companies to use DUAL_EC_DRBG in their products. Some people have claimed that there were attempts to modify some IETF standards to make enough random bytes visible, to aid in exploiting the random number generator. A major vendor of networking gear, Juniper, did use DUAL_EC_DRBG in some of its products, but with different constants [<a href="#Checkoway2016" class="cite xref">Checkoway2016</a>]. Where did these come from? Were they from the NSA or some other government? Could their source tree have been hacked by an intelligence agency? There was a different hack of their code at around the same time [<a href="#Moore2015" class="cite xref">Moore2015</a>]. No one is talking.<a href="#section-5.4-4" class="pilcrow">¶</a> The Snowden revelations also included data suggesting that the NSA had a worldwide eavesdropping network and a group that tried very specific, targeted hacks on very specific targets' systems. In retrospect, neither is surprising: "spies gonna spy". The NSA's business is signals intelligence; of course they're going to try to intercept traffic. Indeed, the DUAL_EC_DRBG tampering is useless to anyone who has not collected messages to decrypt. And targeted hacks are a natural way around strong encryption: collect the data before it is encrypted or after it is decrypted, and don't worry about the strength of the algorithms.<a href="#section-5.4-5" class="pilcrow">¶</a> The privacy community, worldwide, was appalled, though perhaps they shouldn't have been. It calls to mind the line that Claude Rains' character uttered in the movie Casablanca [<a href="#Curtiz" class="cite xref">Curtiz</a>]: "I'm shocked, shocked to find that gambling is going on in here." The immediate and continuing reaction was to deploy more encryption. The standards have long existed; what was missing was adoption. One barrier was the difficulty and expense of getting certificates to use with TLS, the successor to SSL; that void was filled by Let's Encrypt [<a href="#LE" class="cite xref">LE</a>], which made free certificates easy to get online. Today, most HTTP traffic is encrypted, so much so that Google's search engine down-ranks sites that do not use it. Major email providers uniformly use TLS to protect all traffic. Wi-Fi, though a local area issue, now uses much stronger encryption. (It's important to remember that security and insecurity have economic components. Security doesn't have to be perfect to be very useful, if it raises the attackers' costs by enough.)<a href="#section-5.4-6" class="pilcrow">¶</a> The news on the software side is less good. Not a day goes by when one does not read of organizations being hit by ransomware. It goes without saying that any threat actor capable of encrypting disks is also capable of stealing the information on them; indeed, that is a frequent accompanying activity, since the threat of disclosure is another incentive to pay for those sites that do have good enough backups. Major vendors have put a lot of effort into securing their software, but bugs and operational errors by end-user sites persist.<a href="#section-5.4-7" class="pilcrow">¶</a> </section> </div> <div id="whither-the-ietf"> <section id="section-5.5"> <h3 id="name-whither-the-ietf"> <a href="#section-5.5" class="section-number selfRef">5.5. </a><a href="#name-whither-the-ietf" class="section-name selfRef">Whither the IETF?</a> </h3> Signal intelligence agencies, not just the NSA, but its peers around the globe -- most major countries have their own -- are not going to go away. The challenges that have beset the NSA are common to all such agencies, and their solutions are likely the same. The question is what should be done to protect individual privacy. A number of strong democracies, such as Australia and the United Kingdom, are, in a resumption of the Crypto Wars, moving to restrict encryption. Spurred on by complaints from the FBI and other law enforcement agencies, the US Congress frequently considers bills to do the same.<a href="#section-5.5-1" class="pilcrow">¶</a> The IETF has long had a commitment to strong, ubiquitous encryption. This is a good thing. It needs to continue, with cryptography and other security features designed into protocols from the beginning. But there is also a need for maintenance. Parameters such as key lengths and modulus sizes age; a value that is acceptable today may not be 10 years hence. (We've already seen apparent problems from 1024-bit moduli specified in an RFC, an RFC that was not modified when technology improved enough that attacking encryption based on them had become feasible [<a href="#Adrian2015" class="cite xref">Adrian2015</a>].) The IETF can do nothing about the code that vendors ship or that sites use, but it can alert the world that it thinks things have changed.<a href="#section-5.5-2" class="pilcrow">¶</a> Cryptoagility is of increasing importance. In the next very few years, we will have so-called post-quantum algorithms. Both protocols and key lengths will need to change, perhaps drastically. Is the IETF ready? What will happen to, say, DNSSEC if key lengths become drastically longer? Backwards compatibility will remain important, but that, of course, opens the door to other attacks. We've long thought about them; we need to be sure that our mechanisms work -- we've been surprised in the past [<a href="#BellovinRescorla2006" class="cite xref">BellovinRescorla2006</a>].<a href="#section-5.5-3" class="pilcrow">¶</a> We also need to worry more about metadata. General Michael Hayden, former director of both the NSA and the CIA, once remarked, "We kill people based on metadata" [<a href="#Ferran2014" class="cite xref">Ferran2014</a>]. But caution is necessary; attempts to hide metadata can have side effects. To give a trivial example, Tor is quite strong, but if your exit node is in a different country than you are in, web sites that use IP geolocation may present their content in a language foreign to you. Some sites even block connections from known Tor exit nodes. More generally, many attempts to hide metadata involve trusting a different party; that party may turn out to be untrustworthy or it may itself become a target of attack. As another prominent IETFer has remarked, "Insecurity is like entropy; you can't destroy it, but you can move it around." The IETF has done a lot; it needs to do more. And remember that the risk here is not just governments acting directly, it's also private companies that collect the data and sell it to all comers.<a href="#section-5.5-4" class="pilcrow">¶</a> Finally, the IETF must remember that its middle name is "Engineering". To me, one of the attributes of engineering is the art of picking the right solution in an over-constrained environment. Intelligence agencies won't go away, nor will national restrictions on cryptography. We have to pick the right path while staying true to our principles.<a href="#section-5.5-5" class="pilcrow">¶</a> </section> </div> </section> </div> <div id="security-considerations"> <section id="section-6"> <h2 id="name-security-considerations"> <a href="#section-6" class="section-number selfRef">6. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a> </h2> Each or any of the authors may have forgotten or omitted things or gotten things wrong. We're sorry if that's the case, but that's in the nature of a look-back such as this. Such flaws almost certainly won't worsen security or privacy, though.<a href="#section-6-1" class="pilcrow">¶</a> </section> </div> <div id="iana-considerations"> <section id="section-7"> <h2 id="name-iana-considerations"> <a href="#section-7" class="section-number selfRef">7. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a> </h2> This document has no IANA actions.<a href="#section-7-1" class="pilcrow">¶</a> </section> </div> <section id="section-8"> <h2 id="name-informative-references"> <a href="#section-8" class="section-number selfRef">8. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a> </h2> <dl class="references"> <dt id="ACME">[ACME]</dt> <dd> IETF, "Automated Certificate Management Environment (acme)", <<a href="https://datatracker.ietf.org/wg/acme/about/">https://datatracker.ietf.org/wg/acme/about/</a>>. </dd> <dd class="break"></dd> <dt id="Adrian2015">[Adrian2015]</dt> <dd> Adrian, D., Bhargavan, K., Durumeric, Z., Gaudry, P., Green, M., Halderman, J. A., Heninger, N., Springhall, D., Thomé, E., Valenta, L., VanderSloot, B., Wustrow, E., Zanella-Béguelin, S., and P. Zimmermann, "Imperfect Forward Secrecy: How Diffie-Hellman Fails in Practice", CCS '15: Proceedings of the 22th ACM Conference on Computer and Communications Security, <time datetime="2015-10" class="refDate">October 2015</time>, <<a href="https://dl.acm.org/doi/10.1145/2810103.2813707">https://dl.acm.org/doi/10.1145/2810103.2813707</a>>. </dd> <dd class="break"></dd> <dt id="Badii2021">[Badii2021]</dt> <dd> Badiei, F., Fidler, B., and The Pennsylvania State University Press, "The Would-Be Technocracy: Evaluating Efforts to Direct and Control Social Change with Internet Protocol Design", Journal of Information Policy, vol. 11, pp. 376-402, DOI 10.5325/jinfopoli.11.2021.0376, <time datetime="2021-12" class="refDate">December 2021</time>, <<a href="https://doi.org/10.5325/jinfopoli.11.2021.0376">https://doi.org/10.5325/jinfopoli.11.2021.0376</a>>. </dd> <dd class="break"></dd> <dt id="Badii2023">[Badii2023]</dt> <dd> Badiei, F., "Sanctions and the Internet", Digital Medusa, <time datetime="2023" class="refDate">2023</time>, <<a href="https://digitalmedusa.org/wp-content/uploads/2023/05/SanctionsandtheInternet-DigitalMedusa.pdf">https://digitalmedusa.org/wp-content/uploads/2023/05/SanctionsandtheInternet-DigitalMedusa.pdf</a>>. </dd> <dd class="break"></dd> <dt id="Baldwin2022">[Baldwin2022]</dt> <dd> Baldwin, M., "Did Britain sell Enigmas postwar?", Dr. Enigma, <time datetime="2022-03" class="refDate">March 2022</time>, <<a href="https://drenigma.org/2022/03/02/did-britain-sell-enigmas-postwar/">https://drenigma.org/2022/03/02/did-britain-sell-enigmas-postwar/</a>>. </dd> <dd class="break"></dd> <dt id="BellovinRescorla2006">[BellovinRescorla2006]</dt> <dd> Bellovin, S. M. and E. K. Rescorla, "Deploying a New Hash Algorithm", Proceedings of NDSS '06, <time datetime="2006-02" class="refDate">February 2006</time>, <<a href="https://www.cs.columbia.edu/~smb/papers/new-hash.pdf">https://www.cs.columbia.edu/~smb/papers/new-hash.pdf</a>>. </dd> <dd class="break"></dd> <dt id="Blaze1994">[Blaze1994]</dt> <dd> Blaze, M., "Protocol Failure in the Escrowed Encryption Standard", CCS '94: Proceedings of Second ACM Conference on Computer and Communications Security, <time datetime="1994" class="refDate">1994</time>, <<a href="https://dl.acm.org/doi/10.1145/191177.191193">https://dl.acm.org/doi/10.1145/191177.191193</a>>. </dd> <dd class="break"></dd> <dt id="Borda2011">[Borda2011]</dt> <dd> Borda, M., "Fundamentals in Information Theory and Coding", Springer-Berlin, <time datetime="2011-05" class="refDate">May 2011</time>. </dd> <dd class="break"></dd> <dt id="Broad1982">[Broad1982]</dt> <dd> Broad, W. J., "Evading the Soviet Ear at Glen Cove", Science, 217:4563, pp. 910-911, <time datetime="1982-09" class="refDate">September 1982</time>, <<a href="https://www.science.org/doi/abs/10.1126/science.217.4563.910">https://www.science.org/doi/abs/10.1126/science.217.4563.910</a>>. </dd> <dd class="break"></dd> <dt id="CFRG">[CFRG]</dt> <dd> IRTF, "Crypto Forum (cfrg)", <<a href="https://datatracker.ietf.org/rg/cfrg/about/">https://datatracker.ietf.org/rg/cfrg/about/</a>>. </dd> <dd class="break"></dd> <dt id="Checkoway2016">[Checkoway2016]</dt> <dd> Checkoway, S., Maskiewicz, J., Garman, C., Fried, J., Cohney, S., Green, M., Heninger, N., Weinmann, R. P., Rescorla, E., and Hovav Shacham, "A Systematic Analysis of the Juniper Dual EC Incident", CCS '16: Proceedings of the 2016 ACM SIGSAC Conference on Computer and Communications Security, pp. 468-479, <time datetime="2016-10" class="refDate">October 2016</time>, <<a href="https://dl.acm.org/citation.cfm?id=2978395">https://dl.acm.org/citation.cfm?id=2978395</a>>. </dd> <dd class="break"></dd> <dt id="CURDLE">[CURDLE]</dt> <dd> IETF, "CURves, Deprecating and a Little more Encryption (curdle)", <<a href="https://datatracker.ietf.org/wg/curdle/about/">https://datatracker.ietf.org/wg/curdle/about/</a>>. </dd> <dd class="break"></dd> <dt id="Curtiz">[Curtiz]</dt> <dd> Curtiz, M., Epstein, J. J., Epstein, P. G., and H. Koch, "Casablanca", Warner Bros. Pictures, <time datetime="1942-11" class="refDate">November 1942</time>. </dd> <dd class="break"></dd> <dt id="Doria2012">[Doria2012]</dt> <dd> Liddicoat, J. and A. Doria, "Human Rights and Internet Protocols: Comparing Processes and Principles", The Internet Society, <time datetime="2012-12" class="refDate">December 2012</time>, <<a href="https://www.internetsociety.org/resources/doc/2012/human-rights-and-internet-protocols-comparing-processes-and-principles/">https://www.internetsociety.org/resources/doc/2012/human-rights-and-internet-protocols-comparing-processes-and-principles/</a>>. </dd> <dd class="break"></dd> <dt id="Dual-EC">[Dual-EC]</dt> <dd> Bernstein, D., Lange, T., and R. Niederhagen, "Dual EC: A Standardized Back Door", <time datetime="2016-07" class="refDate">July 2016</time>, <<a href="https://eprint.iacr.org/2015/767.pdf">https://eprint.iacr.org/2015/767.pdf</a>>. </dd> <dd class="break"></dd> <dt id="Ferran2014">[Ferran2014]</dt> <dd> Ferran, L., "Ex-NSA Chief: "We Kill People Based on Metadata"", ABC News, <time datetime="2014-05" class="refDate">May 2014</time>, <<a href="https://abcnews.go.com/blogs/headlines/2014/05/ex-nsa-chief-we-kill-people-based-on-metadata">https://abcnews.go.com/blogs/headlines/2014/05/ex-nsa-chief-we-kill-people-based-on-metadata</a>>. </dd> <dd class="break"></dd> <dt id="Garfinkel1995">[Garfinkel1995]</dt> <dd> Garfinkel, S., "PGP: Pretty Good Privacy", O'Reilly and Associates, <time datetime="1995-01" class="refDate">January 1995</time>. </dd> <dd class="break"></dd> <dt id="Guard2013">[Guard2013]</dt> <dd> Greenwald, G., "NSA collecting phone records of millions of Verizon customers daily", The Guardian, <time datetime="2013-06" class="refDate">June 2013</time>. </dd> <dd class="break"></dd> <dt id="Headrick1991">[Headrick1991]</dt> <dd> Headrick, D. R., "The Invisible Weapon: Telecommunications and International Politics, 1851-1945", Oxford University Press, <time datetime="1991" class="refDate">1991</time>. </dd> <dd class="break"></dd> <dt id="Johnson1998">[Johnson1998]</dt> <dd> Johnson, T. R., "American Cryptology During the Cold War, 1945-1989; Book III: Retrenchment and Reform, 1972-1980", Center for Cryptologic History, NSA, <time datetime="1998" class="refDate">1998</time>, <<a href="https://www.nsa.gov/portals/75/documents/news-features/declassified-documents/cryptologic-histories/cold_war_iii.pdf">https://www.nsa.gov/portals/75/documents/news-features/declassified-documents/cryptologic-histories/cold_war_iii.pdf</a>>. </dd> <dd class="break"></dd> <dt id="Kahn1996">[Kahn1996]</dt> <dd> Kahn, D., "The Codebreakers: The Comprehensive History of Secret Communication from Ancient Times to the Internet", 2nd Edition, Scribner, <time datetime="1996" class="refDate">1996</time>. </dd> <dd class="break"></dd> <dt id="Kennedy1971">[Kennedy1971]</dt> <dd> Kennedy, P. M., "Imperial cable communications and strategy, 1870-1914", English Historical Review, 86:341, pp. 728-752, Oxford University Press, <time datetime="1971-10" class="refDate">October 1971</time>, <<a href="https://www.jstor.org/stable/563928">https://www.jstor.org/stable/563928</a>>. </dd> <dd class="break"></dd> <dt id="Kerr2020">[Kerr2020]</dt> <dd> Kerr, O. S., "Decryption Originalism: The Lessons of Burr", Harvard Law Review, 134:905, <time datetime="2021-01" class="refDate">January 2021</time>, <<a href="https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3533069">https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3533069</a>>. </dd> <dd class="break"></dd> <dt id="Kostyuk2022">[Kostyuk2022]</dt> <dd> Kostyuk, N. and S. Landau, "Dueling over DUAL_EC_DRBG: The Consequences of Corrupting a Cryptographic Standardization Process", Harvard National Security Journal, 13:2, pp. 224-284, <time datetime="2022-06" class="refDate">June 2022</time>, <<a href="https://www.harvardnsj.org/wp-content/uploads/sites/13/2022/06/Vol13Iss2_Kostyuk-Landau_Dual-EC-DRGB.pdf">https://www.harvardnsj.org/wp-content/uploads/sites/13/2022/06/Vol13Iss2_Kostyuk-Landau_Dual-EC-DRGB.pdf</a>>. </dd> <dd class="break"></dd> <dt id="Landau1988">[Landau1988]</dt> <dd> Landau, S., "Zero Knowledge and the Department of Defense", Notices of the American Mathematical Society, 35:1, pp. 5-12, <time datetime="1988-01" class="refDate">January 1988</time>, <<a href="https://privacyink.org/pdf/Zero_Knowledge.pdf">https://privacyink.org/pdf/Zero_Knowledge.pdf</a>>. </dd> <dd class="break"></dd> <dt id="Landau2014">[Landau2014]</dt> <dd> Landau, S., "Under the Radar: NSA's Efforts to Secure Private-Sector Telecommunications Infrastructure", Journal of National Security Law & Policy, 7:3, <time datetime="2014-09" class="refDate">September 2014</time>, <<a href="https://jnslp.com/wp-content/uploads/2015/03/NSA%E2%80%99s-Efforts-to-Secure-Private-Sector-Telecommunications-Infrastructure_2.pdf">https://jnslp.com/wp-content/uploads/2015/03/NSA%E2%80%99s-Efforts-to-Secure-Private-Sector-Telecommunications-Infrastructure_2.pdf</a>>. </dd> <dd class="break"></dd> <dt id="LE">[LE]</dt> <dd> Aas, J., Barnes, R., Case, B., Durumeric, Z., Eckersley, P., Flores-López, A., Halderman, A., Hoffman-Andrews, J., Kasten, J., Rescorla, E., Schoen, S. D., and B. Warren, "Let's Encrypt: An Automated Certificate Authority to Encrypt the Entire Web", CCS '19: Proceedings of the 2019 ACM SIGSAC Conference on Computer and Communications Security, <time datetime="2019-11" class="refDate">November 2019</time>, <<a href="https://dl.acm.org/doi/pdf/10.1145/3319535.3363192">https://dl.acm.org/doi/pdf/10.1145/3319535.3363192</a>>. </dd> <dd class="break"></dd> <dt id="Levy2001">[Levy2001]</dt> <dd> Levy, S., "Crypto: How the Code Rebels Beat the Government-Saving Privacy in the Digital Age", Penguin Publishing Group, <time datetime="2001-01" class="refDate">January 2001</time>. </dd> <dd class="break"></dd> <dt id="MADINAS">[MADINAS]</dt> <dd> IETF, "MAC Address Device Identification for Network and Application Services (madinas)", <<a href="https://datatracker.ietf.org/wg/madinas/about">https://datatracker.ietf.org/wg/madinas/about</a>>. </dd> <dd class="break"></dd> <dt id="Masnick2023">[Masnick2023]</dt> <dd> Masnick, M., "The Unintended Consequences of Internet Regulation", Copia, <time datetime="2023-04" class="refDate">April 2023</time>, <<a href="https://copia.is/library/unintended-consequences/">https://copia.is/library/unintended-consequences/</a>>. </dd> <dd class="break"></dd> <dt id="Miller2020">[Miller2020]</dt> <dd> Miller, G., "The intelligence coup of the century", The Washington Post, <time datetime="2020-02" class="refDate">February 2020</time>, <<a href="https://www.washingtonpost.com/graphics/2020/world/national-security/cia-crypto-encryption-machines-espionage/">https://www.washingtonpost.com/graphics/2020/world/national-security/cia-crypto-encryption-machines-espionage/</a>>. </dd> <dd class="break"></dd> <dt id="Moore2015">[Moore2015]</dt> <dd> Moore, H. D., "CVE-2015-7755: Juniper ScreenOS Authentication Backdoor", Rapid7, <time datetime="2015-12" class="refDate">December 2015</time>, <<a href="https://www.rapid7.com/blog/post/2015/12/20/cve-2015-7755-juniper-screenos-authentication-backdoor/">https://www.rapid7.com/blog/post/2015/12/20/cve-2015-7755-juniper-screenos-authentication-backdoor/</a>>. </dd> <dd class="break"></dd> <dt id="I-D.ietf-mpls-opportunistic-encrypt">[MPLS-OPPORTUNISTIC-ENCRYPT]</dt> <dd> Farrel, A. and S. Farrell, "Opportunistic Security in MPLS Networks", Work in Progress, Internet-Draft, draft-ietf-mpls-opportunistic-encrypt-03, <time datetime="2017-03-28" class="refDate">28 March 2017</time>, <<a href="https://datatracker.ietf.org/doc/html/draft-ietf-mpls-opportunistic-encrypt-03">https://datatracker.ietf.org/doc/html/draft-ietf-mpls-opportunistic-encrypt-03</a>>. </dd> <dd class="break"></dd> <dt id="Perpass">[Perpass]</dt> <dd> IETF, "perpass mailing list", <<a href="https://mailarchive.ietf.org/arch/browse/perpass/">https://mailarchive.ietf.org/arch/browse/perpass/</a>>. </dd> <dd class="break"></dd> <dt id="Perpass-BoF">[Perpass-BoF]</dt> <dd> IETF, "perpass BoF -- Handling Pervasive Monitoring in the IETF", IETF 88 Proceedings, <time datetime="2013-11" class="refDate">November 2013</time>, <<a href="https://www.ietf.org/proceedings/88/perpass.html">https://www.ietf.org/proceedings/88/perpass.html</a>>. </dd> <dd class="break"></dd> <dt id="Plenary-video">[Plenary-video]</dt> <dd> "IETF 88 Technical Plenary: Hardening The Internet", YouTube video, 2:37:28, posted by "IETF - Internet Engineering Task Force", <time datetime="2013-11" class="refDate">November 2013</time>, <<a href="https://www.youtube.com/watch?v=oV71hhEpQ20&pp=ygUQaWV0ZiA4OCBwbGVuYXJ5IA%3D%3D">https://www.youtube.com/watch?v=oV71hhEpQ20&pp=ygUQaWV0ZiA4OCBwbGVuYXJ5IA%3D%3D</a>>. </dd> <dd class="break"></dd> <dt id="Refs-to-7258">[Refs-to-7258]</dt> <dd> IETF, "References to RFC7258", <<a href="https://datatracker.ietf.org/doc/rfc7258/referencedby/">https://datatracker.ietf.org/doc/rfc7258/referencedby/</a>>. </dd> <dd class="break"></dd> <dt id="RFC1984">[RFC1984]</dt> <dd> IAB and IESG, "IAB and IESG Statement on Cryptographic Technology and the Internet", BCP 200, RFC 1984, DOI 10.17487/RFC1984, <time datetime="1996-08" class="refDate">August 1996</time>, <<a href="https://www.rfc-editor.org/info/rfc1984">https://www.rfc-editor.org/info/rfc1984</a>>. </dd> <dd class="break"></dd> <dt id="RFC3365">[RFC3365]</dt> <dd> Schiller, J., "Strong Security Requirements for Internet Engineering Task Force Standard Protocols", BCP 61, RFC 3365, DOI 10.17487/RFC3365, <time datetime="2002-08" class="refDate">August 2002</time>, <<a href="https://www.rfc-editor.org/info/rfc3365">https://www.rfc-editor.org/info/rfc3365</a>>. </dd> <dd class="break"></dd> <dt id="RFC6462">[RFC6462]</dt> <dd> Cooper, A., "Report from the Internet Privacy Workshop", RFC 6462, DOI 10.17487/RFC6462, <time datetime="2012-01" class="refDate">January 2012</time>, <<a href="https://www.rfc-editor.org/info/rfc6462">https://www.rfc-editor.org/info/rfc6462</a>>. </dd> <dd class="break"></dd> <dt id="RFC7217">[RFC7217]</dt> <dd> Gont, F., "A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)", RFC 7217, DOI 10.17487/RFC7217, <time datetime="2014-04" class="refDate">April 2014</time>, <<a href="https://www.rfc-editor.org/info/rfc7217">https://www.rfc-editor.org/info/rfc7217</a>>. </dd> <dd class="break"></dd> <dt id="RFC7258">[RFC7258]</dt> <dd> Farrell, S. and H. Tschofenig, "Pervasive Monitoring Is an Attack", BCP 188, RFC 7258, DOI 10.17487/RFC7258, <time datetime="2014-05" class="refDate">May 2014</time>, <<a href="https://www.rfc-editor.org/info/rfc7258">https://www.rfc-editor.org/info/rfc7258</a>>. </dd> <dd class="break"></dd> <dt id="RFC7480">[RFC7480]</dt> <dd> Newton, A., Ellacott, B., and N. Kong, "HTTP Usage in the Registration Data Access Protocol (RDAP)", STD 95, RFC 7480, DOI 10.17487/RFC7480, <time datetime="2015-03" class="refDate">March 2015</time>, <<a href="https://www.rfc-editor.org/info/rfc7480">https://www.rfc-editor.org/info/rfc7480</a>>. </dd> <dd class="break"></dd> <dt id="RFC7481">[RFC7481]</dt> <dd> Hollenbeck, S. and N. Kong, "Security Services for the Registration Data Access Protocol (RDAP)", STD 95, RFC 7481, DOI 10.17487/RFC7481, <time datetime="2015-03" class="refDate">March 2015</time>, <<a href="https://www.rfc-editor.org/info/rfc7481">https://www.rfc-editor.org/info/rfc7481</a>>. </dd> <dd class="break"></dd> <dt id="RFC7687">[RFC7687]</dt> <dd> Farrell, S., Wenning, R., Bos, B., Blanchet, M., and H. Tschofenig, "Report from the Strengthening the Internet (STRINT) Workshop", RFC 7687, DOI 10.17487/RFC7687, <time datetime="2015-12" class="refDate">December 2015</time>, <<a href="https://www.rfc-editor.org/info/rfc7687">https://www.rfc-editor.org/info/rfc7687</a>>. </dd> <dd class="break"></dd> <dt id="RFC7858">[RFC7858]</dt> <dd> Hu, Z., Zhu, L., Heidemann, J., Mankin, A., Wessels, D., and P. Hoffman, "Specification for DNS over Transport Layer Security (TLS)", RFC 7858, DOI 10.17487/RFC7858, <time datetime="2016-05" class="refDate">May 2016</time>, <<a href="https://www.rfc-editor.org/info/rfc7858">https://www.rfc-editor.org/info/rfc7858</a>>. </dd> <dd class="break"></dd> <dt id="RFC8056">[RFC8056]</dt> <dd> Gould, J., "Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status Mapping", RFC 8056, DOI 10.17487/RFC8056, <time datetime="2017-01" class="refDate">January 2017</time>, <<a href="https://www.rfc-editor.org/info/rfc8056">https://www.rfc-editor.org/info/rfc8056</a>>. </dd> <dd class="break"></dd> <dt id="RFC8064">[RFC8064]</dt> <dd> Gont, F., Cooper, A., Thaler, D., and W. Liu, "Recommendation on Stable IPv6 Interface Identifiers", RFC 8064, DOI 10.17487/RFC8064, <time datetime="2017-02" class="refDate">February 2017</time>, <<a href="https://www.rfc-editor.org/info/rfc8064">https://www.rfc-editor.org/info/rfc8064</a>>. </dd> <dd class="break"></dd> <dt id="RFC8280">[RFC8280]</dt> <dd> ten Oever, N. and C. Cath, "Research into Human Rights Protocol Considerations", RFC 8280, DOI 10.17487/RFC8280, <time datetime="2017-10" class="refDate">October 2017</time>, <<a href="https://www.rfc-editor.org/info/rfc8280">https://www.rfc-editor.org/info/rfc8280</a>>. </dd> <dd class="break"></dd> <dt id="RFC8446">[RFC8446]</dt> <dd> Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, <time datetime="2018-08" class="refDate">August 2018</time>, <<a href="https://www.rfc-editor.org/info/rfc8446">https://www.rfc-editor.org/info/rfc8446</a>>. </dd> <dd class="break"></dd> <dt id="RFC8461">[RFC8461]</dt> <dd> Margolis, D., Risher, M., Ramakrishnan, B., Brotman, A., and J. Jones, "SMTP MTA Strict Transport Security (MTA-STS)", RFC 8461, DOI 10.17487/RFC8461, <time datetime="2018-09" class="refDate">September 2018</time>, <<a href="https://www.rfc-editor.org/info/rfc8461">https://www.rfc-editor.org/info/rfc8461</a>>. </dd> <dd class="break"></dd> <dt id="RFC8484">[RFC8484]</dt> <dd> Hoffman, P. and P. McManus, "DNS Queries over HTTPS (DoH)", RFC 8484, DOI 10.17487/RFC8484, <time datetime="2018-10" class="refDate">October 2018</time>, <<a href="https://www.rfc-editor.org/info/rfc8484">https://www.rfc-editor.org/info/rfc8484</a>>. </dd> <dd class="break"></dd> <dt id="RFC8981">[RFC8981]</dt> <dd> Gont, F., Krishnan, S., Narten, T., and R. Draves, "Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6", RFC 8981, DOI 10.17487/RFC8981, <time datetime="2021-02" class="refDate">February 2021</time>, <<a href="https://www.rfc-editor.org/info/rfc8981">https://www.rfc-editor.org/info/rfc8981</a>>. </dd> <dd class="break"></dd> <dt id="RFC9000">[RFC9000]</dt> <dd> Iyengar, J., Ed. and M. Thomson, Ed., "QUIC: A UDP-Based Multiplexed and Secure Transport", RFC 9000, DOI 10.17487/RFC9000, <time datetime="2021-05" class="refDate">May 2021</time>, <<a href="https://www.rfc-editor.org/info/rfc9000">https://www.rfc-editor.org/info/rfc9000</a>>. </dd> <dd class="break"></dd> <dt id="RFC9082">[RFC9082]</dt> <dd> Hollenbeck, S. and A. Newton, "Registration Data Access Protocol (RDAP) Query Format", STD 95, RFC 9082, DOI 10.17487/RFC9082, <time datetime="2021-06" class="refDate">June 2021</time>, <<a href="https://www.rfc-editor.org/info/rfc9082">https://www.rfc-editor.org/info/rfc9082</a>>. </dd> <dd class="break"></dd> <dt id="RFC9083">[RFC9083]</dt> <dd> Hollenbeck, S. and A. Newton, "JSON Responses for the Registration Data Access Protocol (RDAP)", STD 95, RFC 9083, DOI 10.17487/RFC9083, <time datetime="2021-06" class="refDate">June 2021</time>, <<a href="https://www.rfc-editor.org/info/rfc9083">https://www.rfc-editor.org/info/rfc9083</a>>. </dd> <dd class="break"></dd> <dt id="RFC9113">[RFC9113]</dt> <dd> Thomson, M., Ed. and C. Benfield, Ed., "HTTP/2", RFC 9113, DOI 10.17487/RFC9113, <time datetime="2022-06" class="refDate">June 2022</time>, <<a href="https://www.rfc-editor.org/info/rfc9113">https://www.rfc-editor.org/info/rfc9113</a>>. </dd> <dd class="break"></dd> <dt id="RFC9224">[RFC9224]</dt> <dd> Blanchet, M., "Finding the Authoritative Registration Data Access Protocol (RDAP) Service", STD 95, RFC 9224, DOI 10.17487/RFC9224, <time datetime="2022-03" class="refDate">March 2022</time>, <<a href="https://www.rfc-editor.org/info/rfc9224">https://www.rfc-editor.org/info/rfc9224</a>>. </dd> <dd class="break"></dd> <dt id="Roth2022">[Roth2022]</dt> <dd> Roth, E., "Internet backbone provider shuts off service in Russia", The Verge, <time datetime="2022-03" class="refDate">March 2022</time>, <<a href="https://www.theverge.com/2022/3/5/22962822/internet-backbone-provider-cogent-shuts-off-service-russia">https://www.theverge.com/2022/3/5/22962822/internet-backbone-provider-cogent-shuts-off-service-russia</a>>. </dd> <dd class="break"></dd> <dt id="Rowlett1998">[Rowlett1998]</dt> <dd> Rowlett, F. B., "The Story of Magic, Memoirs of an American Cryptologic Pioneer", Aegean Park Press, <time datetime="1998" class="refDate">1998</time>. </dd> <dd class="break"></dd> <dt id="Slater1870">[Slater1870]</dt> <dd> Slater, R., "Telegraphic Code, to Ensure Secresy in the Transmission of Telegrams", First Edition, W.R. Gray, <time datetime="1870" class="refDate">1870</time>, <<a href="https://books.google.com/books?id=MJYBAAAAQAAJ">https://books.google.com/books?id=MJYBAAAAQAAJ</a>>. </dd> <dd class="break"></dd> <dt id="Smith1845">[Smith1845]</dt> <dd> Smith, F. O., "The Secret Corresponding Vocabulary: Adapted for Use to Morse's Electro-Magnetic Telegraph, and Also in Conducting Written Correspondence, Transmitted by the Mails, or Otherwise", Thurston, Isley & Company, <time datetime="1845" class="refDate">1845</time>, <<a href="https://books.google.com/books?id=Z45clCxsF7EC">https://books.google.com/books?id=Z45clCxsF7EC</a>>. </dd> <dd class="break"></dd> <dt id="STRINT">[STRINT]</dt> <dd> W3C and IAB, "A W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)", <time datetime="2014-03" class="refDate">March 2014</time>, <<a href="https://www.w3.org/2014/strint/">https://www.w3.org/2014/strint/</a>>. </dd> <dd class="break"></dd> <dt id="Timeline">[Timeline]</dt> <dd> Wikipedia, "Global surveillance disclosures (2013-present)", <time datetime="2023-07" class="refDate">July 2023</time>, <<a href="https://en.wikipedia.org/w/index.php?title=Global_surveillance_disclosures_(2013%E2%80%93present)&oldid=1161557819">https://en.wikipedia.org/w/index.php?title=Global_surveillance_disclosures_(2013%E2%80%93present)&oldid=1161557819</a>>. </dd> <dd class="break"></dd> <dt id="I-D.ietf-tls-esni">[TLS-ECH]</dt> <dd> Rescorla, E., Oku, K., Sullivan, N., and C. A. Wood, "TLS Encrypted Client Hello", Work in Progress, Internet-Draft, draft-ietf-tls-esni-16, <time datetime="2023-04-06" class="refDate">6 April 2023</time>, <<a href="https://datatracker.ietf.org/doc/html/draft-ietf-tls-esni-16">https://datatracker.ietf.org/doc/html/draft-ietf-tls-esni-16</a>>. </dd> <dd class="break"></dd> <dt id="Toronto">[Toronto]</dt> <dd> Memmott, M., "Canada Used Airport Wi-Fi To Track Travelers, Snowden Leak Alleges", NPR, <time datetime="2014-01" class="refDate">January 2014</time>, <<a href="https://www.npr.org/sections/thetwo-way/2014/01/31/269418375/airport-wi-fi-used-to-track-travelers-snowden-leak-alleges">https://www.npr.org/sections/thetwo-way/2014/01/31/269418375/airport-wi-fi-used-to-track-travelers-snowden-leak-alleges</a>>. </dd> <dd class="break"></dd> <dt id="UTA">[UTA]</dt> <dd> IETF, "Using TLS in Applications (uta)", <<a href="https://datatracker.ietf.org/wg/uta/about">https://datatracker.ietf.org/wg/uta/about</a>>. </dd> <dd class="break"></dd> <dt id="Zubhoff2019">[Zubhoff2019]</dt> <dd> Zuboff, S., "The Age of Surveillance Capitalism: The Fight for a Human Future at the New Frontier of Power", PublicAffairs, ISBN 9781781256855, <time datetime="2019-01" class="refDate">January 2019</time>. </dd> <dd class="break"></dd> </dl> </section> <div id="acknowledgments"> <section id="appendix-A"> <h2 id="name-acknowledgments"> <a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a> </h2> Susan Landau added many valuable comments to Steve Bellovin's essay.<a href="#appendix-A-1" class="pilcrow">¶</a> We thank Carsten Bormann, Brian Carpenter, Wendy Grossman, Kathleen Moriarty, Jan Schaumann, Seth David Schoen, and Paul Wouters for comments and review of this text, though that of course doesn't mean that they necessarily agree with the text.<a href="#appendix-A-2" class="pilcrow">¶</a> This document was created at the behest of Eliot Lear, who also cat herded and did some editing.<a href="#appendix-A-3" class="pilcrow">¶</a> </section> </div> <div id="authors-addresses"> <section id="appendix-B"> <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">Stephen Farrell</div> <div dir="auto" class="left">Trinity College, Dublin</div> <div dir="auto" class="left">Ireland</div> <div class="email"> Email: <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">Farzaneh Badii</div> <div dir="auto" class="left">Digital Medusa</div> <div class="email"> Email: <a href="mailto:farzaneh.badii@gmail.com" class="email">farzaneh.badii@gmail.com</a> </div> </address> <address class="vcard"> <div dir="auto" class="left">Bruce Schneier</div> <div dir="auto" class="left">Harvard University</div> <div dir="auto" class="left">United States of America</div> <div class="email"> Email: <a href="mailto:schneier@schneier.com" class="email">schneier@schneier.com</a> </div> </address> <address class="vcard"> <div dir="auto" class="left">Steven M. Bellovin</div> <div dir="auto" class="left">Columbia University</div> <div dir="auto" class="left">United States of America</div> <div class="email"> Email: <a href="mailto:smb@cs.columbia.edu" class="email">smb@cs.columbia.edu</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>