File: rfc8951.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 (1984 lines) | stat: -rw-r--r-- 82,121 bytes
parent folder | download | duplicates (2)
<!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 8951: Clarification of Enrollment over Secure Transport (EST): Transfer Encodings and ASN.1</title>
<meta content="Michael Richardson" name="author">
<meta content="Thomas Werner" name="author">
<meta content="Wei Pan" name="author">
<meta content='
       This document updates RFC 7030: Enrollment over Secure Transport
      to resolve some errata that were reported and that have proven to
      cause interoperability issues when RFC 7030 was extended. 
       This document deprecates the specification of
      "Content-Transfer-Encoding" headers for Enrollment over Secure Transport
      (EST) endpoints. This document
      fixes some syntactical errors in ASN.1 that were present. 
    ' name="description">
<meta content="xml2rfc 3.5.0" name="generator">
<meta content="8951" name="rfc.number">
<!-- Generator version information:
  xml2rfc 3.5.0
    Python 3.6.10
    appdirs 1.4.4
    ConfigArgParse 1.2.3
    google-i18n-address 2.3.5
    html5lib 1.0.1
    intervaltree 3.0.2
    Jinja2 2.11.2
    kitchen 1.2.6
    lxml 4.4.2
    pycairo 1.19.0
    pycountry 19.8.18
    pyflakes 2.1.1
    PyYAML 5.3.1
    requests 2.22.0
    setuptools 40.6.2
    six 1.14.0
    WeasyPrint 51
-->
<link href="rfc8951.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.compact, .ulCompact,
ol.compact, .olCompact {
  line-height: 100%;
  margin: 0 0 0 2em;
}

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

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

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

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

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

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

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

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

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

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

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

.refInstance {
  margin-bottom: 1.25em;
}

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

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

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

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

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

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

/* pagination */
@media print {
  body {

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

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

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

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

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

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

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

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

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

}

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


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

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

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

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

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

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

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

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

}
/* Tweak the bcp14 keyword presentation */
.bcp14 {
  font-variant: small-caps;
  font-weight: bold;
  font-size: 0.9em;
}
/* Tweak the invisible space above H* in order not to overlay links in text above */
 h2 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 31px;
 }
 h3 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
 h4 {
  margin-top: -18px;  /* provide offset for in-page anchors */
  padding-top: 24px;
 }
/* Float artwork pilcrow to the right */
@media screen {
  .artwork a.pilcrow {
    display: block;
    line-height: 0.7;
    margin-top: 0.15em;
  }
}
/* Make pilcrows on dd visible */
@media screen {
  dd:hover > a.pilcrow {
    visibility: visible;
  }
}
/* Make the placement of figcaption match that of a table's caption
   by removing the figure's added bottom margin */
.alignLeft.art-text,
.alignCenter.art-text,
.alignRight.art-text {
   margin-bottom: 0;
}
.alignLeft,
.alignCenter,
.alignRight {
  margin: 1em 0 0 0;
}
/* In print, the pilcrow won't show on hover, so prevent it from taking up space,
   possibly even requiring a new line */
@media print {
  a.pilcrow {
    display: none;
  }
}
/* Styling for the external metadata */
div#external-metadata {
  background-color: #eee;
  padding: 0.5em;
  margin-bottom: 0.5em;
  display: none;
}
div#internal-metadata {
  padding: 0.5em;                       /* to match the external-metadata padding */
}
/* Styling for title RFC Number */
h1#rfcnum {
  clear: both;
  margin: 0 0 -1em;
  padding: 1em 0 0 0;
}
/* Make .olPercent look the same as <ol><li> */
dl.olPercent > dd {
  margin-bottom: 0.25em;
  min-height: initial;
}
/* Give aside some styling to set it apart */
aside {
  border-left: 1px solid #ddd;
  margin: 1em 0 1em 2em;
  padding: 0.2em 2em;
}
aside > dl,
aside > ol,
aside > ul,
aside > table,
aside > p {
  margin-bottom: 0.5em;
}
/* Additional page break settings */
@media print {
  figcaption, table caption {
    page-break-before: avoid;
  }
}
/* Font size adjustments for print */
@media print {
  body  { font-size: 10pt;      line-height: normal; max-width: 96%; }
  h1    { font-size: 1.72em;    padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */
  h2    { font-size: 1.44em;    padding-top: 1.5em; } /* 1*1.2*1.2 */
  h3    { font-size: 1.2em;     padding-top: 1.5em; } /* 1*1.2 */
  h4    { font-size: 1em;       padding-top: 1.5em; }
  h5, h6 { font-size: 1em;      margin: initial; padding: 0.5em 0 0.3em; }
}
/* Sourcecode margin in print, when there's no pilcrow */
@media print {
  .artwork,
  .sourcecode {
    margin-bottom: 1em;
  }
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}
/* ol type a */
ol.type-a { list-style-type: lower-alpha; }
ol.type-A { list-style-type: upper-alpha; }
ol.type-i { list-style-type: lower-roman; }
ol.type-I { list-style-type: lower-roman; }
/* Apply the print table and row borders in general, on request from the RPC,
and increase the contrast between border and odd row background sligthtly */
table {
  border: 1px solid #ddd;
}
td {
  border-top: 1px solid #ddd;
}
tr:nth-child(2n+1) > td {
  background-color: #f8f8f8;
}
/* Use style rules to govern display of the TOC. */
@media screen and (max-width: 1023px) {
  #toc nav { display: none; }
  #toc.active nav { display: block; }
}
/* Add support for keepWithNext */
.keepWithNext {
  break-after: avoid-page;
  break-after: avoid-page;
}
/* Add support for keepWithPrevious */
.keepWithPrevious {
  break-before: avoid-page;
}
/* Change the approach to avoiding breaks inside artwork etc. */
figure, pre, table, .artwork, .sourcecode  {
  break-before: avoid-page;
  break-after: auto;
}
/* Avoid breaks between <dt> and <dd> */
dl {
  break-before: auto;
  break-inside: auto;
}
dt {
  break-before: auto;
  break-after: avoid-page;
}
dd {
  break-before: avoid-page;
  break-after: auto;
  orphans: 3;
  widows: 3
}
span.break, dd.break {
  margin-bottom: 0;
  min-height: 0;
  break-before: auto;
  break-inside: auto;
  break-after: auto;
}
/* Undo break-before ToC */
@media print {
  #toc {
    break-before: auto;
  }
}
/* Text in compact lists should not get extra bottim margin space,
   since that would makes the list not compact */
ul.compact p, .ulCompact p,
ol.compact p, .olCompact p {
 margin: 0;
}
/* But the list as a whole needs the extra space at the end */
section ul.compact,
section .ulCompact,
section ol.compact,
section .olCompact {
  margin-bottom: 1em;                    /* same as p not within ul.compact etc. */
}
/* The tt and code background above interferes with for instance table cell
   backgrounds.  Changed to something a bit more selective. */
tt, code {
  background-color: transparent;
}
p tt, p code, li tt, li code {
  background-color: #f8f8f8;
}
/* Tweak the pre margin -- 0px doesn't come out well */
pre {
   margin-top: 0.5px;
}
/* Tweak the comact list text */
ul.compact, .ulCompact,
ol.compact, .olCompact,
dl.compact, .dlCompact {
  line-height: normal;
}
/* Don't add top margin for nested lists */
li > ul, li > ol, li > dl,
dd > ul, dd > ol, dd > dl,
dl > dd > dl {
  margin-top: initial;
}
/* Elements that should not be rendered on the same line as a <dt> */
/* This should match the element list in writer.text.TextWriter.render_dl() */
dd > div.artwork:first-child,
dd > aside:first-child,
dd > figure:first-child,
dd > ol:first-child,
dd > div:first-child > pre.sourcecode,
dd > table:first-child,
dd > ul:first-child {
  clear: left;
}
/* fix for weird browser behaviour when <dd/> is empty */
dt+dd:empty::before{
  content: "\00a0";
}
</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc8951" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc7030est-clarify-10" 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 8951</td>
<td class="center">Clarification of EST</td>
<td class="right">November 2020</td>
</tr></thead>
<tfoot><tr>
<td class="left">Richardson, et al.</td>
<td class="center">Standards Track</td>
<td class="right">[Page]</td>
</tr></tfoot>
</table>
<div id="external-metadata" class="document-information"></div>
<div id="internal-metadata" class="document-information">
<dl id="identifiers">
<dt class="label-stream">Stream:</dt>
<dd class="stream">Internet Engineering Task Force (IETF)</dd>
<dt class="label-rfc">RFC:</dt>
<dd class="rfc"><a href="https://www.rfc-editor.org/rfc/rfc8951" class="eref">8951</a></dd>
<dt class="label-updates">Updates:</dt>
<dd class="updates">
<a href="https://www.rfc-editor.org/rfc/rfc7030" class="eref">7030</a> </dd>
<dt class="label-category">Category:</dt>
<dd class="category">Standards Track</dd>
<dt class="label-published">Published:</dt>
<dd class="published">
<time datetime="2020-11" class="published">November 2020</time>
    </dd>
<dt class="label-issn">ISSN:</dt>
<dd class="issn">2070-1721</dd>
<dt class="label-authors">Authors:</dt>
<dd class="authors">
<div class="author">
      <div class="author-name">M. Richardson</div>
<div class="org">Sandelman Software Works</div>
</div>
<div class="author">
      <div class="author-name">T. Werner</div>
<div class="org">Siemens</div>
</div>
<div class="author">
      <div class="author-name">W. Pan</div>
<div class="org">Huawei Technologies</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8951</h1>
<h1 id="title">Clarification of Enrollment over Secure Transport (EST): Transfer Encodings and ASN.1</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">This document updates RFC 7030: Enrollment over Secure Transport
      to resolve some errata that were reported and that have proven to
      cause interoperability issues when RFC 7030 was extended.<a href="#section-abstract-1" class="pilcrow">¶</a></p>
<p id="section-abstract-2">This document deprecates the specification of
      "Content-Transfer-Encoding" headers for Enrollment over Secure Transport
      (EST) endpoints. This document
      fixes some syntactical errors in ASN.1 that were present.<a href="#section-abstract-2" 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 is an Internet Standards Track document.<a href="#section-boilerplate.1-1" class="pilcrow">¶</a></p>
<p id="section-boilerplate.1-2">
            This document is a product of the Internet Engineering Task Force
            (IETF).  It represents the consensus of the IETF community.  It has
            received public review and has been approved for publication by
            the Internet Engineering Steering Group (IESG).  Further
            information on Internet Standards is available in 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/rfc8951">https://www.rfc-editor.org/info/rfc8951</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) 2020 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. Code Components extracted from this
            document must include Simplified BSD License text as described in
            Section 4.e of the Trust Legal Provisions and are provided without
            warranty as described in the Simplified BSD License.<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 ulEmpty">
<li class="compact toc 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><a href="#section-toc.1-1.1.1" class="pilcrow">¶</a></p>
</li>
          <li class="compact toc 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-terminology" class="xref">Terminology</a><a href="#section-toc.1-1.2.1" class="pilcrow">¶</a></p>
</li>
          <li class="compact toc ulEmpty" id="section-toc.1-1.3">
            <p id="section-toc.1-1.3.1"><a href="#section-3" class="xref">3</a>.  <a href="#name-changes-to-est-endpoint-pro" class="xref">Changes to EST Endpoint Processing</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
<ul class="compact toc ulEmpty">
<li class="compact toc ulEmpty" id="section-toc.1-1.3.2.1">
                <p id="section-toc.1-1.3.2.1.1" class="keepWithNext"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-white-space-processing" class="xref">White Space Processing</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="compact toc ulEmpty" id="section-toc.1-1.3.2.2">
                <p id="section-toc.1-1.3.2.2.1"><a href="#section-3.2" class="xref">3.2</a>.  <a href="#name-changes-to-section-4-of-rfc" class="xref">Changes to Section 4 of RFC 7030</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p>
<ul class="compact toc ulEmpty">
<li class="compact toc ulEmpty" id="section-toc.1-1.3.2.2.2.1">
                    <p id="section-toc.1-1.3.2.2.2.1.1"><a href="#section-3.2.1" class="xref">3.2.1</a>.  <a href="#name-section-413" class="xref">Section 4.1.3</a><a href="#section-toc.1-1.3.2.2.2.1.1" class="pilcrow">¶</a></p>
</li>
                  <li class="compact toc ulEmpty" id="section-toc.1-1.3.2.2.2.2">
                    <p id="section-toc.1-1.3.2.2.2.2.1"><a href="#section-3.2.2" class="xref">3.2.2</a>.  <a href="#name-section-431" class="xref">Section 4.3.1</a><a href="#section-toc.1-1.3.2.2.2.2.1" class="pilcrow">¶</a></p>
</li>
                  <li class="compact toc ulEmpty" id="section-toc.1-1.3.2.2.2.3">
                    <p id="section-toc.1-1.3.2.2.2.3.1"><a href="#section-3.2.3" class="xref">3.2.3</a>.  <a href="#name-section-432" class="xref">Section 4.3.2</a><a href="#section-toc.1-1.3.2.2.2.3.1" class="pilcrow">¶</a></p>
</li>
                  <li class="compact toc ulEmpty" id="section-toc.1-1.3.2.2.2.4">
                    <p id="section-toc.1-1.3.2.2.2.4.1"><a href="#section-3.2.4" class="xref">3.2.4</a>.  <a href="#name-section-442" class="xref">Section 4.4.2</a><a href="#section-toc.1-1.3.2.2.2.4.1" class="pilcrow">¶</a></p>
</li>
                  <li class="compact toc ulEmpty" id="section-toc.1-1.3.2.2.2.5">
                    <p id="section-toc.1-1.3.2.2.2.5.1"><a href="#section-3.2.5" class="xref">3.2.5</a>.  <a href="#name-section-452" class="xref">Section 4.5.2</a><a href="#section-toc.1-1.3.2.2.2.5.1" class="pilcrow">¶</a></p>
</li>
                </ul>
</li>
            </ul>
</li>
          <li class="compact toc 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-clarification-of-asn1-for-c" class="xref">Clarification of ASN.1 for Certificate Attribute Set</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
</li>
          <li class="compact toc 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-clarification-of-error-mess" class="xref">Clarification of Error Messages for Certificate Enrollment Operations</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
<ul class="compact toc ulEmpty">
<li class="compact toc 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-updating-section-423-simple" class="xref">Updating Section 4.2.3: Simple Enroll and Re-enroll Response</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="compact toc 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-updating-section-442-server" class="xref">Updating Section 4.4.2: Server-Side Key Generation Response</a><a href="#section-toc.1-1.5.2.2.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="compact toc 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-privacy-considerations" class="xref">Privacy Considerations</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
</li>
          <li class="compact toc 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-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
</li>
          <li class="compact toc 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-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
</li>
          <li class="compact toc 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-references" class="xref">References</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
<ul class="compact toc ulEmpty">
<li class="compact toc ulEmpty" id="section-toc.1-1.9.2.1">
                <p id="section-toc.1-1.9.2.1.1"><a href="#section-9.1" class="xref">9.1</a>.  <a href="#name-normative-references" class="xref">Normative References</a><a href="#section-toc.1-1.9.2.1.1" class="pilcrow">¶</a></p>
</li>
              <li class="compact toc ulEmpty" id="section-toc.1-1.9.2.2">
                <p id="section-toc.1-1.9.2.2.1"><a href="#section-9.2" class="xref">9.2</a>.  <a href="#name-informative-references" class="xref">Informative References</a><a href="#section-toc.1-1.9.2.2.1" class="pilcrow">¶</a></p>
</li>
            </ul>
</li>
          <li class="compact toc ulEmpty" id="section-toc.1-1.10">
            <p id="section-toc.1-1.10.1"><a href="#section-appendix.a" class="xref">Appendix A</a>.  <a href="#name-asn1-module" class="xref">ASN.1 Module</a><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
</li>
          <li class="compact toc ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-acknowledgements" class="xref">Acknowledgements</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
</li>
          <li class="compact toc ulEmpty" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#section-appendix.c" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p>
</li>
        </ul>
</nav>
</section>
</div>
<div id="introduction">
<section id="section-1">
      <h2 id="name-introduction">
<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction" class="section-name selfRef">Introduction</a>
      </h2>
<p id="section-1-1">Enrollment over Secure Transport (EST) is defined in <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span>. The EST specification defines a
      number of HTTP endpoints for certificate enrollment and management. The
      details of the transaction were defined in terms of MIME headers, as
      defined in <span>[<a href="#RFC2045" class="xref">RFC2045</a>]</span>, rather than in
      terms of the HTTP protocol, as defined in <span>[<a href="#RFC7230" class="xref">RFC7230</a>]</span> and <span>[<a href="#RFC7231" class="xref">RFC7231</a>]</span>.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2"><span>[<a href="#RFC2616" class="xref">RFC2616</a>]</span> and later <span><a href="https://www.rfc-editor.org/rfc/rfc7231#appendix-A.5" class="relref">Appendix A.5</a> of [<a href="#RFC7231" class="xref">RFC7231</a>]</span> have text
      specifically deprecating Content-Transfer-Encoding. However, <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span> incorrectly uses this header.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3">Any updates to <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span> to bring it
      in line with HTTP processing risk changing the on-wire protocol in a way
      that is not backwards compatible. However, reports from implementers
      suggest that many implementations do not send the
      Content-Transfer-Encoding, and many of them ignore it. The consequence
      is that simply deprecating the header would remain compatible with
      current implementations.<a href="#section-1-3" class="pilcrow">¶</a></p>
<p id="section-1-4"><span>[<a href="#I-D.ietf-anima-bootstrapping-keyinfra" class="xref">BRSKI</a>]</span> extends <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span>,
      adding new functionality. Interop testing of the protocol has
      revealed that unusual processing called out in <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span> causes confusion.<a href="#section-1-4" class="pilcrow">¶</a></p>
<p id="section-1-5">EST is currently specified as part of <span>[<a href="#IEC62351" class="xref">IEC62351</a>]</span> and is widely used in government, utilities, and
      financial markets today.<a href="#section-1-5" class="pilcrow">¶</a></p>
<p id="section-1-6">This document, therefore, revises <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span> to reflect the field reality, deprecating the
      extraneous field.<a href="#section-1-6" class="pilcrow">¶</a></p>
<p id="section-1-7">This document deals with errata numbers <span>[<a href="#errata4384" class="xref">errata4384</a>]</span>, <span>[<a href="#errata5107" class="xref">errata5107</a>]</span>, <span>[<a href="#errata5108" class="xref">errata5108</a>]</span>, and <span>[<a href="#errata5904" class="xref">errata5904</a>]</span>.<a href="#section-1-7" class="pilcrow">¶</a></p>
<p id="section-1-8">This document deals with <span>[<a href="#errata5107" class="xref">errata5107</a>]</span>
      and <span>[<a href="#errata5904" class="xref">errata5904</a>]</span> in <a href="#estendpoint" class="xref">Section 3</a>. <span>[<a href="#errata5108" class="xref">errata5108</a>]</span> is dealt with in <a href="#error" class="xref">Section 5</a>.  <span>[<a href="#errata4384" class="xref">errata4384</a>]</span> is
      closed by correcting the ASN.1 Module in <a href="#csrasn1" class="xref">Section 4</a>.<a href="#section-1-8" class="pilcrow">¶</a></p>
</section>
</div>
<div id="terminology">
<section id="section-2">
      <h2 id="name-terminology">
<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-terminology" class="section-name selfRef">Terminology</a>
      </h2>
<p id="section-2-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-2-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="estendpoint">
<section id="section-3">
      <h2 id="name-changes-to-est-endpoint-pro">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-changes-to-est-endpoint-pro" class="section-name selfRef">Changes to EST Endpoint Processing</a>
      </h2>
<p id="section-3-1">Sections <a href="https://www.rfc-editor.org/rfc/rfc7030#section-4.1.3" class="relref">4.1.3</a> (CA Certificates Response, /cacerts), <a href="https://www.rfc-editor.org/rfc/rfc7030#section-4.3.1" class="relref">4.3.1</a> and <a href="https://www.rfc-editor.org/rfc/rfc7030#section-4.3.2" class="relref">4.3.2</a> (Full CMC,
      /fullcmc), <a href="https://www.rfc-editor.org/rfc/rfc7030#section-4.4.2" class="relref">4.4.2</a>
      (Server-Side Key Generation, /serverkeygen), and <a href="https://www.rfc-editor.org/rfc/rfc7030#section-4.5.2" class="relref">4.5.2</a> (CSR Attributes, /csrattrs) of
      <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span>
      specify the use of base64 encoding with a Content-Transfer-Encoding for
      requests and responses.<a href="#section-3-1" class="pilcrow">¶</a></p>
<p id="section-3-2">This document updates <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span> to
      require the POST request and payload response of all endpoints using
      base64 encoding, as specified in  <span><a href="https://www.rfc-editor.org/rfc/rfc4648#section-4" class="relref">Section 4</a> of [<a href="#RFC4648" class="xref">RFC4648</a>]</span>. In both cases, the Distinguished
      Encoding Rules (DER) <span>[<a href="#X.690" class="xref">X.690</a>]</span> are used to
      produce the input for the base64 encoding routine. This format is to
      be used regardless of any Content-Transfer-Encoding header, and any
      value in such a header <span class="bcp14">MUST</span> be ignored.<a href="#section-3-2" class="pilcrow">¶</a></p>
<div id="whitespace-processing">
<section id="section-3.1">
        <h3 id="name-white-space-processing">
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-white-space-processing" class="section-name selfRef">White Space Processing</a>
        </h3>
<p id="section-3.1-1">Note that "base64" as used in the HTTP <span>[<a href="#RFC2616" class="xref">RFC2616</a>]</span> does not permit CRLF, while the "base64" used in
 MIME <span>[<a href="#RFC2045" class="xref">RFC2045</a>]</span> does. This
 specification clarifies that despite what <span>[<a href="#RFC2616" class="xref">RFC2616</a>]</span> says, white space including CR, LF, spaces (ASCII
 32), and tabs (ASCII 9) <span class="bcp14">SHOULD</span> be tolerated by
 receivers. Senders are not required to insert any kind of white space.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="changes-sections-4-of-rfc7030">
<section id="section-3.2">
        <h3 id="name-changes-to-section-4-of-rfc">
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-changes-to-section-4-of-rfc" class="section-name selfRef">Changes to Section 4 of RFC 7030</a>
        </h3>
<div id="sect-413">
<section id="section-3.2.1">
          <h4 id="name-section-413">
<a href="#section-3.2.1" class="section-number selfRef">3.2.1. </a><a href="#name-section-413" class="section-name selfRef">Section 4.1.3</a>
          </h4>
<p id="section-3.2.1-1">Replace:<a href="#section-3.2.1-1" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.1-2">
A successful response <span class="bcp14">MUST</span> be a certs-only CMC Simple PKI Response,
as defined in <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span>, containing the certificates described in the
following paragraph.  The HTTP content-type of
"application/pkcs7-mime" is used.  The Simple PKI Response is sent
with a Content-Transfer-Encoding of "base64" <span>[<a href="#RFC2045" class="xref">RFC2045</a>]</span>.<a href="#section-3.2.1-2" class="pilcrow">¶</a>
</blockquote>
<p id="section-3.2.1-3">with:<a href="#section-3.2.1-3" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.1-4">
A successful response <span class="bcp14">MUST</span> be a certs-only CMC Simple PKI Response,
as defined in <span>[<a href="#RFC5272" class="xref">RFC5272</a>]</span>, containing the certificates described in the
following paragraph.  The HTTP content-type of
"application/pkcs7-mime" is used.  The CMC Simple PKI Response is
encoded in base64 <span>[<a href="#RFC4648" class="xref">RFC4648</a>]</span>.<a href="#section-3.2.1-4" class="pilcrow">¶</a>
</blockquote>
</section>
</div>
<div id="sect-431">
<section id="section-3.2.2">
          <h4 id="name-section-431">
<a href="#section-3.2.2" class="section-number selfRef">3.2.2. </a><a href="#name-section-431" class="section-name selfRef">Section 4.3.1</a>
          </h4>
<p id="section-3.2.2-1">Replace:<a href="#section-3.2.2-1" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.2-2">
If the HTTP POST to /fullcmc is not a valid Full PKI Request, the
server <span class="bcp14">MUST</span> reject the message.  The HTTP content-type used is
"application/pkcs7-mime" with an smime-type parameter "CMC-request",
as specified in <span>[<a href="#RFC5273" class="xref">RFC5273</a>]</span>.  The body of the message is the binary
value of the encoding of the PKI Request with a
Content-Transfer-Encoding of "base64" <span>[<a href="#RFC2045" class="xref">RFC2045</a>]</span>.<a href="#section-3.2.2-2" class="pilcrow">¶</a>
</blockquote>
<p id="section-3.2.2-3">with:<a href="#section-3.2.2-3" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.2-4">
If the HTTP POST to /fullcmc is not a valid Full PKI Request, the
server <span class="bcp14">MUST</span> reject the message.  The HTTP content-type used is
"application/pkcs7-mime" with an smime-type parameter "CMC-request",
as specified in <span>[<a href="#RFC5273" class="xref">RFC5273</a>]</span>.  The body of the message is encoded
in base64 <span>[<a href="#RFC4648" class="xref">RFC4648</a>]</span>.<a href="#section-3.2.2-4" class="pilcrow">¶</a>
</blockquote>
</section>
</div>
<div id="sect-432">
<section id="section-3.2.3">
          <h4 id="name-section-432">
<a href="#section-3.2.3" class="section-number selfRef">3.2.3. </a><a href="#name-section-432" class="section-name selfRef">Section 4.3.2</a>
          </h4>
<p id="section-3.2.3-1">Replace:<a href="#section-3.2.3-1" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.3-2">
The body of the message is the binary value of the encoding of the
PKI Response with a Content-Transfer-Encoding of "base64" <span>[<a href="#RFC2045" class="xref">RFC2045</a>]</span>.<a href="#section-3.2.3-2" class="pilcrow">¶</a>
</blockquote>
<p id="section-3.2.3-3">with:<a href="#section-3.2.3-3" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.3-4">
The body of the message is the base64 <span>[<a href="#RFC4648" class="xref">RFC4648</a>]</span> encoding of the
PKI Response.<a href="#section-3.2.3-4" class="pilcrow">¶</a>
</blockquote>
</section>
</div>
<div id="sect-442">
<section id="section-3.2.4">
          <h4 id="name-section-442">
<a href="#section-3.2.4" class="section-number selfRef">3.2.4. </a><a href="#name-section-442" class="section-name selfRef">Section 4.4.2</a>
          </h4>
<p id="section-3.2.4-1">Replace:<a href="#section-3.2.4-1" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.4-2">
An "application/pkcs8"
part consists of the base64-encoded DER-encoded <span>[<a href="#X.690" class="xref">X.690</a>]</span>
PrivateKeyInfo with a Content-Transfer-Encoding of "base64"
<span>[<a href="#RFC2045" class="xref">RFC2045</a>]</span>.<a href="#section-3.2.4-2" class="pilcrow">¶</a>
</blockquote>
<p id="section-3.2.4-3">with:<a href="#section-3.2.4-3" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.4-4">
An "application/pkcs8" part consists of the base64-encoded,
DER-encoded <span>[<a href="#X.690" class="xref">X.690</a>]</span> PrivateKeyInfo.<a href="#section-3.2.4-4" class="pilcrow">¶</a>
</blockquote>
<p id="section-3.2.4-5">Replace:<a href="#section-3.2.4-5" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.4-6">
In all three additional encryption cases, the EnvelopedData is
returned in the response as an "application/pkcs7-mime" part with an
smime-type parameter of "server-generated-key" and a Content-
Transfer-Encoding of "base64".<a href="#section-3.2.4-6" class="pilcrow">¶</a>
</blockquote>
<p id="section-3.2.4-7">with:<a href="#section-3.2.4-7" class="pilcrow">¶</a></p>
<blockquote id="section-3.2.4-8">
In all three additional encryption cases, the EnvelopedData is
returned in the response as an "application/pkcs7-mime" part
with an smime-type parameter of "server-generated-key". It is
base64 encoded <span>[<a href="#RFC4648" class="xref">RFC4648</a>]</span>.<a href="#section-3.2.4-8" class="pilcrow">¶</a>
</blockquote>
</section>
</div>
<div id="sect-452">
<section id="section-3.2.5">
          <h4 id="name-section-452">
<a href="#section-3.2.5" class="section-number selfRef">3.2.5. </a><a href="#name-section-452" class="section-name selfRef">Section 4.5.2</a>
          </h4>
<p id="section-3.2.5-1">This section is updated in its entirety in <a href="#csrasn1" class="xref">Section 4</a>.<a href="#section-3.2.5-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
</section>
</div>
<div id="csrasn1">
<section id="section-4">
      <h2 id="name-clarification-of-asn1-for-c">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-clarification-of-asn1-for-c" class="section-name selfRef">Clarification of ASN.1 for Certificate Attribute Set</a>
      </h2>
<p id="section-4-1"><span><a href="https://www.rfc-editor.org/rfc/rfc7030#section-4.5.2" class="relref">Section 4.5.2</a> of [<a href="#RFC7030" class="xref">RFC7030</a>]</span> is to be
      replaced with the following text:<a href="#section-4-1" class="pilcrow">¶</a></p>
<blockquote id="section-4-2">
        <p id="section-4-2.1">4.5.2 CSR Attributes Response<a href="#section-4-2.1" class="pilcrow">¶</a></p>
<p id="section-4-2.2">If locally configured policy for an authenticated EST client indicates
a CSR Attributes Response is to be provided, the server response <span class="bcp14">MUST</span>
include an HTTP 200 response code.  An HTTP response code of 204 or 404
indicates that a CSR Attributes Response is not available.  Regardless
of the response code, the EST server and CA <span class="bcp14">MAY</span> reject any subsequent
enrollment requests for any reason, e.g., incomplete CSR attributes in
the request.<a href="#section-4-2.2" class="pilcrow">¶</a></p>
<p id="section-4-2.3">Responses to attribute request messages <span class="bcp14">MUST</span> be encoded as the
content-type of "application/csrattrs" and are to be "base64" <span>[<a href="#RFC4648" class="xref">RFC4648</a>]</span>
encoded.  The syntax for application/csrattrs body is as follows:<a href="#section-4-2.3" class="pilcrow">¶</a></p>
<div id="section-4-2.4">
<pre class="sourcecode lang-asn.1">
CsrAttrs ::= SEQUENCE SIZE (0..MAX) OF AttrOrOID

AttrOrOID ::= CHOICE {
  oid        OBJECT IDENTIFIER,
  attribute  Attribute {{AttrSet}} }

AttrSet ATTRIBUTE ::= { ... }
</pre><a href="#section-4-2.4" class="pilcrow">¶</a>
</div>
<p id="section-4-2.5">An EST server includes zero or more OIDs or attributes <span>[<a href="#RFC2986" class="xref">RFC2986</a>]</span> that it requests the client to use
      in the certification request.  The client <span class="bcp14">MUST</span> ignore any
      OID or attribute it does not recognize.  When the server encodes CSR
      attributes as an empty SEQUENCE, it means that the server has no
      specific additional information it desires in a client certification
      request (this is functionally equivalent to an HTTP response code of 204
      or 404).<a href="#section-4-2.5" class="pilcrow">¶</a></p>
<p id="section-4-2.6">If the CA requires a particular cryptographic algorithm or use of a particular
signature scheme (e.g., certification of a public key based on a
certain elliptic curve or signing using a certain hash algorithm), it
<span class="bcp14">MUST</span> provide that information in the CSR Attribute Response.  If an
EST server requires the linking of identity and POP information (see
Section 3.5), it <span class="bcp14">MUST</span> include the challengePassword OID in the CSR
Attributes Response.<a href="#section-4-2.6" class="pilcrow">¶</a></p>
<p id="section-4-2.7">The structure of the CSR Attributes Response <span class="bcp14">SHOULD</span>, to the greatest
extent possible, reflect the structure of the CSR it is requesting.
Requests to use a particular signature scheme (e.g., using a
particular hash function) are represented as an OID to be reflected
in the SignatureAlgorithm of the CSR.  Requests to use a particular
cryptographic algorithm (e.g., certification of a public key based on a certain
elliptic curve) are represented as an attribute, to be reflected as
the AlgorithmIdentifier of the SubjectPublicKeyInfo, with a type
indicating the algorithm and the values indicating the particular
parameters specific to the algorithm.  Requests for descriptive
information from the client are made by an attribute, to be
represented as Attributes of the CSR, with a type indicating the
<span>[<a href="#RFC2985" class="xref">RFC2985</a>]</span> extensionRequest and the values indicating the particular
attributes desired to be included in the resulting certificate's
extensions.<a href="#section-4-2.7" class="pilcrow">¶</a></p>
<p id="section-4-2.8">The sequence is Distinguished Encoding Rules (DER) encoded <span>[<a href="#X.690" class="xref">X.690</a>]</span> and then base64 encoded (<span><a href="https://www.rfc-editor.org/rfc/rfc4648#section-4" class="relref">Section 4</a> of [<a href="#RFC4648" class="xref">RFC4648</a>]</span>).  The resulting text
      forms the application/csrattr body, without headers.<a href="#section-4-2.8" class="pilcrow">¶</a></p>
<p id="section-4-2.9">For example, if a CA requests that a client a) submit a certification 
   request containing the challengePassword (indicating that linking of
   identity and POP information is requested; see Section <a href="https://www.rfc-editor.org/rfc/rfc7030#section-3.5" class="relref">3.5</a>), b) submit an 
   extensionRequest with the Media Access Control (MAC) address
   <span>[<a href="#RFC2307" class="xref">RFC2307</a>]</span> of the client, and c) use the secp384r1 elliptic curve
   to sign using the SHA384 hash function, then it takes the
   following:<a href="#section-4-2.9" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-4-2.10">
<pre>
      OID:        challengePassword (1.2.840.113549.1.9.7)

      Attribute:  type = extensionRequest (1.2.840.113549.1.9.14)
                  value = macAddress (1.3.6.1.1.1.1.22)

      Attribute:  type = id-ecPublicKey (1.2.840.10045.2.1)
                  value = secp384r1 (1.3.132.0.34)

      OID:        ecdsaWithSHA384 (1.2.840.10045.4.3.3)
</pre><a href="#section-4-2.10" class="pilcrow">¶</a>
</div>
<p id="section-4-2.11">and encodes them into an ASN.1 SEQUENCE to produce:<a href="#section-4-2.11" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-4-2.12">
<pre>
 30 41 06 09 2a 86 48 86 f7 0d 01 09 07 30 12 06 07 2a 86 48 ce 3d
 02 01 31 07 06 05 2b 81 04 00 22 30 16 06 09 2a 86 48 86 f7 0d 01
 09 0e 31 09 06 07 2b 06 01 01 01 01 16 06 08 2a 86 48 ce 3d 04 03
 03
</pre><a href="#section-4-2.12" class="pilcrow">¶</a>
</div>
<p id="section-4-2.13">and then base64 encodes the resulting ASN.1 SEQUENCE to produce:<a href="#section-4-2.13" class="pilcrow">¶</a></p>
<div class="artwork art-text alignLeft" id="section-4-2.14">
<pre>
 MEEGCSqGSIb3DQEJBzASBgcqhkjOPQIBMQcGBSuBBAAiMBYGCSqGSIb3DQEJDjEJ
 BgcrBgEBAQEWBggqhkjOPQQDAw==
</pre><a href="#section-4-2.14" class="pilcrow">¶</a>
</div>
</blockquote>
</section>
</div>
<div id="error">
<section id="section-5">
      <h2 id="name-clarification-of-error-mess">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-clarification-of-error-mess" class="section-name selfRef">Clarification of Error Messages for Certificate Enrollment Operations</a>
      </h2>
<p id="section-5-1"><span>[<a href="#errata5108" class="xref">errata5108</a>]</span> clarifies what format
      the error messages are to be in. Previously, a client might be confused
      into believing that an error returned with type text/plain was not
      intended to be an error.<a href="#section-5-1" class="pilcrow">¶</a></p>
<div id="updating-section-423-simple-enroll-and-re-enroll-response">
<section id="section-5.1">
        <h3 id="name-updating-section-423-simple">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-updating-section-423-simple" class="section-name selfRef">Updating Section 4.2.3: Simple Enroll and Re-enroll Response</a>
        </h3>
<p id="section-5.1-1">Replace:<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<blockquote id="section-5.1-2">
    If the content-type is not set, the response data <span class="bcp14">MUST</span> be a
    plaintext human-readable error message containing explanatory
    information describing why the request was rejected (for
    example, indicating that CSR attributes are incomplete).<a href="#section-5.1-2" class="pilcrow">¶</a>
</blockquote>
<p id="section-5.1-3">with:<a href="#section-5.1-3" class="pilcrow">¶</a></p>
<blockquote id="section-5.1-4">
    If the content-type is not set, the response data <span class="bcp14">MUST</span> be a
    plaintext human-readable error message containing explanatory
    information describing why the request was rejected (for
    example, indicating that CSR attributes are incomplete).
    Servers <span class="bcp14">MAY</span> use the "text/plain" content-type <span>[<a href="#RFC2046" class="xref">RFC2046</a>]</span>
    for human-readable errors.<a href="#section-5.1-4" class="pilcrow">¶</a>
</blockquote>
</section>
</div>
<div id="updating-section-442-server-side-key-generation-response">
<section id="section-5.2">
        <h3 id="name-updating-section-442-server">
<a href="#section-5.2" class="section-number selfRef">5.2. </a><a href="#name-updating-section-442-server" class="section-name selfRef">Updating Section 4.4.2: Server-Side Key Generation Response</a>
        </h3>
<p id="section-5.2-1">Replace:<a href="#section-5.2-1" class="pilcrow">¶</a></p>
<blockquote id="section-5.2-2">
    If the content-type is not set, the response data <span class="bcp14">MUST</span> be a
    plaintext human-readable error message.<a href="#section-5.2-2" class="pilcrow">¶</a>
</blockquote>
<p id="section-5.2-3">with:<a href="#section-5.2-3" class="pilcrow">¶</a></p>
<blockquote id="section-5.2-4">
    If the content-type is not set, the response data <span class="bcp14">MUST</span> be a
    plaintext human-readable error message.
    Servers <span class="bcp14">MAY</span> use the "text/plain" content-type <span>[<a href="#RFC2046" class="xref">RFC2046</a>]</span>
    for human-readable errors.<a href="#section-5.2-4" class="pilcrow">¶</a>
</blockquote>
</section>
</div>
</section>
</div>
<div id="privacy-considerations">
<section id="section-6">
      <h2 id="name-privacy-considerations">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-privacy-considerations" class="section-name selfRef">Privacy Considerations</a>
      </h2>
<p id="section-6-1">This document does not disclose any additional identities that either
      an active or passive observer would see with <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span>.<a href="#section-6-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="security-considerations">
<section id="section-7">
      <h2 id="name-security-considerations">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-security-considerations" class="section-name selfRef">Security Considerations</a>
      </h2>
<p id="section-7-1">This document clarifies an existing security mechanism.
It does not create any new protocol mechanisms.<a href="#section-7-1" class="pilcrow">¶</a></p>
<p id="section-7-2">All security considerations from <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span> also apply to the clarifications described in this document.<a href="#section-7-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="iana-considerations">
<section id="section-8">
      <h2 id="name-iana-considerations">
<a href="#section-8" class="section-number selfRef">8. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-8-1">The ASN.1 module in <a href="#asn1-module" class="xref">Appendix A</a> of
      this document makes use of object identifiers (OIDs).<a href="#section-8-1" class="pilcrow">¶</a></p>
<p id="section-8-2">IANA has registered an OID for id-mod-est-2019 (1.3.6.1.5.5.7.0.98)
      in the "SMI Security for PKIX Module Identifier" registry for the ASN.1 module.<a href="#section-8-2" class="pilcrow">¶</a></p>
<p id="section-8-3">The OID for the Asymmetric Decryption Key Identifier (1.2.840.113549.1.9.16.2.54)
      was previously defined in <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span>.
      IANA has updated the Reference column for the Asymmetric
      Decryption Key Identifier attribute to also include a reference to this document.<a href="#section-8-3" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-9">
      <h2 id="name-references">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-references" class="section-name selfRef">References</a>
      </h2>
<section id="section-9.1">
        <h3 id="name-normative-references">
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-normative-references" class="section-name selfRef">Normative References</a>
        </h3>
<dl class="references">
<dt id="errata4384">[errata4384]</dt>
        <dd>
<span class="refAuthor">RFC Errata</span>, <span class="refTitle">Erratum ID 4384</span>, <span class="refContent">RFC 7030</span>, <span>&lt;<a href="https://www.rfc-editor.org/errata/eid4384">https://www.rfc-editor.org/errata/eid4384</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="errata5107">[errata5107]</dt>
        <dd>
<span class="refAuthor">RFC Errata</span>, <span class="refTitle">Erratum ID 5107</span>, <span class="refContent">RFC 7030</span>, <span>&lt;<a href="https://www.rfc-editor.org/errata/eid5107">https://www.rfc-editor.org/errata/eid5107</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="errata5108">[errata5108]</dt>
        <dd>
<span class="refAuthor">RFC Errata</span>, <span class="refTitle">Erratum ID 5108</span>, <span class="refContent">RFC 7030</span>, <span>&lt;<a href="https://www.rfc-editor.org/errata/eid5108">https://www.rfc-editor.org/errata/eid5108</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="errata5904">[errata5904]</dt>
        <dd>
<span class="refAuthor">RFC Errata</span>, <span class="refTitle">Erratum ID 5904</span>, <span class="refContent">RFC 7030</span>, <span>&lt;<a href="https://www.rfc-editor.org/errata/eid5904">https://www.rfc-editor.org/errata/eid5904</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="IEC62351">[IEC62351]</dt>
        <dd>
<span class="refAuthor">International Electrotechnical Commission</span>, <span class="refTitle">"Power systems management and associated information exchange - Data and communications security - Part 9: Cyber security key management for power system equipment"</span>, <span class="seriesInfo">ISO/IEC 62351-9:2017</span>, <time datetime="2017-05" class="refDate">May 2017</time>. </dd>
<dd class="break"></dd>
<dt id="RFC2045">[RFC2045]</dt>
        <dd>
<span class="refAuthor">Freed, N.</span><span class="refAuthor"> and N. Borenstein</span>, <span class="refTitle">"Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies"</span>, <span class="seriesInfo">RFC 2045</span>, <span class="seriesInfo">DOI 10.17487/RFC2045</span>, <time datetime="1996-11" class="refDate">November 1996</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2045">https://www.rfc-editor.org/info/rfc2045</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC2046">[RFC2046]</dt>
        <dd>
<span class="refAuthor">Freed, N.</span><span class="refAuthor"> and N. Borenstein</span>, <span class="refTitle">"Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types"</span>, <span class="seriesInfo">RFC 2046</span>, <span class="seriesInfo">DOI 10.17487/RFC2046</span>, <time datetime="1996-11" class="refDate">November 1996</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2046">https://www.rfc-editor.org/info/rfc2046</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="RFC2986">[RFC2986]</dt>
        <dd>
<span class="refAuthor">Nystrom, M.</span><span class="refAuthor"> and B. Kaliski</span>, <span class="refTitle">"PKCS #10: Certification Request Syntax Specification Version 1.7"</span>, <span class="seriesInfo">RFC 2986</span>, <span class="seriesInfo">DOI 10.17487/RFC2986</span>, <time datetime="2000-11" class="refDate">November 2000</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2986">https://www.rfc-editor.org/info/rfc2986</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC4648">[RFC4648]</dt>
        <dd>
<span class="refAuthor">Josefsson, S.</span>, <span class="refTitle">"The Base16, Base32, and Base64 Data Encodings"</span>, <span class="seriesInfo">RFC 4648</span>, <span class="seriesInfo">DOI 10.17487/RFC4648</span>, <time datetime="2006-10" class="refDate">October 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4648">https://www.rfc-editor.org/info/rfc4648</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5272">[RFC5272]</dt>
        <dd>
<span class="refAuthor">Schaad, J.</span><span class="refAuthor"> and M. Myers</span>, <span class="refTitle">"Certificate Management over CMS (CMC)"</span>, <span class="seriesInfo">RFC 5272</span>, <span class="seriesInfo">DOI 10.17487/RFC5272</span>, <time datetime="2008-06" class="refDate">June 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5272">https://www.rfc-editor.org/info/rfc5272</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5273">[RFC5273]</dt>
        <dd>
<span class="refAuthor">Schaad, J.</span><span class="refAuthor"> and M. Myers</span>, <span class="refTitle">"Certificate Management over CMS (CMC): Transport Protocols"</span>, <span class="seriesInfo">RFC 5273</span>, <span class="seriesInfo">DOI 10.17487/RFC5273</span>, <time datetime="2008-06" class="refDate">June 2008</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5273">https://www.rfc-editor.org/info/rfc5273</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC5912">[RFC5912]</dt>
        <dd>
<span class="refAuthor">Hoffman, P.</span><span class="refAuthor"> and J. Schaad</span>, <span class="refTitle">"New ASN.1 Modules for the Public Key Infrastructure Using X.509 (PKIX)"</span>, <span class="seriesInfo">RFC 5912</span>, <span class="seriesInfo">DOI 10.17487/RFC5912</span>, <time datetime="2010-06" class="refDate">June 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5912">https://www.rfc-editor.org/info/rfc5912</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC6268">[RFC6268]</dt>
        <dd>
<span class="refAuthor">Schaad, J.</span><span class="refAuthor"> and S. Turner</span>, <span class="refTitle">"Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)"</span>, <span class="seriesInfo">RFC 6268</span>, <span class="seriesInfo">DOI 10.17487/RFC6268</span>, <time datetime="2011-07" class="refDate">July 2011</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6268">https://www.rfc-editor.org/info/rfc6268</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7030">[RFC7030]</dt>
        <dd>
<span class="refAuthor">Pritikin, M., Ed.</span><span class="refAuthor">, Yee, P., Ed.</span><span class="refAuthor">, and D. Harkins, Ed.</span>, <span class="refTitle">"Enrollment over Secure Transport"</span>, <span class="seriesInfo">RFC 7030</span>, <span class="seriesInfo">DOI 10.17487/RFC7030</span>, <time datetime="2013-10" class="refDate">October 2013</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7030">https://www.rfc-editor.org/info/rfc7030</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="X.680">[X.680]</dt>
        <dd>
<span class="refAuthor">ITU-T</span>, <span class="refTitle">"Information technology -- Abstract Syntax Notation One (ASN.1): Specification of basic notation"</span>, <span class="seriesInfo">ITU-T Recommendation X.680, ISO/IEC 8824-1:2015</span>, <time datetime="2015-08" class="refDate">August 2015</time>, <span>&lt;<a href="https://www.itu.int/rec/T-REC-X.680-201508-I/en">https://www.itu.int/rec/T-REC-X.680-201508-I/en</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="X.681">[X.681]</dt>
        <dd>
<span class="refAuthor">ITU-T</span>, <span class="refTitle">"Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification"</span>, <span class="seriesInfo">ITU-T Recommendation X.681, ISO/IEC 8824-2:2015</span>, <time datetime="2015-08" class="refDate">August 2015</time>, <span>&lt;<a href="https://www.itu.int/rec/T-REC-X.681">https://www.itu.int/rec/T-REC-X.681</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="X.682">[X.682]</dt>
        <dd>
<span class="refAuthor">ITU-T</span>, <span class="refTitle">"Information Technology - Abstract Syntax Notation One (ASN.1): Constraint specification"</span>, <span class="seriesInfo">ITU-T Recommendation X.682, ISO/IEC 8824-3:2015</span>, <time datetime="2015-08" class="refDate">August 2015</time>, <span>&lt;<a href="https://www.itu.int/rec/T-REC-X.682">https://www.itu.int/rec/T-REC-X.682</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="X.683">[X.683]</dt>
        <dd>
<span class="refAuthor">ITU-T</span>, <span class="refTitle">"Information Technology - Abstract Syntax Notation One (ASN.1): Parameterization of ASN.1 specifications"</span>, <span class="seriesInfo">ITU-T Recommendation X.683, ISO/IEC 8824-4:2015</span>, <time datetime="2015-08" class="refDate">August 2015</time>, <span>&lt;<a href="https://www.itu.int/rec/T-REC-X.683">https://www.itu.int/rec/T-REC-X.683</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="X.690">[X.690]</dt>
      <dd>
<span class="refAuthor">ITU-T</span>, <span class="refTitle">"Information Technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER)"</span>, <span class="seriesInfo">ITU-T Recommendation X.690, ISO/IEC 8825-1:2015</span>, <time datetime="2015-08" class="refDate">August 2015</time>, <span>&lt;<a href="https://www.itu.int/rec/T-REC-X.690">https://www.itu.int/rec/T-REC-X.690</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
<section id="section-9.2">
        <h3 id="name-informative-references">
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-informative-references" class="section-name selfRef">Informative References</a>
        </h3>
<dl class="references">
<dt id="I-D.ietf-anima-bootstrapping-keyinfra">[BRSKI]</dt>
        <dd>
<span class="refAuthor">Pritikin, M.</span><span class="refAuthor">, Richardson, M. C.</span><span class="refAuthor">, Eckert, T.</span><span class="refAuthor">, Behringer, M. H.</span><span class="refAuthor">, and K. Watsen</span>, <span class="refTitle">"Bootstrapping Remote Secure Key Infrastructures (BRSKI)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-anima-bootstrapping-keyinfra-45</span>, <time datetime="2020-11-11" class="refDate">11 November 2020</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-45">https://tools.ietf.org/html/draft-ietf-anima-bootstrapping-keyinfra-45</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC2307">[RFC2307]</dt>
        <dd>
<span class="refAuthor">Howard, L.</span>, <span class="refTitle">"An Approach for Using LDAP as a Network Information Service"</span>, <span class="seriesInfo">RFC 2307</span>, <span class="seriesInfo">DOI 10.17487/RFC2307</span>, <time datetime="1998-03" class="refDate">March 1998</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2307">https://www.rfc-editor.org/info/rfc2307</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC2616">[RFC2616]</dt>
        <dd>
<span class="refAuthor">Fielding, R.</span><span class="refAuthor">, Gettys, J.</span><span class="refAuthor">, Mogul, J.</span><span class="refAuthor">, Frystyk, H.</span><span class="refAuthor">, Masinter, L.</span><span class="refAuthor">, Leach, P.</span><span class="refAuthor">, and T. Berners-Lee</span>, <span class="refTitle">"Hypertext Transfer Protocol -- HTTP/1.1"</span>, <span class="seriesInfo">RFC 2616</span>, <span class="seriesInfo">DOI 10.17487/RFC2616</span>, <time datetime="1999-06" class="refDate">June 1999</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2616">https://www.rfc-editor.org/info/rfc2616</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC2985">[RFC2985]</dt>
        <dd>
<span class="refAuthor">Nystrom, M.</span><span class="refAuthor"> and B. Kaliski</span>, <span class="refTitle">"PKCS #9: Selected Object Classes and Attribute Types Version 2.0"</span>, <span class="seriesInfo">RFC 2985</span>, <span class="seriesInfo">DOI 10.17487/RFC2985</span>, <time datetime="2000-11" class="refDate">November 2000</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc2985">https://www.rfc-editor.org/info/rfc2985</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7230">[RFC7230]</dt>
        <dd>
<span class="refAuthor">Fielding, R., Ed.</span><span class="refAuthor"> and J. Reschke, Ed.</span>, <span class="refTitle">"Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing"</span>, <span class="seriesInfo">RFC 7230</span>, <span class="seriesInfo">DOI 10.17487/RFC7230</span>, <time datetime="2014-06" class="refDate">June 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7230">https://www.rfc-editor.org/info/rfc7230</a>&gt;</span>. </dd>
<dd class="break"></dd>
<dt id="RFC7231">[RFC7231]</dt>
      <dd>
<span class="refAuthor">Fielding, R., Ed.</span><span class="refAuthor"> and J. Reschke, Ed.</span>, <span class="refTitle">"Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content"</span>, <span class="seriesInfo">RFC 7231</span>, <span class="seriesInfo">DOI 10.17487/RFC7231</span>, <time datetime="2014-06" class="refDate">June 2014</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7231">https://www.rfc-editor.org/info/rfc7231</a>&gt;</span>. </dd>
<dd class="break"></dd>
</dl>
</section>
</section>
<div id="asn1-module">
<section id="section-appendix.a">
      <h2 id="name-asn1-module">
<a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-asn1-module" class="section-name selfRef">ASN.1 Module</a>
      </h2>
<p id="section-appendix.a-1">This annex provides the normative ASN.1 definitions for the
      structures described in this specification using ASN.1 as defined in
      <span>[<a href="#X.680" class="xref">X.680</a>]</span>, <span>[<a href="#X.681" class="xref">X.681</a>]</span>, <span>[<a href="#X.682" class="xref">X.682</a>]</span>, and <span>[<a href="#X.683" class="xref">X.683</a>]</span>.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
<p id="section-appendix.a-2">The ASN.1 modules makes imports from the ASN.1 modules in <span>[<a href="#RFC5912" class="xref">RFC5912</a>]</span> and <span>[<a href="#RFC6268" class="xref">RFC6268</a>]</span>.<a href="#section-appendix.a-2" class="pilcrow">¶</a></p>
<p id="section-appendix.a-3">There is no ASN.1 Module in <span>[<a href="#RFC7030" class="xref">RFC7030</a>]</span>.  This module has been created by combining the lines
      that are contained in the document body.<a href="#section-appendix.a-3" class="pilcrow">¶</a></p>
<div id="section-appendix.a-4">
<pre class="sourcecode lang-asn.1">
PKIXEST-2019
     { iso(1) identified-organization(3) dod(6)
       internet(1) security(5) mechanisms(5) pkix(7)
       id-mod(0) id-mod-est-2019(98) }

DEFINITIONS IMPLICIT TAGS ::=
BEGIN

-- EXPORTS ALL --

IMPORTS

Attribute
FROM CryptographicMessageSyntax-2010  -- [RFC6268]
      { iso(1) member-body(2) us(840) rsadsi(113549)
        pkcs(1) pkcs-9(9) smime(16) modules(0)
         id-mod-cms-2009(58) }

ATTRIBUTE
FROM PKIX-CommonTypes-2009 -- [RFC5912]
    { iso(1) identified-organization(3) dod(6) internet(1)
      security(5) mechanisms(5) pkix(7) id-mod(0)
      id-mod-pkixCommon-02(57) } ;


-- CSR Attributes

CsrAttrs ::= SEQUENCE SIZE (0..MAX) OF AttrOrOID

AttrOrOID ::= CHOICE {
   oid        OBJECT IDENTIFIER,
   attribute  Attribute {{AttrSet}} }

AttrSet ATTRIBUTE ::= { ... }


-- Asymmetric Decrypt Key Identifier Attribute

aa-asymmDecryptKeyID ATTRIBUTE ::=
    { TYPE AsymmetricDecryptKeyIdentifier
      IDENTIFIED BY id-aa-asymmDecryptKeyID }

id-aa-asymmDecryptKeyID OBJECT IDENTIFIER ::= { iso(1)
    member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs-9(9)
    smime(16) aa(2) 54 }

AsymmetricDecryptKeyIdentifier ::= OCTET STRING

END
</pre><a href="#section-appendix.a-4" class="pilcrow">¶</a>
</div>
</section>
</div>
<div id="acknowledgements">
<section id="section-appendix.b">
      <h2 id="name-acknowledgements">
<a href="#name-acknowledgements" class="section-name selfRef">Acknowledgements</a>
      </h2>
<p id="section-appendix.b-1">Huawei Technologies supported the efforts of <span class="contact-name">Wei Pan</span> and <span class="contact-name">Michael Richardson</span>.<a href="#section-appendix.b-1" class="pilcrow">¶</a></p>
<p id="section-appendix.b-2">The ASN.1 Module was assembled by <span class="contact-name">Russ Housley</span>
      and formatted by <span class="contact-name">Sean Turner</span>. <span class="contact-name">Russ Housley</span> provided editorial review.<a href="#section-appendix.b-2" class="pilcrow">¶</a></p>
</section>
</div>
<div id="authors-addresses">
<section id="section-appendix.c">
      <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Michael Richardson</span></div>
<div dir="auto" class="left"><span class="org">Sandelman Software Works</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:mcr+ietf@sandelman.ca" class="email">mcr+ietf@sandelman.ca</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Thomas Werner</span></div>
<div dir="auto" class="left"><span class="org">Siemens</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:thomas-werner@siemens.com" class="email">thomas-werner@siemens.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Wei Pan</span></div>
<div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:william.panwei@huawei.com" class="email">william.panwei@huawei.com</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>