File: rfc9151.html

package info (click to toggle)
doc-rfc 20230121-1
links: PTS, VCS
area: non-free
in suites: bookworm, forky, sid, trixie
size: 1,609,944 kB
file content (2033 lines) | stat: -rw-r--r-- 96,425 bytes
<!DOCTYPE html>
<html lang="en" class="RFC">
<head>
<meta charset="utf-8">
<meta content="Common,Latin" name="scripts">
<meta content="initial-scale=1.0" name="viewport">
<title>RFC 9151: Commercial National Security Algorithm (CNSA) Suite Profile for TLS and DTLS 1.2 and 1.3</title>
<meta content="Dorothy Cooley" name="author">
<meta content="
       This document defines a base profile for TLS protocol versions 1.2
      and 1.3 as well as DTLS protocol versions 1.2 and 1.3 for use with the
      US Commercial National Security Algorithm (CNSA) Suite.
       
       The profile applies to the capabilities, configuration, and operation
      of all components of US National Security Systems that use TLS or DTLS.
      It is also appropriate for all other US Government systems that process
      high-value information.
 
       The profile is made publicly available here for use by developers and
      operators of these and any other system deployments.
 
    " name="description">
<meta content="xml2rfc 3.12.2" name="generator">
<meta content="9151" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.12.2
    Python 3.6.15
    appdirs 1.4.4
    ConfigArgParse 1.4.1
    google-i18n-address 2.4.0
    html5lib 1.0.1
    intervaltree 3.0.2
    Jinja2 2.11.3
    kitchen 1.2.6
    lxml 4.4.2
    pycairo 1.15.1
    pycountry 19.8.18
    pyflakes 2.1.1
    PyYAML 5.4.1
    requests 2.24.0
    setuptools 40.5.0
    six 1.14.0
    WeasyPrint 52.5
-->
<link href="rfc9151.xml" rel="alternate" type="application/rfc+xml">
<link href="#copyright" rel="license">
<style type="text/css">/*

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

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

*/

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

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

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

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

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

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

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

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

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

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

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

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

/* info block */
#identifiers {
  margin: 0;
  font-size: 0.9em;
}
#identifiers dt {
  width: 3em;
  clear: left;
}
#identifiers dd {
  float: left;
  margin-bottom: 0;
}
/* 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: "Noto Sans",Arial,Helvetica,sans-serif;
  margin: 0.5em 0;
}
address.vcard .type {
  display: none;
}
.alternative-contact {
  margin: 1.5em 0 1em;
}
hr.addr {
  border-top: 1px dashed;
  margin: 0;
  color: #ddd;
  max-width: calc(100% - 16px);
}

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

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

/* pagination */
@media print {
  body {

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

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

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

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

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

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

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

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

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

}

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


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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
  font-variant: small-caps;
  font-weight: bold;
  font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
 h2 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 31px;
 }
 h3 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
 h4 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
/* Float artwork pilcrow to the right */
@media screen {
  .artwork a.pilcrow {
    display: block;
    line-height: 0.7;
    margin-top: 0.15em;
  }
}
/* Make pilcrows on dd visible */
@media screen {
  dd:hover > a.pilcrow {
    visibility: visible;
  }
}
/* Make the placement of figcaption match that of a table's caption
   by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
   margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
  margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
   possibly even requiring a new line */
@media print {
  a.pilcrow {
    display: none;
  }
}
/* Styling for the external metadata */
div#external-metadata {
  background-color: #eee;
  padding: 0.5em;
  margin-bottom: 0.5em;
  display: none;
}
div#internal-metadata {
  padding: 0.5em;                       /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
  clear: both;
  margin: 0 0 -1em;
  padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
  margin-bottom: 0.25em;
  min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
  border-left: 1px solid #ddd;
  margin: 1em 0 1em 2em;
  padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
  margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
  figcaption, table caption {
    page-break-before: avoid;
  }
}
/* Font size adjustments for print */
@media print {
  body  { font-size: 10pt;      line-height: normal; max-width: 96%; }
  h1    { font-size: 1.72em;    padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
  h2    { font-size: 1.44em;    padding-top: 1.5em; } /* 1*1.2*1.2 */
  h3    { font-size: 1.2em;     padding-top: 1.5em; } /* 1*1.2 */
  h4    { font-size: 1em;       padding-top: 1.5em; }
  h5, h6 { font-size: 1em;      margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
  .artwork,
  .sourcecode {
    margin-bottom: 1em;
  }
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
  border: 1px solid #ddd;
}
td {
  border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
  background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
  #toc nav { display: none; }
  #toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
  break-after: avoid-page;
  break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
  break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode  {
  break-before: 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 bottim margin space,
   since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
 margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
  margin-bottom: 1em;                    /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
   backgrounds.  Changed to something a bit more selective. */
tt, code {
  background-color: transparent;
}
p tt, p code, li tt, li code {
  background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
   margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
  line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
  margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
  clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
  content: "\00a0";
}
/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */
li > p {
  margin-bottom: 0.5em
}
/* Don't let p margin spill out from inside list items */
li > p:last-of-type {
  margin-bottom: 0;
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc9151" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-cooley-cnsa-dtls-tls-profile-07" rel="prev">
  </head>
<body>
<script src="https://www.rfc-editor.org/js/metadata.min.js"></script>
<table class="ears">
<thead><tr>
<td class="left">RFC 9151</td>
<td class="center">CNSA Suite Profile for (D)TLS</td>
<td class="right">April 2022</td>
</tr></thead>
<tfoot><tr>
<td class="left">Cooley</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/rfc9151" class="eref">9151</a></dd>
<dt class="label-category">Category:</dt>
<dd class="category">Informational</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2022-04" class="published">April 2022</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Author:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">D. Cooley</div>
<div class="org">NSA</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 9151</h1>
<h1 id="title">Commercial National Security Algorithm (CNSA) Suite Profile for TLS and DTLS 1.2 and 1.3</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">This document defines a base profile for TLS protocol versions 1.2
      and 1.3 as well as DTLS protocol versions 1.2 and 1.3 for use with the
      US Commercial National Security Algorithm (CNSA) Suite.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
<p id="section-abstract-2">The profile applies to the capabilities, configuration, and operation
      of all components of US National Security Systems that use TLS or DTLS.
      It is also appropriate for all other US Government systems that process
      high-value information.<a href="#section-abstract-2" class="pilcrow">¶</a></p>
<p id="section-abstract-3">The profile is made publicly available here for use by developers and
      operators of these and any other system deployments.<a href="#section-abstract-3" class="pilcrow">¶</a></p>
</section>
<div id="status-of-memo">
<section id="section-boilerplate.1">
        <h2 id="name-status-of-this-memo">
<a href="#name-status-of-this-memo" class="section-name selfRef">Status of This Memo</a>
        </h2>
<p id="section-boilerplate.1-1">
            This document is not an Internet Standards Track specification; it is
            published for informational purposes.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-2">
            This 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></p>
<p id="section-boilerplate.1-3">
            Information about the current status of this document, any
            errata, and how to provide feedback on it may be obtained at
            <span><a href="https://www.rfc-editor.org/info/rfc9151">https://www.rfc-editor.org/info/rfc9151</a></span>.<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="copyright">
<section id="section-boilerplate.2">
        <h2 id="name-copyright-notice">
<a href="#name-copyright-notice" class="section-name selfRef">Copyright Notice</a>
        </h2>
<p id="section-boilerplate.2-1">
            Copyright (c) 2022 IETF Trust and the persons identified as the
            document authors. All rights reserved.<a href="#section-boilerplate.2-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.2-2">
            This document is subject to BCP 78 and the IETF Trust's Legal
            Provisions Relating to IETF Documents
            (<span><a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a></span>) in effect on the date of
            publication of this document. Please review these documents
            carefully, as they describe your rights and restrictions with
            respect to this document.<a href="#section-boilerplate.2-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="toc">
<section id="section-toc.1">
        <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents">
<a href="#name-table-of-contents" class="section-name selfRef">Table of Contents</a>
        </h2>
<nav class="toc"><ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction" class="xref">Introduction</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-cnsa" class="xref">CNSA</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>.  <a href="#name-terminology" class="xref">Terminology</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4">
            <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-cnsa-suites" class="xref">CNSA Suites</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.1">
                <p id="section-toc.1-1.4.2.1.1"><a href="#section-4.1" class="xref">4.1</a>.  <a href="#name-cnsa-dtls-key-establishment" class="xref">CNSA (D)TLS Key Establishment Algorithms</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4.2.2">
                <p id="section-toc.1-1.4.2.2.1"><a href="#section-4.2" class="xref">4.2</a>.  <a href="#name-cnsa-tls-authentication" class="xref">CNSA TLS Authentication</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5">
            <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-cnsa-compliance-and-interop" class="xref">CNSA Compliance and Interoperability Requirements</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.1">
                <p id="section-toc.1-1.5.2.1.1"><a href="#section-5.1" class="xref">5.1</a>.  <a href="#name-acceptable-elliptic-curve-c" class="xref">Acceptable Elliptic Curve Cryptography (ECC) Curves</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.2">
                <p id="section-toc.1-1.5.2.2.1"><a href="#section-5.2" class="xref">5.2</a>.  <a href="#name-acceptable-rsa-schemes-para" class="xref">Acceptable RSA Schemes, Parameters, and Checks</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.3">
                <p id="section-toc.1-1.5.2.3.1"><a href="#section-5.3" class="xref">5.3</a>.  <a href="#name-acceptable-finite-field-gro" class="xref">Acceptable Finite Field Groups</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5.2.4">
                <p id="section-toc.1-1.5.2.4.1"><a href="#section-5.4" class="xref">5.4</a>.  <a href="#name-certificates" class="xref">Certificates</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6">
            <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-dtls-12-requirements" class="xref">(D)TLS 1.2 Requirements</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.1">
                <p id="section-toc.1-1.6.2.1.1"><a href="#section-6.1" class="xref">6.1</a>.  <a href="#name-the-extended_master_secret-" class="xref">The "extended_master_secret" Extension</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.2">
                <p id="section-toc.1-1.6.2.2.1"><a href="#section-6.2" class="xref">6.2</a>.  <a href="#name-the-signature_algorithms-ex" class="xref">The "signature_algorithms" Extension</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.3">
                <p id="section-toc.1-1.6.2.3.1"><a href="#section-6.3" class="xref">6.3</a>.  <a href="#name-the-signature_algorithms_ce" class="xref">The "signature_algorithms_cert" Extension</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.4">
                <p id="section-toc.1-1.6.2.4.1"><a href="#section-6.4" class="xref">6.4</a>.  <a href="#name-the-certificaterequest-mess" class="xref">The CertificateRequest Message</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.5">
                <p id="section-toc.1-1.6.2.5.1"><a href="#section-6.5" class="xref">6.5</a>.  <a href="#name-the-certificateverify-messa" class="xref">The CertificateVerify Message</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.6">
                <p id="section-toc.1-1.6.2.6.1"><a href="#section-6.6" class="xref">6.6</a>.  <a href="#name-the-signature-in-the-server" class="xref">The Signature in the ServerKeyExchange Message</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6.2.7">
                <p id="section-toc.1-1.6.2.7.1"><a href="#section-6.7" class="xref">6.7</a>.  <a href="#name-certificate-status" class="xref">Certificate Status</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7">
            <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-dtls-13-requirements" class="xref">(D)TLS 1.3 Requirements</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.1">
                <p id="section-toc.1-1.7.2.1.1"><a href="#section-7.1" class="xref">7.1</a>.  <a href="#name-the-signature_algorithms-ext" class="xref">The "signature_algorithms" Extension</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.2">
                <p id="section-toc.1-1.7.2.2.1"><a href="#section-7.2" class="xref">7.2</a>.  <a href="#name-the-signature_algorithms_cer" class="xref">The "signature_algorithms_cert" Extension</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.3">
                <p id="section-toc.1-1.7.2.3.1"><a href="#section-7.3" class="xref">7.3</a>.  <a href="#name-the-early_data-extension" class="xref">The "early_data" Extension</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.4">
                <p id="section-toc.1-1.7.2.4.1"><a href="#section-7.4" class="xref">7.4</a>.  <a href="#name-resumption" class="xref">Resumption</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7.2.5">
                <p id="section-toc.1-1.7.2.5.1"><a href="#section-7.5" class="xref">7.5</a>.  <a href="#name-certificate-status-2" class="xref">Certificate Status</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8">
            <p id="section-toc.1-1.8.1"><a href="#section-8" class="xref">8</a>.  <a href="#name-security-considerations" class="xref">Security Considerations</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9">
            <p id="section-toc.1-1.9.1"><a href="#section-9" class="xref">9</a>.  <a href="#name-iana-considerations" class="xref">IANA Considerations</a></p>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-10" class="xref">10</a>. <a href="#name-references" class="xref">References</a></p>
<ul class="compact toc ulBare ulEmpty">
<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.1">
                <p id="section-toc.1-1.10.2.1.1"><a href="#section-10.1" class="xref">10.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a></p>
</li>
              <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10.2.2">
                <p id="section-toc.1-1.10.2.2.1"><a href="#section-10.2" class="xref">10.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#appendix-A" class="xref"></a><a href="#name-authors-address" class="xref">Author's Address</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<div id="intro">
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">This document specifies a profile of TLS version 1.2 <span>[<a href="#RFC5246" class="xref">RFC5246</a>]</span> and TLS version 1.3 <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span> as well as DTLS version 1.2 <span>[<a href="#RFC6347" class="xref">RFC6347</a>]</span> and DTLS version 1.3 <span>[<a href="#RFC9147" class="xref">RFC9147</a>]</span> for use by applications that support the National Security Agency's (NSA) Commercial National Security Algorithm (CNSA) Suite <span>[<a href="#CNSA" class="xref">CNSA</a>]</span>.  The profile applies to the capabilities, configuration, and operation of all components of US National Security Systems <span>[<a href="#SP80059" class="xref">SP80059</a>]</span>. It is also appropriate for all other US Government systems that process high-value information. It is made publicly available for use by developers and operators of these and any other system deployments.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2">This document does not define any new cipher suites; instead, it defines a CNSA-compliant profile of TLS and DTLS, and the cipher suites defined in <span>[<a href="#RFC5288" class="xref">RFC5288</a>]</span>, <span>[<a href="#RFC5289" class="xref">RFC5289</a>]</span>, and <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>.  This profile uses only algorithms in the CNSA Suite.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">The reader is assumed to have familiarity with the TLS 1.2 and 1.3 as well as the DTLS 1.2 and 1.3 protocol specifications: <span>[<a href="#RFC5246" class="xref">RFC5246</a>]</span>, <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>,  <span>[<a href="#RFC6347" class="xref">RFC6347</a>]</span>, and <span>[<a href="#RFC9147" class="xref">RFC9147</a>]</span>, respectively.  All <span class="bcp14">MUST</span>-level requirements from the protocol documents apply throughout this profile; they are generally not repeated.  This profile contains changes that elevate some <span class="bcp14">SHOULD</span>-level options to <span class="bcp14">MUST</span>-level; this profile also contains changes that elevate some <span class="bcp14">MAY</span>-level options to <span class="bcp14">SHOULD</span>-level or <span class="bcp14">MUST</span>-level.  All options that are not mentioned in this profile remain at their original requirement level.<a href="#section-1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="cnsa">
<section id="section-2">
      <h2 id="name-cnsa">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-cnsa" class="section-name selfRef">CNSA</a>
      </h2>
<p id="section-2-1">The National Security Agency (NSA) profiles commercial cryptographic
      algorithms and protocols as part of its mission to support secure,
      interoperable communications for US National Security Systems. To this
      end, it publishes guidance both to assist with the US Government
      transition to new algorithms and to provide vendors -- and the Internet
      community in general -- with information concerning their proper use and
      configuration.<a href="#section-2-1" class="pilcrow">¶</a></p>
<p id="section-2-2">Recently, cryptographic transition plans have become overshadowed by the prospect of the development of a cryptographically relevant quantum computer.  The NSA has established the CNSA Suite to provide vendors and IT users near-term flexibility in meeting their Information Assurance (IA) interoperability requirements. The purpose behind this flexibility is to avoid having vendors and customers make two major transitions in a relatively short timeframe, as we anticipate a need to shift to quantum-resistant cryptography in the near future.<a href="#section-2-2" class="pilcrow">¶</a></p>
<p id="section-2-3">The NSA is authoring a set of RFCs, including this one, to provide
      updated guidance concerning the use of certain commonly available
      commercial algorithms in IETF protocols.  These RFCs can be used in
      conjunction with other RFCs and cryptographic guidance (e.g., NIST
      Special Publications) to properly protect Internet traffic and
      data-at-rest for US National Security Systems.<a href="#section-2-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="terms">
<section id="section-3">
      <h2 id="name-terminology">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
      </h2>
<p id="section-3-1">The key words "<span class="bcp14">MUST</span>", "<span class="bcp14">MUST NOT</span>", "<span class="bcp14">REQUIRED</span>", "<span class="bcp14">SHALL</span>", "<span class="bcp14">SHALL NOT</span>", "<span class="bcp14">SHOULD</span>", "<span class="bcp14">SHOULD NOT</span>", "<span class="bcp14">RECOMMENDED</span>", "<span class="bcp14">NOT RECOMMENDED</span>", "<span class="bcp14">MAY</span>", and "<span class="bcp14">OPTIONAL</span>" in this document are to be interpreted as described in BCP 14 <span>[<a href="#RFC2119" class="xref">RFC2119</a>]</span> <span>[<a href="#RFC8174" class="xref">RFC8174</a>]</span> when, and only when, they appear in all capitals, as shown here.<a href="#section-3-1" class="pilcrow">¶</a></p>
<p id="section-3-2">"ECDSA" and "ECDH" refer to the use of the Elliptic Curve Digital Signature Algorithm (ECDSA) and Elliptic Curve Diffie Hellman (ECDH), respectively. ECDSA and ECDH are used with the NIST P-384 curve (which is based on a 384-bit prime modulus) and the SHA-384 hash function.  Similarly, "RSA" and "DH" refer to Rivest-Shamir-Adleman (RSA) and Finite Field Diffie-Hellman (DH), respectively. RSA and DH are used with a 3072-bit or 4096-bit modulus.  When RSA is used for digital signature, it is used with the SHA-384 hash function.<a href="#section-3-2" class="pilcrow">¶</a></p>
<p id="section-3-3">Henceforth, this document refers to TLS versions 1.2 and 1.3 and DTLS versions 1.2 and 1.3 collectively as "(D)TLS".<a href="#section-3-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="cnsa-suite">
<section id="section-4">
      <h2 id="name-cnsa-suites">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-cnsa-suites" class="section-name selfRef">CNSA Suites</a>
      </h2>
<p id="section-4-1"><span>[<a href="#CNSA" class="xref">CNSA</a>]</span> approves the use of both Finite Field and elliptic curve versions of the DH key agreement algorithm as well as RSA-based key establishment. <span>[<a href="#CNSA" class="xref">CNSA</a>]</span> also approves certain versions of the RSA and elliptic curve digital signature algorithms. The approved encryption techniques include the Advanced Encryption Standard (AES) used with a 256-bit key in an Authenticated Encryption with Associated Data (AEAD) mode.<a href="#section-4-1" class="pilcrow">¶</a></p>
<p id="section-4-2">In particular, CNSA includes the following:<a href="#section-4-2" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlNewline" id="section-4-3">
        <dt id="section-4-3.1">Encryption:
</dt>
        <dd style="margin-left: 1.5em" id="section-4-3.2">AES <span>[<a href="#AES" class="xref">AES</a>]</span> (with key size 256 bits),
operating in Galois/Counter Mode (GCM) <span>[<a href="#GCM" class="xref">GCM</a>]</span><a href="#section-4-3.2" class="pilcrow">¶</a>
</dd>
        <dd class="break"></dd>
<dt id="section-4-3.3">Digital Signature:
</dt>
        <dd style="margin-left: 1.5em" id="section-4-3.4">
          <p id="section-4-3.4.1">ECDSA <span>[<a href="#DSS" class="xref">DSS</a>]</span> (using the NIST P-384
elliptic curve)<a href="#section-4-3.4.1" class="pilcrow">¶</a></p>
<p id="section-4-3.4.2">RSA <span>[<a href="#DSS" class="xref">DSS</a>]</span> (with a modulus of
            3072 bits or 4096 bits)<a href="#section-4-3.4.2" class="pilcrow">¶</a></p>
</dd>
        <dd class="break"></dd>
<dt id="section-4-3.5">Key Establishment (includes key agreement and key transport):
</dt>
        <dd style="margin-left: 1.5em" id="section-4-3.6">
          <p id="section-4-3.6.1">ECDH <span>[<a href="#PWKE-A" class="xref">PWKE-A</a>]</span> (using the NIST P-384
  elliptic curve)<a href="#section-4-3.6.1" class="pilcrow">¶</a></p>
<p id="section-4-3.6.2">DH <span>[<a href="#PWKE-A" class="xref">PWKE-A</a>]</span> (with a prime
            modulus of 3072 or 4096 bits)<a href="#section-4-3.6.2" class="pilcrow">¶</a></p>
<p id="section-4-3.6.3">RSA <span>[<a href="#PWKE-B" class="xref">PWKE-B</a>]</span> (with a modulus of
            3072 or 4096 bits, but only in (D)TLS 1.2)<a href="#section-4-3.6.3" class="pilcrow">¶</a></p>
</dd>
      <dd class="break"></dd>
</dl>
<p id="section-4-4"><span>[<a href="#CNSA" class="xref">CNSA</a>]</span> also approves the use of SHA-384 <span>[<a href="#SHS" class="xref">SHS</a>]</span> as the hash algorithm for mask generation, signature generation, Pseudorandom Function (PRF) in TLS 1.2 and HMAC-based Key Derivation Function (HKDF) in TLS 1.3.<a href="#section-4-4" class="pilcrow">¶</a></p>
<div id="tls-ke">
<section id="section-4.1">
        <h3 id="name-cnsa-dtls-key-establishment">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-cnsa-dtls-key-establishment" class="section-name selfRef">CNSA (D)TLS Key Establishment Algorithms</a>
        </h3>
<p id="section-4.1-1">The following combination of algorithms and key sizes are used in CNSA (D)TLS:<a href="#section-4.1-1" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-4.1-2.1">AES with 256-bit key, operating in GCM mode<a href="#section-4.1-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-4.1-2.2">ECDH <span>[<a href="#PWKE-A" class="xref">PWKE-A</a>]</span> using the
          Ephemeral Unified Model Scheme with cofactor set to 1 (see Section
          6.1.2.2 in <span>[<a href="#PWKE-A" class="xref">PWKE-A</a>]</span>)<a href="#section-4.1-2.2" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-4.1-2.3">TLS PRF/HKDF with SHA-384 <span>[<a href="#SHS" class="xref">SHS</a>]</span><a href="#section-4.1-2.3" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-4.1-3">Or<a href="#section-4.1-3" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-4.1-4.1">AES with 256-bit key, operating in GCM mode<a href="#section-4.1-4.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-4.1-4.2">RSA key transport using 3072-bit or 4096-bit modulus <span>[<a href="#PWKE-B" class="xref">PWKE-B</a>]</span><span>[<a href="#RFC8017" class="xref">RFC8017</a>]</span><a href="#section-4.1-4.2" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-4.1-4.3">TLS PRF/HKDF with SHA-384 <span>[<a href="#SHS" class="xref">SHS</a>]</span><a href="#section-4.1-4.3" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-4.1-5">Or<a href="#section-4.1-5" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-4.1-6.1">AES with 256-bit key, operating in GCM mode<a href="#section-4.1-6.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-4.1-6.2">DH using dhEphem with domain parameters specified below in <a href="#ff-groups" class="xref">Section 5.3</a> (see Section 6.1.2.1 in <span>[<a href="#PWKE-A" class="xref">PWKE-A</a>]</span>)<a href="#section-4.1-6.2" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-4.1-6.3">TLS PRF/HKDF with SHA-384 <span>[<a href="#SHS" class="xref">SHS</a>]</span><a href="#section-4.1-6.3" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-4.1-7">The specific CNSA-compliant cipher suites are listed in <a href="#compliance" class="xref">Section 5</a>.<a href="#section-4.1-7" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tls-auth">
<section id="section-4.2">
        <h3 id="name-cnsa-tls-authentication">
<a href="#section-4.2" class="section-number selfRef">4.2. </a><a href="#name-cnsa-tls-authentication" class="section-name selfRef">CNSA TLS Authentication</a>
        </h3>
<p id="section-4.2-1">For server and/or client authentication, CNSA (D)TLS <span class="bcp14">MUST</span> generate and verify either ECDSA signatures or RSA signatures.<a href="#section-4.2-1" class="pilcrow">¶</a></p>
<p id="section-4.2-2">In all cases, the client <span class="bcp14">MUST</span> authenticate the
        server.  The server <span class="bcp14">MAY</span> also authenticate the client, as
        needed by the specific application.<a href="#section-4.2-2" class="pilcrow">¶</a></p>
<p id="section-4.2-3">The public keys used to verify these signatures <span class="bcp14">MUST</span>
        be contained in a certificate (see <a href="#certs" class="xref">Section 5.4</a> for more
        information).<a href="#section-4.2-3" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="compliance">
<section id="section-5">
      <h2 id="name-cnsa-compliance-and-interop">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-cnsa-compliance-and-interop" class="section-name selfRef">CNSA Compliance and Interoperability Requirements</a>
      </h2>
<p id="section-5-1">CNSA (D)TLS <span class="bcp14">MUST NOT</span> use TLS versions prior to (D)TLS
      1.2 in a CNSA-compliant system.  CNSA (D)TLS servers and clients
      <span class="bcp14">MUST</span> implement and use either (D)TLS version 1.2 <span>[<a href="#RFC5246" class="xref">RFC5246</a>]</span> <span>[<a href="#RFC6347" class="xref">RFC6347</a>]</span> or (D)TLS version 1.3 <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span> <span>[<a href="#RFC9147" class="xref">RFC9147</a>]</span>.<a href="#section-5-1" class="pilcrow">¶</a></p>
<div id="ecc-curves">
<section id="section-5.1">
        <h3 id="name-acceptable-elliptic-curve-c">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-acceptable-elliptic-curve-c" class="section-name selfRef">Acceptable Elliptic Curve Cryptography (ECC) Curves</a>
        </h3>
<p id="section-5.1-1">The elliptic curves used in the CNSA Suite appear in the literature
        under two different names <span>[<a href="#DSS" class="xref">DSS</a>]</span> <span>[<a href="#SECG" class="xref">SECG</a>]</span>.  For the sake of clarity, both names
        are listed below:<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<span id="name-elliptic-curves-in-cnsa-sui"></span><div id="elliptic_curve_table">
<table class="center" id="table-1">
          <caption>
<a href="#table-1" class="selfRef">Table 1</a>:
<a href="#name-elliptic-curves-in-cnsa-sui" class="selfRef">Elliptic Curves in CNSA Suite</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Curve</th>
              <th class="text-left" rowspan="1" colspan="1">NIST name</th>
              <th class="text-left" rowspan="1" colspan="1">SECG name</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">P-384</td>
              <td class="text-left" rowspan="1" colspan="1">nistp384</td>
              <td class="text-left" rowspan="1" colspan="1">secp384r1</td>
            </tr>
          </tbody>
        </table>
</div>
<p id="section-5.1-3"><span>[<a href="#RFC8422" class="xref">RFC8422</a>]</span> defines a variety of elliptic curves.  CNSA (D)TLS connections <span class="bcp14">MUST</span> use secp384r1 (also called nistp384), and the uncompressed form <span class="bcp14">MUST</span> be used, as required by <span>[<a href="#RFC8422" class="xref">RFC8422</a>]</span> and <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>.<a href="#section-5.1-3" class="pilcrow">¶</a></p>
<p id="section-5.1-4">Key pairs <span class="bcp14">MUST</span> be generated following Section 5.6.1.2 of <span>[<a href="#PWKE-A" class="xref">PWKE-A</a>]</span>.<a href="#section-5.1-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="rsa-schemes">
<section id="section-5.2">
        <h3 id="name-acceptable-rsa-schemes-para">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-acceptable-rsa-schemes-para" class="section-name selfRef">Acceptable RSA Schemes, Parameters, and Checks</a>
        </h3>
<p id="section-5.2-1"><span>[<a href="#CNSA" class="xref">CNSA</a>]</span> specifies a minimum modulus size of 3072 bits; however, only two modulus sizes (3072 bits and 4096 bits) are supported by this profile.<a href="#section-5.2-1" class="pilcrow">¶</a></p>
<span class="break"></span><dl class="dlNewline" id="section-5.2-2">
          <dt id="section-5.2-2.1">For (D)TLS 1.2:
</dt>
          <dd style="margin-left: 1.5em" id="section-5.2-2.2">
            <p id="section-5.2-2.2.1">For certificate signatures, RSASSA-PKCS1-v1_5 <span>[<a href="#RFC8017" class="xref">RFC8017</a>]</span> <span class="bcp14">MUST</span> be supported, and RSASSA-PSS <span>[<a href="#DSS" class="xref">DSS</a>]</span> <span class="bcp14">SHOULD</span> be supported.<a href="#section-5.2-2.2.1" class="pilcrow">¶</a></p>
<p id="section-5.2-2.2.2">For signatures in TLS handshake messages, RSASSA-PKCS1-v1_5 <span>[<a href="#RFC8017" class="xref">RFC8017</a>]</span> <span class="bcp14">MUST</span> be supported, and RSASSA-PSS <span>[<a href="#DSS" class="xref">DSS</a>]</span> <span class="bcp14">SHOULD</span> be supported.<a href="#section-5.2-2.2.2" class="pilcrow">¶</a></p>
<p id="section-5.2-2.2.3">For key transport, RSAES-PKCS1-v1_5 <span>[<a href="#RFC8017" class="xref">RFC8017</a>]</span> <span class="bcp14">MUST</span> be supported.<a href="#section-5.2-2.2.3" class="pilcrow">¶</a></p>
</dd>
          <dd class="break"></dd>
<dt id="section-5.2-2.3">For (D)TLS 1.3:
</dt>
          <dd style="margin-left: 1.5em" id="section-5.2-2.4">
            <p id="section-5.2-2.4.1">For certificate signatures, RSASSA-PKCS1-v1_5 <span>[<a href="#RFC8017" class="xref">RFC8017</a>]</span> <span class="bcp14">MUST</span> be supported, and RSASSA-PSS <span>[<a href="#DSS" class="xref">DSS</a>]</span> <span class="bcp14">SHOULD</span> be supported.<a href="#section-5.2-2.4.1" class="pilcrow">¶</a></p>
<p id="section-5.2-2.4.2">For signatures in TLS handshake messages, RSASSA-PSS <span>[<a href="#DSS" class="xref">DSS</a>]</span> <span class="bcp14">MUST</span> be
              supported.<a href="#section-5.2-2.4.2" class="pilcrow">¶</a></p>
<p id="section-5.2-2.4.3">For key transport, TLS 1.3 does not support RSA key
              transport.<a href="#section-5.2-2.4.3" class="pilcrow">¶</a></p>
</dd>
          <dd class="break"></dd>
<dt id="section-5.2-2.5">For all versions of (D)TLS:
</dt>
          <dd style="margin-left: 1.5em" id="section-5.2-2.6">
            <p id="section-5.2-2.6.1">RSA exponent e <span class="bcp14">MUST</span> satisfy
  2<sup>16</sup>&lt;e&lt;2<sup>256</sup> and be odd per <span>[<a href="#DSS" class="xref">DSS</a>]</span>.<a href="#section-5.2-2.6.1" class="pilcrow">¶</a></p>
<p id="section-5.2-2.6.2">If RSASSA-PSS is supported (using rsa_pss_rsae_sha384 for example), then
   the implementation <span class="bcp14">MUST</span> assert rsaEncryption as the public
   key algorithm, the hash algorithm (used for both mask generation and
   signature generation) <span class="bcp14">MUST</span> be SHA-384, the mask generation
   function 1 (MGF1) from <span>[<a href="#RFC8017" class="xref">RFC8017</a>]</span>
              <span class="bcp14">MUST</span> be used, and the salt length <span class="bcp14">MUST</span> be 48
   octets.<a href="#section-5.2-2.6.2" class="pilcrow">¶</a></p>
</dd>
        <dd class="break"></dd>
</dl>
</section>
</div>
<div id="ff-groups">
<section id="section-5.3">
        <h3 id="name-acceptable-finite-field-gro">
<a href="#section-5.3" class="section-number selfRef">5.3. </a><a href="#name-acceptable-finite-field-gro" class="section-name selfRef">Acceptable Finite Field Groups</a>
        </h3>
<p id="section-5.3-1"><span>[<a href="#CNSA" class="xref">CNSA</a>]</span> specifies a minimum modulus size of 3072 bits; however, only two modulus sizes (3072 bits and 4096 bits) are supported by this profile.<a href="#section-5.3-1" class="pilcrow">¶</a></p>
<p id="section-5.3-2">Ephemeral key pairs <span class="bcp14">MUST</span> be generated following Section 5.6.1.1.1 of <span>[<a href="#PWKE-A" class="xref">PWKE-A</a>]</span> using the approved safe prime groups specified in <span>[<a href="#RFC7919" class="xref">RFC7919</a>]</span> for DH ephemeral key agreement.  The named groups are:<a href="#section-5.3-2" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-5.3-3.1">ffdhe3072 (ID=257)<a href="#section-5.3-3.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-5.3-3.2">ffdhe4096 (ID=258)<a href="#section-5.3-3.2" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
<div id="certs">
<section id="section-5.4">
        <h3 id="name-certificates">
<a href="#section-5.4" class="section-number selfRef">5.4. </a><a href="#name-certificates" class="section-name selfRef">Certificates</a>
        </h3>
<p id="section-5.4-1">Certificates used to establish a CNSA (D)TLS connection <span class="bcp14">MUST</span> be signed with ECDSA or RSA and <span class="bcp14">MUST</span> be compliant with the CNSA Suite Certificate and Certificate Revocation List (CRL) Profile <span>[<a href="#RFC8603" class="xref">RFC8603</a>]</span>.<a href="#section-5.4-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="tls12-reqts">
<section id="section-6">
      <h2 id="name-dtls-12-requirements">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-dtls-12-requirements" class="section-name selfRef">(D)TLS 1.2 Requirements</a>
      </h2>
<p id="section-6-1">Although TLS 1.2 has technically been obsoleted by the IETF in favor of TLS 1.3, many implementations and deployments of TLS 1.2 will continue to exist.  For the cases where TLS 1.2 continues to be used, implementations <span class="bcp14">MUST</span> use <span>[<a href="#RFC5246" class="xref">RFC5246</a>]</span> and <span class="bcp14">SHOULD</span> implement the updates specified in <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span> (outlined in Section <a href="https://www.rfc-editor.org/rfc/rfc8446#section-1.3" class="relref">1.3</a> of that document).<a href="#section-6-1" class="pilcrow">¶</a></p>
<p id="section-6-2">The CNSA (D)TLS 1.2 client <span class="bcp14">MUST</span> offer at least one of these cipher suites:<a href="#section-6-2" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-6-3.1">TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 <span>[<a href="#RFC5289" class="xref">RFC5289</a>]</span> <span>[<a href="#RFC8422" class="xref">RFC8422</a>]</span><a href="#section-6-3.1" class="pilcrow">¶</a>
</li>
        <li class="normal ulEmpty" id="section-6-3.2">TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 <span>[<a href="#RFC5289" class="xref">RFC5289</a>]</span> <span>[<a href="#RFC8422" class="xref">RFC8422</a>]</span><a href="#section-6-3.2" class="pilcrow">¶</a>
</li>
        <li class="normal ulEmpty" id="section-6-3.3">TLS_RSA_WITH_AES_256_GCM_SHA384 <span>[<a href="#RFC5288" class="xref">RFC5288</a>]</span><a href="#section-6-3.3" class="pilcrow">¶</a>
</li>
        <li class="normal ulEmpty" id="section-6-3.4">TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 <span>[<a href="#RFC5288" class="xref">RFC5288</a>]</span> <span>[<a href="#RFC7919" class="xref">RFC7919</a>]</span><a href="#section-6-3.4" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-6-4">The CNSA cipher suites listed above <span class="bcp14">MUST</span> be the first
      (most preferred) cipher suites in the ClientHello message.<a href="#section-6-4" class="pilcrow">¶</a></p>
<p id="section-6-5">A CNSA (D)TLS client that offers interoperability with servers that are not CNSA compliant <span class="bcp14">MAY</span> offer additional cipher suites, but any additional cipher suites <span class="bcp14">MUST</span> appear after the CNSA cipher suites in the ClientHello message.<a href="#section-6-5" class="pilcrow">¶</a></p>
<p id="section-6-6">A CNSA (D)TLS server <span class="bcp14">MUST</span> accept one of the CNSA
      Suites above if they are offered in the ClientHello message before
      accepting a non-CNSA-compliant suite.<a href="#section-6-6" class="pilcrow">¶</a></p>
<p id="section-6-7">If interoperability is not desired with non-CNSA-compliant clients or
      servers, then the session <span class="bcp14">MUST</span> fail if no CNSA Suites are
      offered or accepted.<a href="#section-6-7" class="pilcrow">¶</a></p>
<div id="ext-master-secret">
<section id="section-6.1">
        <h3 id="name-the-extended_master_secret-">
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-the-extended_master_secret-" class="section-name selfRef">The "extended_master_secret" Extension</a>
        </h3>
<p id="section-6.1-1">A CNSA (D)TLS client <span class="bcp14">SHOULD</span> include and a CNSA
        (D)TLS server <span class="bcp14">SHOULD</span> accept the
        "extended_master_secret" extension as specified in <span>[<a href="#RFC7627" class="xref">RFC7627</a>]</span>. See <span><a href="https://www.rfc-editor.org/rfc/rfc7627#section-1" class="relref">Section 1</a> of [<a href="#RFC7627" class="xref">RFC7627</a>]</span> for security
        concerns when this extension is not used.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tls12-sig-algs">
<section id="section-6.2">
        <h3 id="name-the-signature_algorithms-ex">
<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-the-signature_algorithms-ex" class="section-name selfRef">The "signature_algorithms" Extension</a>
        </h3>
<p id="section-6.2-1">A CNSA (D)TLS client <span class="bcp14">MUST</span> include and a CNSA (D)TLS server <span class="bcp14">MUST</span> also accept the "signature_algorithms" extension. The CNSA (D)TLS client <span class="bcp14">MUST</span> offer and the 
  CNSA (D)TLS server <span class="bcp14">MUST</span> also accept at least one of the following values in the "signature_algorithms" extensions as specified in <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>:<a href="#section-6.2-1" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-6.2-2.1">ecdsa_secp384r1_sha384<a href="#section-6.2-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-6.2-2.2">rsa_pkcs1_sha384<a href="#section-6.2-2.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-6.2-3">And, if supported, the client <span class="bcp14">SHOULD</span> offer and/or the server <span class="bcp14">SHOULD</span> also accept:<a href="#section-6.2-3" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-6.2-4.1">rsa_pss_pss_sha384<a href="#section-6.2-4.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-6.2-4.2">rsa_pss_rsae_sha384<a href="#section-6.2-4.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-6.2-5">Following the guidance in <span>[<a href="#RFC8603" class="xref">RFC8603</a>]</span>, CNSA (D)TLS servers <span class="bcp14">MUST</span> only accept ECDSA or RSA for signatures on ServerKeyExchange messages and for certification path validation.<a href="#section-6.2-5" class="pilcrow">¶</a></p>
<p id="section-6.2-6">Other client offerings <span class="bcp14">MAY</span> be included to indicate the acceptable signature algorithms in cipher suites that are offered for interoperability with servers not compliant with CNSA and to indicate the signature algorithms that are acceptable for ServerKeyExchange messages and for certification path validation in non-compliant CNSA (D)TLS connections. These offerings <span class="bcp14">MUST NOT</span> be accepted by a CNSA-compliant (D)TLS server.<a href="#section-6.2-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tls12-sig-algs-cert-ext">
<section id="section-6.3">
        <h3 id="name-the-signature_algorithms_ce">
<a href="#section-6.3" class="section-number selfRef">6.3. </a><a href="#name-the-signature_algorithms_ce" class="section-name selfRef">The "signature_algorithms_cert" Extension</a>
        </h3>
<p id="section-6.3-1">A CNSA (D)TLS client <span class="bcp14">MAY</span> include the
        "signature_algorithms_cert" extension.  CNSA (D)TLS servers
        <span class="bcp14">MUST</span> process the "signature_algorithms_cert" extension
        if it is offered per <span><a href="https://www.rfc-editor.org/rfc/rfc8446#section-4.2.3" class="relref">Section 4.2.3</a> of [<a href="#RFC8446" class="xref">RFC8446</a>]</span>.<a href="#section-6.3-1" class="pilcrow">¶</a></p>
<p id="section-6.3-2">Both CNSA (D)TLS clients and servers <span class="bcp14">MUST</span> use one of the following values for certificate path validation:<a href="#section-6.3-2" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-6.3-3.1">ecdsa_secp384r1_sha384<a href="#section-6.3-3.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-6.3-3.2">rsa_pkcs1_sha384<a href="#section-6.3-3.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-6.3-4">And, if supported, <span class="bcp14">SHOULD</span> offer/accept:<a href="#section-6.3-4" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-6.3-5.1">rsa_pss_pss_sha384<a href="#section-6.3-5.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-6.3-5.2">rsa_pss_rsae_sha384<a href="#section-6.3-5.2" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
<div id="tls12-cert-request">
<section id="section-6.4">
        <h3 id="name-the-certificaterequest-mess">
<a href="#section-6.4" class="section-number selfRef">6.4. </a><a href="#name-the-certificaterequest-mess" class="section-name selfRef">The CertificateRequest Message</a>
        </h3>
<p id="section-6.4-1">When a CNSA (D)TLS server is configured to authenticate the client, the server <span class="bcp14">MUST</span> include the following values in its CertificateRequest.supported_signature_algorithms <span>[<a href="#RFC5246" class="xref">RFC5246</a>]</span> offer:<a href="#section-6.4-1" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-6.4-2.1">ecdsa_secp384r1_sha384<a href="#section-6.4-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-6.4-2.2">rsa_pkcs1_sha384<a href="#section-6.4-2.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-6.4-3">And, if supported as specified in <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>, <span class="bcp14">SHOULD</span> offer/accept:<a href="#section-6.4-3" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-6.4-4.1">rsa_pss_pss_sha384<a href="#section-6.4-4.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-6.4-4.2">rsa_pss_rsae_sha384<a href="#section-6.4-4.2" class="pilcrow">¶</a>
</li>
        </ul>
</section>
</div>
<div id="tls12-cert-verify">
<section id="section-6.5">
        <h3 id="name-the-certificateverify-messa">
<a href="#section-6.5" class="section-number selfRef">6.5. </a><a href="#name-the-certificateverify-messa" class="section-name selfRef">The CertificateVerify Message</a>
        </h3>
<p id="section-6.5-1">A CNSA (D)TLS client <span class="bcp14">MUST</span> use ECDSA or RSA when sending the CertificateVerify message.  CNSA (D)TLS servers <span class="bcp14">MUST</span> only accept ECDSA or RSA in the CertificateVerify message.<a href="#section-6.5-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tls12-ske-message">
<section id="section-6.6">
        <h3 id="name-the-signature-in-the-server">
<a href="#section-6.6" class="section-number selfRef">6.6. </a><a href="#name-the-signature-in-the-server" class="section-name selfRef">The Signature in the ServerKeyExchange Message</a>
        </h3>
<p id="section-6.6-1">A CNSA (D)TLS server <span class="bcp14">MUST</span> sign the ServerKeyExchange message using ECDSA or RSA.<a href="#section-6.6-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tls12-cert-status">
<section id="section-6.7">
        <h3 id="name-certificate-status">
<a href="#section-6.7" class="section-number selfRef">6.7. </a><a href="#name-certificate-status" class="section-name selfRef">Certificate Status</a>
        </h3>
<p id="section-6.7-1">Certificate Authorities (CAs) providing certificates to a CNSA (D)TLS
        server or client <span class="bcp14">MUST</span> provide certificate revocation
        status information via a Certificate Revocation List (CRL)
        distribution point or using the Online Certificate Status Protocol
        (OCSP).  A CNSA client <span class="bcp14">SHOULD</span> request it according to
        <span><a href="https://www.rfc-editor.org/rfc/rfc8446#section-4.4.2.1" class="relref">Section 4.4.2.1</a> of [<a href="#RFC8446" class="xref">RFC8446</a>]</span>.  If OCSP is supported, the (D)TLS server
        <span class="bcp14">SHOULD</span> provide OCSP responses in the
        CertificateStatus message.<a href="#section-6.7-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="tls13-reqts">
<section id="section-7">
      <h2 id="name-dtls-13-requirements">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-dtls-13-requirements" class="section-name selfRef">(D)TLS 1.3 Requirements</a>
      </h2>
<p id="section-7-1">The CNSA (D)TLS client <span class="bcp14">MUST</span> offer the following cipher
      suite in the ClientHello:<a href="#section-7-1" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-7-2.1">TLS_AES_256_GCM_SHA384<a href="#section-7-2.1" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-7-3">The CNSA (D)TLS client <span class="bcp14">MUST</span> include at least one of
      the following values in the "supported_groups" extension:<a href="#section-7-3" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-7-4.1">ECDHE:  secp384r1<a href="#section-7-4.1" class="pilcrow">¶</a>
</li>
        <li class="normal ulEmpty" id="section-7-4.2">DHE: ffdhe3072<a href="#section-7-4.2" class="pilcrow">¶</a>
</li>
        <li class="normal ulEmpty" id="section-7-4.3">DHE: ffdhe4096<a href="#section-7-4.3" class="pilcrow">¶</a>
</li>
      </ul>
<p id="section-7-5">The CNSA cipher suite <span class="bcp14">MUST</span> be the first (most
      preferred) cipher suite in the ClientHello message and in the
      extensions.<a href="#section-7-5" class="pilcrow">¶</a></p>
<p id="section-7-6">A CNSA (D)TLS client that offers interoperability with servers that are 
not CNSA compliant <span class="bcp14">MAY</span> offer additional cipher suites, but any additional 
cipher suites <span class="bcp14">MUST</span> appear after the CNSA-compliant cipher suites in the 
ClientHello message.<a href="#section-7-6" class="pilcrow">¶</a></p>
<p id="section-7-7">A CNSA (D)TLS server <span class="bcp14">MUST</span> accept one of the CNSA algorithms listed above if they are offered in the ClientHello message.<a href="#section-7-7" class="pilcrow">¶</a></p>
<p id="section-7-8">If interoperability is not desired with non-CNSA-compliant clients or servers, then the session <span class="bcp14">MUST</span> fail if no CNSA Suites are offered or accepted.<a href="#section-7-8" class="pilcrow">¶</a></p>
<div id="tls13-sig-algs">
<section id="section-7.1">
        <h3 id="name-the-signature_algorithms-ext">
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-the-signature_algorithms-ext" class="section-name selfRef">The "signature_algorithms" Extension</a>
        </h3>
<p id="section-7.1-1">A CNSA (D)TLS client <span class="bcp14">MUST</span> include the "signature_algorithms" extension. The CNSA (D)TLS client <span class="bcp14">MUST</span> offer at least one of the following values in the "signature_algorithms" extension:<a href="#section-7.1-1" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-7.1-2.1">ecdsa_secp384r1_sha384<a href="#section-7.1-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-7.1-2.2">rsa_pss_pss_sha384<a href="#section-7.1-2.2" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-7.1-2.3">rsa_pss_rsae_sha384<a href="#section-7.1-2.3" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-7.1-3">Clients that allow negotiating TLS 1.2 <span class="bcp14">MAY</span> offer rsa_pkcs1_sha384 for use with TLS 1.2.  Other offerings <span class="bcp14">MAY</span> be included to indicate the acceptable signature algorithms in cipher suites that are offered for interoperability with servers not compliant with CNSA in non-compliant CNSA (D)TLS connections.  These offerings <span class="bcp14">MUST NOT</span> be accepted by a CNSA-compliant (D)TLS server.<a href="#section-7.1-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tls13-sig-algs-cert">
<section id="section-7.2">
        <h3 id="name-the-signature_algorithms_cer">
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-the-signature_algorithms_cer" class="section-name selfRef">The "signature_algorithms_cert" Extension</a>
        </h3>
<p id="section-7.2-1">A CNSA (D)TLS client <span class="bcp14">SHOULD</span> include the "signature_algorithms_cert" extension. And, if offered, the CNSA (D)TLS client <span class="bcp14">MUST</span> offer at least one of the following values in the "signature_algorithms_cert" extension:<a href="#section-7.2-1" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-7.2-2.1">ecdsa_secp384r1_sha384<a href="#section-7.2-2.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-7.2-2.2">rsa_pkcs1_sha384<a href="#section-7.2-2.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-7.2-3">And, if supported, <span class="bcp14">SHOULD</span> offer:<a href="#section-7.2-3" class="pilcrow">¶</a></p>
<ul class="normal ulEmpty">
<li class="normal ulEmpty" id="section-7.2-4.1">rsa_pss_pss_sha384<a href="#section-7.2-4.1" class="pilcrow">¶</a>
</li>
          <li class="normal ulEmpty" id="section-7.2-4.2">rsa_pss_rsae_sha384<a href="#section-7.2-4.2" class="pilcrow">¶</a>
</li>
        </ul>
<p id="section-7.2-5">Following the guidance in <span>[<a href="#RFC8603" class="xref">RFC8603</a>]</span>, CNSA (D)TLS servers <span class="bcp14">MUST</span> only accept ECDSA or RSA for certificate path validation.<a href="#section-7.2-5" class="pilcrow">¶</a></p>
<p id="section-7.2-6">Other offerings <span class="bcp14">MAY</span> be included to indicate the signature algorithms that are acceptable for certification path validation in non-compliant CNSA (D)TLS connections. These offerings <span class="bcp14">MUST NOT</span> be accepted by a CNSA-compliant (D)TLS server.<a href="#section-7.2-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tls13-early-data">
<section id="section-7.3">
        <h3 id="name-the-early_data-extension">
<a href="#section-7.3" class="section-number selfRef">7.3. </a><a href="#name-the-early_data-extension" class="section-name selfRef">The "early_data" Extension</a>
        </h3>
<p id="section-7.3-1">A CNSA (D)TLS client or server <span class="bcp14">MUST NOT</span> include the
        "early_data" extension.  See <span><a href="https://www.rfc-editor.org/rfc/rfc8446#section-2.3" class="relref">Section 2.3</a> of [<a href="#RFC8446" class="xref">RFC8446</a>]</span> for security concerns.<a href="#section-7.3-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tls13-resumption">
<section id="section-7.4">
        <h3 id="name-resumption">
<a href="#section-7.4" class="section-number selfRef">7.4. </a><a href="#name-resumption" class="section-name selfRef">Resumption</a>
        </h3>
<p id="section-7.4-1">A CNSA (D)TLS server <span class="bcp14">MAY</span> send a CNSA (D)TLS client a
        NewSessionTicket message to enable resumption. A CNSA (D)TLS client
        <span class="bcp14">MUST</span> request "psk_dhe_ke" via the
        "psk_key_exchange_modes" ClientHello extension to resume a session. A
        CNSA (D)TLS client <span class="bcp14">MUST</span> offer Ephemeral Elliptic Curve
        Diffie-Hellman (ECDHE) with SHA-384 and/or Ephemeral Diffie-Hellman (DHE) with SHA-384 in the
        "supported_groups" and/or "key_share" extensions.<a href="#section-7.4-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="tls13-cert-stat">
<section id="section-7.5">
        <h3 id="name-certificate-status-2">
<a href="#section-7.5" class="section-number selfRef">7.5. </a><a href="#name-certificate-status-2" class="section-name selfRef">Certificate Status</a>
        </h3>
<p id="section-7.5-1">Certificate Authorities (CAs) providing certificates to a CNSA (D)TLS server or client <span class="bcp14">MUST</span> provide certificate revocation status information via a Certificate Revocation List (CRL) distribution point or using the Online Certificate Status Protocol (OCSP).  A CNSA client <span class="bcp14">SHOULD</span> request it according to <span><a href="https://www.rfc-editor.org/rfc/rfc8446#section-4.4.2.1" class="relref">Section 4.4.2.1</a> of [<a href="#RFC8446" class="xref">RFC8446</a>]</span>.  If OCSP is supported, the (D)TLS server <span class="bcp14">SHOULD</span> provide OCSP responses in the "CertificateEntry".<a href="#section-7.5-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="sec-considerations">
<section id="section-8">
      <h2 id="name-security-considerations">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-8-1">Most of the security considerations for this document are described
      in <span>[<a href="#RFC5246" class="xref">RFC5246</a>]</span>, <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>, <span>[<a href="#RFC6347" class="xref">RFC6347</a>]</span>, and <span>[<a href="#RFC9147" class="xref">RFC9147</a>]</span>.  In addition, the security
      considerations for Elliptic Curve Cryptography (ECC) related to TLS are
      described in <span>[<a href="#RFC8422" class="xref">RFC8422</a>]</span>, <span>[<a href="#RFC5288" class="xref">RFC5288</a>]</span>, and <span>[<a href="#RFC5289" class="xref">RFC5289</a>]</span>. Readers should consult those documents.<a href="#section-8-1" class="pilcrow">¶</a></p>
<p id="section-8-2">In order to meet the goal of a consistent security level for the entire cipher suite, CNSA (D)TLS implementations <span class="bcp14">MUST</span> only use the elliptic curves, RSA schemes, and Finite Fields defined in <a href="#ecc-curves" class="xref">Section 5.1</a>, <a href="#rsa-schemes" class="xref">Section 5.2</a>, and <a href="#ff-groups" class="xref">Section 5.3</a>, respectively.  If this is not the case, then security may be weaker than is required.<a href="#section-8-2" class="pilcrow">¶</a></p>
<p id="section-8-3">As noted in TLS version 1.3 <span>[<a href="#RFC8446" class="xref">RFC8446</a>]</span>, TLS does not provide inherent replay protections for early data.  For this reason, this profile forbids the use of early data.<a href="#section-8-3" class="pilcrow">¶</a></p>
</section>
</div>
<div id="iana-considerations">
<section id="section-9">
      <h2 id="name-iana-considerations">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-9-1">This document has no IANA actions.<a href="#section-9-1" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-10">
      <h2 id="name-references">
<a href="#section-10" class="section-number selfRef">10. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-10.1">
        <h3 id="name-normative-references">
<a href="#section-10.1" class="section-number selfRef">10.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="AES">[AES]</dt>
        <dd>
<span class="refAuthor">National Institute of Standards and Technology</span>, <span class="refTitle">"Announcing the ADVANCED ENCRYPTION STANDARD (AES)"</span>, <span class="seriesInfo">FIPS 197</span>, <span class="seriesInfo">DOI 10.6028/NIST.FIPS.197</span>, <time datetime="2001-11" class="refDate">November 2001</time>, <span>&lt;<a href="https://nvlpubs.nist.gov/nistpubs/fips/NIST.FIPS.197.pdf">https://nvlpubs.nist.gov/nistpubs/fips/NIST.FIPS.197.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="CNSA">[CNSA]</dt>
        <dd>
<span class="refAuthor">Committee for National Security Systems</span>, <span class="refTitle">"Use of Public Standards for Secure Information Sharing"</span>, <span class="seriesInfo">CNSSP 15</span>, <time datetime="2016-10" class="refDate">October 2016</time>, <span>&lt;<a href="https://www.cnss.gov/CNSS/issuances/Policies.cfm">https://www.cnss.gov/CNSS/issuances/Policies.cfm</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="DSS">[DSS]</dt>
        <dd>
<span class="refAuthor">National Institute of Standards and Technology</span>, <span class="refTitle">"Digital Signature Standard (DSS)"</span>, <span class="seriesInfo">FIPS PUB 186-4</span>, <span class="seriesInfo">DOI 10.6028/NIST.FIPS.186-4</span>, <time datetime="2013-07" class="refDate">July 2013</time>, <span>&lt;<a href="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf">https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.186-4.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="GCM">[GCM]</dt>
        <dd>
<span class="refAuthor">Dworkin, M.</span>, <span class="refTitle">"Recommendation for Block Cipher Modes of Operation: Galois/Counter Mode (GCM) and GMAC"</span>, <span class="seriesInfo">NIST Special Publication 800-38D</span>, <span class="seriesInfo">DOI 10.6028/NIST.SP.800-38D</span>, <time datetime="2007-11" class="refDate">November 2007</time>, <span>&lt;<a href="https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf">https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="PWKE-A">[PWKE-A]</dt>
        <dd>
<span class="refAuthor">Barker, E.</span>, <span class="refAuthor">Chen, L.</span>, <span class="refAuthor">Roginsky, A.</span>, <span class="refAuthor">Vassilev, A.</span>, and <span class="refAuthor">R. Davis</span>, <span class="refTitle">"Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography"</span>, <span class="seriesInfo">NIST Special Publication 800-56A Revision 3</span>, <span class="seriesInfo">DOI 10.6028/NIST.SP.800-56Ar3</span>, <time datetime="2018-04" class="refDate">April 2018</time>, <span>&lt;<a href="https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar3.pdf">https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar3.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="PWKE-B">[PWKE-B]</dt>
        <dd>
<span class="refAuthor">Barker, E.</span>, <span class="refAuthor">Chen, L.</span>, <span class="refAuthor">Roginsky, A.</span>, <span class="refAuthor">Vassilev, A.</span>, <span class="refAuthor">Davis, R.</span>, and <span class="refAuthor">S. Simon</span>, <span class="refTitle">"Recommendation for Pair-Wise Key Establishment Schemes Using Integer Factorization Cryptography"</span>, <span class="seriesInfo">NIST Special Publication 800-56B Revision 2</span>, <span class="seriesInfo">DOI 10.6028/NIST.SP.800-56Br2</span>, <time datetime="2019-03" class="refDate">March 2019</time>, <span>&lt;<a href="https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Br2.pdf">https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Br2.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC2119">[RFC2119]</dt>
        <dd>
<span class="refAuthor">Bradner, S.</span>, <span class="refTitle">"Key words for use in RFCs to Indicate Requirement Levels"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 2119</span>, <span class="seriesInfo">DOI 10.17487/RFC2119</span>, <time datetime="1997-03" class="refDate">March 1997</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5246">[RFC5246]</dt>
        <dd>
<span class="refAuthor">Dierks, T.</span> and <span class="refAuthor">E. Rescorla</span>, <span class="refTitle">"The Transport Layer Security (TLS) Protocol Version 1.2"</span>, <span class="seriesInfo">RFC 5246</span>, <span class="seriesInfo">DOI 10.17487/RFC5246</span>, <time datetime="2008-08" class="refDate">August 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5246">https://www.rfc-editor.org/info/rfc5246</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5288">[RFC5288]</dt>
        <dd>
<span class="refAuthor">Salowey, J.</span>, <span class="refAuthor">Choudhury, A.</span>, and <span class="refAuthor">D. McGrew</span>, <span class="refTitle">"AES Galois Counter Mode (GCM) Cipher Suites for TLS"</span>, <span class="seriesInfo">RFC 5288</span>, <span class="seriesInfo">DOI 10.17487/RFC5288</span>, <time datetime="2008-08" class="refDate">August 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5288">https://www.rfc-editor.org/info/rfc5288</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5289">[RFC5289]</dt>
        <dd>
<span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode (GCM)"</span>, <span class="seriesInfo">RFC 5289</span>, <span class="seriesInfo">DOI 10.17487/RFC5289</span>, <time datetime="2008-08" class="refDate">August 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5289">https://www.rfc-editor.org/info/rfc5289</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6347">[RFC6347]</dt>
        <dd>
<span class="refAuthor">Rescorla, E.</span> and <span class="refAuthor">N. Modadugu</span>, <span class="refTitle">"Datagram Transport Layer Security Version 1.2"</span>, <span class="seriesInfo">RFC 6347</span>, <span class="seriesInfo">DOI 10.17487/RFC6347</span>, <time datetime="2012-01" class="refDate">January 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6347">https://www.rfc-editor.org/info/rfc6347</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7627">[RFC7627]</dt>
        <dd>
<span class="refAuthor">Bhargavan, K., Ed.</span>, <span class="refAuthor">Delignat-Lavaud, A.</span>, <span class="refAuthor">Pironti, A.</span>, <span class="refAuthor">Langley, A.</span>, and <span class="refAuthor">M. Ray</span>, <span class="refTitle">"Transport Layer Security (TLS) Session Hash and Extended Master Secret Extension"</span>, <span class="seriesInfo">RFC 7627</span>, <span class="seriesInfo">DOI 10.17487/RFC7627</span>, <time datetime="2015-09" class="refDate">September 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7627">https://www.rfc-editor.org/info/rfc7627</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7919">[RFC7919]</dt>
        <dd>
<span class="refAuthor">Gillmor, D.</span>, <span class="refTitle">"Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)"</span>, <span class="seriesInfo">RFC 7919</span>, <span class="seriesInfo">DOI 10.17487/RFC7919</span>, <time datetime="2016-08" class="refDate">August 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7919">https://www.rfc-editor.org/info/rfc7919</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8017">[RFC8017]</dt>
        <dd>
<span class="refAuthor">Moriarty, K., Ed.</span>, <span class="refAuthor">Kaliski, B.</span>, <span class="refAuthor">Jonsson, J.</span>, and <span class="refAuthor">A. Rusch</span>, <span class="refTitle">"PKCS #1: RSA Cryptography Specifications Version 2.2"</span>, <span class="seriesInfo">RFC 8017</span>, <span class="seriesInfo">DOI 10.17487/RFC8017</span>, <time datetime="2016-11" class="refDate">November 2016</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8017">https://www.rfc-editor.org/info/rfc8017</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8174">[RFC8174]</dt>
        <dd>
<span class="refAuthor">Leiba, B.</span>, <span class="refTitle">"Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"</span>, <span class="seriesInfo">BCP 14</span>, <span class="seriesInfo">RFC 8174</span>, <span class="seriesInfo">DOI 10.17487/RFC8174</span>, <time datetime="2017-05" class="refDate">May 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8422">[RFC8422]</dt>
        <dd>
<span class="refAuthor">Nir, Y.</span>, <span class="refAuthor">Josefsson, S.</span>, and <span class="refAuthor">M. Pegourie-Gonnard</span>, <span class="refTitle">"Elliptic Curve Cryptography (ECC) Cipher Suites for Transport Layer Security (TLS) Versions 1.2 and Earlier"</span>, <span class="seriesInfo">RFC 8422</span>, <span class="seriesInfo">DOI 10.17487/RFC8422</span>, <time datetime="2018-08" class="refDate">August 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8422">https://www.rfc-editor.org/info/rfc8422</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8446">[RFC8446]</dt>
        <dd>
<span class="refAuthor">Rescorla, E.</span>, <span class="refTitle">"The Transport Layer Security (TLS) Protocol Version 1.3"</span>, <span class="seriesInfo">RFC 8446</span>, <span class="seriesInfo">DOI 10.17487/RFC8446</span>, <time datetime="2018-08" class="refDate">August 2018</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8446">https://www.rfc-editor.org/info/rfc8446</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC8603">[RFC8603]</dt>
        <dd>
<span class="refAuthor">Jenkins, M.</span> and <span class="refAuthor">L. Zieglar</span>, <span class="refTitle">"Commercial National Security Algorithm (CNSA) Suite Certificate and Certificate Revocation List (CRL) Profile"</span>, <span class="seriesInfo">RFC 8603</span>, <span class="seriesInfo">DOI 10.17487/RFC8603</span>, <time datetime="2019-05" class="refDate">May 2019</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8603">https://www.rfc-editor.org/info/rfc8603</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC9147">[RFC9147]</dt>
        <dd>
<span class="refAuthor">Rescorla, E.</span>, <span class="refAuthor">Tschofenig, H.</span>, and <span class="refAuthor">N. Modadugu</span>, <span class="refTitle">"The Datagram Transport Layer Security (DTLS) Protocol Version 1.3"</span>, <span class="seriesInfo">RFC 9147</span>, <span class="seriesInfo">DOI 10.17487/RFC9147</span>, <time datetime="2022-04" class="refDate">April 2022</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc9147">https://www.rfc-editor.org/info/rfc9147</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="SHS">[SHS]</dt>
      <dd>
<span class="refAuthor">National Institute of Standards and Technology (NIST)</span>, <span class="refTitle">"Secure Hash Standard (SHS)"</span>, <span class="seriesInfo">DOI 10.6028/NIST.FIPS.180-4</span>, <span class="seriesInfo">FIPS PUB 180-4</span>, <time datetime="2015-08" class="refDate">August 2015</time>, <span>&lt;<a href="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf">https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-10.2">
        <h3 id="name-informative-references">
<a href="#section-10.2" class="section-number selfRef">10.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="SECG">[SECG]</dt>
        <dd>
<span class="refAuthor">Brown, D.</span>, <span class="refTitle">"SEC 2: Recommended Elliptic Curve Domain Parameters"</span>, <span class="seriesInfo">Version 2.0</span>, <time datetime="2010-02" class="refDate">February 2010</time>, <span>&lt;<a href="https://www.secg.org/sec2-v2.pdf">https://www.secg.org/sec2-v2.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="SP80059">[SP80059]</dt>
      <dd>
<span class="refAuthor">Barker, W.</span>, <span class="refTitle">"Guideline for Identifying an Information System as a National Security System"</span>, <span class="seriesInfo">DOI 10.6028/NIST.SP.800-59</span>, <span class="seriesInfo">NIST Special Publication 800-59</span>, <time datetime="2003-08" class="refDate">August 2003</time>, <span>&lt;<a href="https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-59.pdf">https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-59.pdf</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<div id="authors-addresses">
<section id="appendix-A">
      <h2 id="name-authors-address">
<a href="#name-authors-address" class="section-name selfRef">Author's Address</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Dorothy Cooley</span></div>
<div dir="auto" class="left"><span class="org">National Security Agency</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:decoole@nsa.gov" class="email">decoole@nsa.gov</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>