File: rfc8697.html

package info (click to toggle)
doc-rfc 20201128-1
links: PTS, VCS
area: non-free
in suites: bullseye
size: 1,307,124 kB
file content (2972 lines) | stat: -rw-r--r-- 147,789 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 8697: Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)</title>
<meta content="Ina Minei" name="author">
<meta content="Edward Crabbe" name="author">
<meta content="Siva Sivabalan" name="author">
<meta content="Hariharan Ananthakrishnan" name="author">
<meta content="Dhruv Dhody" name="author">
<meta content="Yosuke Tanaka" name="author">
<meta content="
       This document introduces a generic mechanism to create a grouping of Label Switched Paths (LSPs) in the
       context of a Path Computation Element (PCE).
       This grouping can then be used to define associations between sets of LSPs or between a
       set of LSPs and a set of attributes (such as configuration parameters
       or behaviors), and it is equally applicable to the stateful PCE (active and passive modes) and the stateless PCE.
       
    " name="description">
<meta content="xml2rfc 2.39.0" name="generator">
<meta content="PCE" name="keyword">
<meta content="PCEP" name="keyword">
<meta content="Association" name="keyword">
<meta content="Group" name="keyword">
<meta content="8697" name="rfc.number">
<link href="rfc8697.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;
  }

}
/* Avoid wrapping of URLs in references */
@media screen {
  .references a {
    white-space: nowrap;
  }
}
/* 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: 0 0 0.25em 0;
  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;
  }
}
/*
  The margin-left: 0 on <dd> removes all distinction
  between levels from nested <dl>s.  Undo that.
*/
dl.olPercent > dd,
dd {
  margin-left: revert;
}
/* Avoid narrow tables forcing too narrow table captions, which may render badly */
table {
  min-width: 20em;
}</style>
<link href="rfc-local.css" rel="stylesheet" type="text/css">
<link href="https://dx.doi.org/10.17487/rfc8697" rel="alternate">
  <link href="urn:issn:2070-1721" rel="alternate">
  <link href="https://datatracker.ietf.org/doc/draft-ietf-pce-association-group-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 8697</td>
<td class="center">PCE Association Group</td>
<td class="right">January 2020</td>
</tr></thead>
<tfoot><tr>
<td class="left">Minei, 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/rfc8697" class="eref">8697</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-01" class="published">January 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">I. Minei</div>
<div class="org">Google, Inc.</div>
</div>
<div class="author">
      <div class="author-name">E. Crabbe</div>
<div class="org">Individual Contributor</div>
</div>
<div class="author">
      <div class="author-name">S. Sivabalan</div>
<div class="org">Cisco Systems, Inc.</div>
</div>
<div class="author">
      <div class="author-name">H. Ananthakrishnan</div>
<div class="org">Netflix</div>
</div>
<div class="author">
      <div class="author-name">D. Dhody</div>
<div class="org">Huawei</div>
</div>
<div class="author">
      <div class="author-name">Y. Tanaka</div>
<div class="org">NTT Communications Corporation</div>
</div>
</dd>
</dl>
</div>
<h1 id="rfcnum">RFC 8697</h1>
<h1 id="title">Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)</h1>
<section id="section-abstract">
      <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="section-abstract-1">This document introduces a generic mechanism to create a grouping of Label Switched Paths (LSPs) in the
       context of a Path Computation Element (PCE).
       This grouping can then be used to define associations between sets of LSPs or between a
       set of LSPs and a set of attributes (such as configuration parameters
       or behaviors), and it is equally applicable to the stateful PCE (active and passive modes) and the stateless PCE.<a href="#section-abstract-1" 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/rfc8697">https://www.rfc-editor.org/info/rfc8697</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="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.1">
            <p id="section-toc.1-1.1.1"><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>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.1.2.1">
                <p id="section-toc.1-1.1.2.1.1"><a href="#section-1.1" class="xref">1.1</a>.  <a href="#name-requirements-language" class="xref">Requirements Language</a><a href="#section-toc.1-1.1.2.1.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.2">
            <p id="section-toc.1-1.2.1"><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="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-architectural-overview" class="xref">Architectural Overview</a><a href="#section-toc.1-1.3.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.3.2.1">
                <p id="section-toc.1-1.3.2.1.1"><a href="#section-3.1" class="xref">3.1</a>.  <a href="#name-motivations" class="xref">Motivations</a><a href="#section-toc.1-1.3.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="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-relationship-to-the-svec-li" class="xref">Relationship to the SVEC List</a><a href="#section-toc.1-1.3.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.3">
                <p id="section-toc.1-1.3.2.3.1"><a href="#section-3.3" class="xref">3.3</a>.  <a href="#name-operational-overview" class="xref">Operational Overview</a><a href="#section-toc.1-1.3.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.3.2.4">
                <p id="section-toc.1-1.3.2.4.1"><a href="#section-3.4" class="xref">3.4</a>.  <a href="#name-operator-configured-associa" class="xref">Operator-Configured Association Range</a><a href="#section-toc.1-1.3.2.4.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="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-discovery-of-supported-asso" class="xref">Discovery of Supported Association Types</a><a href="#section-toc.1-1.4.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc 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-assoc-type-list-tlv" class="xref">ASSOC-Type-List TLV</a><a href="#section-toc.1-1.4.2.1.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.4.2.1.2.1">
                    <p id="section-toc.1-1.4.2.1.2.1.1"><a href="#section-4.1.1" class="xref">4.1.1</a>.  <a href="#name-procedure" class="xref">Procedure</a><a href="#section-toc.1-1.4.2.1.2.1.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
</ul>
</li>
<li class="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-operator-configured-associat" class="xref">Operator-Configured Association Range TLV</a><a href="#section-toc.1-1.5.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="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-procedure-2" class="xref">Procedure</a><a href="#section-toc.1-1.5.2.1.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="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-association-object" class="xref">ASSOCIATION Object</a><a href="#section-toc.1-1.6.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc 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-object-definition" class="xref">Object Definition</a><a href="#section-toc.1-1.6.2.1.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.6.2.1.2.1">
                    <p id="section-toc.1-1.6.2.1.2.1.1"><a href="#section-6.1.1" class="xref">6.1.1</a>.  <a href="#name-global-association-source-t" class="xref">Global Association Source TLV</a><a href="#section-toc.1-1.6.2.1.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.6.2.1.2.2">
                    <p id="section-toc.1-1.6.2.1.2.2.1"><a href="#section-6.1.2" class="xref">6.1.2</a>.  <a href="#name-extended-association-id-tlv" class="xref">Extended Association ID TLV</a><a href="#section-toc.1-1.6.2.1.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.6.2.1.2.3">
                    <p id="section-toc.1-1.6.2.1.2.3.1"><a href="#section-6.1.3" class="xref">6.1.3</a>.  <a href="#name-association-source" class="xref">Association Source</a><a href="#section-toc.1-1.6.2.1.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.6.2.1.2.4">
                    <p id="section-toc.1-1.6.2.1.2.4.1"><a href="#section-6.1.4" class="xref">6.1.4</a>.  <a href="#name-unique-identification-for-a" class="xref">Unique Identification for an Association Group</a><a href="#section-toc.1-1.6.2.1.2.4.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc 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-relationship-to-the-rsvp-as" class="xref">Relationship to the RSVP ASSOCIATION Object</a><a href="#section-toc.1-1.6.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc 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-object-encoding-in-pcep-mes" class="xref">Object Encoding in PCEP Messages</a><a href="#section-toc.1-1.6.2.3.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc ulEmpty" id="section-toc.1-1.6.2.3.2.1">
                    <p id="section-toc.1-1.6.2.3.2.1.1"><a href="#section-6.3.1" class="xref">6.3.1</a>.  <a href="#name-stateful-pcep-messages" class="xref">Stateful PCEP Messages</a><a href="#section-toc.1-1.6.2.3.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.6.2.3.2.2">
                    <p id="section-toc.1-1.6.2.3.2.2.1"><a href="#section-6.3.2" class="xref">6.3.2</a>.  <a href="#name-request-message" class="xref">Request Message</a><a href="#section-toc.1-1.6.2.3.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.6.2.3.2.3">
                    <p id="section-toc.1-1.6.2.3.2.3.1"><a href="#section-6.3.3" class="xref">6.3.3</a>.  <a href="#name-reply-message" class="xref">Reply Message</a><a href="#section-toc.1-1.6.2.3.2.3.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc 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-processing-rules" class="xref">Processing Rules</a><a href="#section-toc.1-1.6.2.4.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="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-iana-considerations" class="xref">IANA Considerations</a><a href="#section-toc.1-1.7.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc 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-pcep-object" class="xref">PCEP Object</a><a href="#section-toc.1-1.7.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc 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-pcep-tlv" class="xref">PCEP TLV</a><a href="#section-toc.1-1.7.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc 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-association-flags" class="xref">Association Flags</a><a href="#section-toc.1-1.7.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc 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-association-type" class="xref">Association Type</a><a href="#section-toc.1-1.7.2.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc 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-pcep-error-object" class="xref">PCEP-Error Object</a><a href="#section-toc.1-1.7.2.5.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="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-security-considerations" class="xref">Security Considerations</a><a href="#section-toc.1-1.8.1" class="pilcrow">¶</a></p>
</li>
<li class="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-manageability-consideration" class="xref">Manageability Considerations</a><a href="#section-toc.1-1.9.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="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-control-of-function-and-pol" class="xref">Control of Function and Policy</a><a href="#section-toc.1-1.9.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="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-information-and-data-models" class="xref">Information and Data Models</a><a href="#section-toc.1-1.9.2.2.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.9.2.3">
                <p id="section-toc.1-1.9.2.3.1"><a href="#section-9.3" class="xref">9.3</a>.  <a href="#name-liveness-detection-and-moni" class="xref">Liveness Detection and Monitoring</a><a href="#section-toc.1-1.9.2.3.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.9.2.4">
                <p id="section-toc.1-1.9.2.4.1"><a href="#section-9.4" class="xref">9.4</a>.  <a href="#name-verifying-correct-operation" class="xref">Verifying Correct Operation</a><a href="#section-toc.1-1.9.2.4.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.9.2.5">
                <p id="section-toc.1-1.9.2.5.1"><a href="#section-9.5" class="xref">9.5</a>.  <a href="#name-requirements-on-other-proto" class="xref">Requirements on Other Protocols</a><a href="#section-toc.1-1.9.2.5.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.9.2.6">
                <p id="section-toc.1-1.9.2.6.1"><a href="#section-9.6" class="xref">9.6</a>.  <a href="#name-impact-on-network-operation" class="xref">Impact on Network Operations</a><a href="#section-toc.1-1.9.2.6.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc 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><a href="#section-toc.1-1.10.1" class="pilcrow">¶</a></p>
<ul class="toc ulEmpty">
<li class="toc 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><a href="#section-toc.1-1.10.2.1.1" class="pilcrow">¶</a></p>
</li>
<li class="toc 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><a href="#section-toc.1-1.10.2.2.1" class="pilcrow">¶</a></p>
</li>
</ul>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.11">
            <p id="section-toc.1-1.11.1"><a href="#section-appendix.a" class="xref">Appendix A</a>.  <a href="#name-example-of-an-operator-conf" class="xref">Example of an Operator-Configured Association Range</a><a href="#section-toc.1-1.11.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.12">
            <p id="section-toc.1-1.12.1"><a href="#section-appendix.b" class="xref"></a><a href="#name-acknowledgments" class="xref">Acknowledgments</a><a href="#section-toc.1-1.12.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.13">
            <p id="section-toc.1-1.13.1"><a href="#section-appendix.c" class="xref"></a><a href="#name-contributors" class="xref">Contributors</a><a href="#section-toc.1-1.13.1" class="pilcrow">¶</a></p>
</li>
<li class="toc ulEmpty" id="section-toc.1-1.14">
            <p id="section-toc.1-1.14.1"><a href="#section-appendix.d" class="xref"></a><a href="#name-authors-addresses" class="xref">Authors' Addresses</a><a href="#section-toc.1-1.14.1" class="pilcrow">¶</a></p>
</li>
</ul>
</nav>
</section>
</div>
<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"><span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> describes the Path Computation Element (PCE)
      Communication Protocol (PCEP).  PCEP enables communication between a
      Path Computation Client (PCC) and a PCE, or between a PCE and another
      PCE, for the purpose of the computation of Multiprotocol Label Switching
      (MPLS) as well as Generalized MPLS (GMPLS) Traffic Engineering Label
      Switched Path (TE LSP) characteristics.<a href="#section-1-1" class="pilcrow">¶</a></p>
<p id="section-1-2"><span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span> specifies a set of extensions to PCEP
      to enable stateful control of TE LSPs within and across PCEP sessions in
      compliance with <span>[<a href="#RFC4657" class="xref">RFC4657</a>]</span>. It includes mechanisms to
      effect LSP State Synchronization between PCCs and PCEs, delegation of
      control over LSPs to PCEs, and PCE control of timing and sequence of
      path computations within and across PCEP sessions. The operational model
      whereby LSPs are initiated from the PCE is described in <span>[<a href="#RFC8281" class="xref">RFC8281</a>]</span>.<a href="#section-1-2" class="pilcrow">¶</a></p>
<p id="section-1-3"><span>[<a href="#RFC4872" class="xref">RFC4872</a>]</span> defines the RSVP ASSOCIATION object, which
      was defined in the context of GMPLS-controlled LSPs to be used to
      associate recovery LSPs with the LSP they are protecting. This object
      also has broader applicability as a mechanism to associate RSVP
      state. <span>[<a href="#RFC6780" class="xref">RFC6780</a>]</span> describes how the ASSOCIATION object can
      be more generally applied by defining the Extended ASSOCIATION
      object.<a href="#section-1-3" class="pilcrow">¶</a></p>
<p id="section-1-4"> This document introduces a generic mechanism to create a grouping of LSPs.
       This grouping can then be used to define associations between sets of LSPs or between a
       set of LSPs and a set of attributes (such as configuration parameters
       or behaviors), and it is equally applicable to the stateful PCE (active
       and passive modes) and the stateless PCE.
       The associations could be created dynamically and conveyed to a PCEP
       peer within PCEP, or they could be configured manually by an operator
       on the PCEP peers. Refer to <a href="#Operation-overview" class="xref">Section 3.3</a> for
       more details.<a href="#section-1-4" class="pilcrow">¶</a></p>
<section id="section-1.1">
        <h3 id="name-requirements-language">
<a href="#section-1.1" class="section-number selfRef">1.1. </a><a href="#name-requirements-language" class="section-name selfRef">Requirements Language</a>
        </h3>
<p id="section-1.1-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-1.1-1" class="pilcrow">¶</a></p>
</section>
</section>
<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">This document uses the following terms defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>:<a href="#section-2-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-2-2.1">PCC<a href="#section-2-2.1" class="pilcrow">¶</a>
</li>
<li id="section-2-2.2">PCE<a href="#section-2-2.2" class="pilcrow">¶</a>
</li>
<li id="section-2-2.3">PCEP Peer<a href="#section-2-2.3" class="pilcrow">¶</a>
</li>
<li id="section-2-2.4">Path Computation Request (PCReq)<a href="#section-2-2.4" class="pilcrow">¶</a>
</li>
<li id="section-2-2.5">Path Computation Reply (PCRep)<a href="#section-2-2.5" class="pilcrow">¶</a>
</li>
<li id="section-2-2.6">PCEP Error (PCErr)<a href="#section-2-2.6" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-2-3">This document uses the following terms defined in <span>[<a href="#RFC8051" class="xref">RFC8051</a>]</span>:<a href="#section-2-3" class="pilcrow">¶</a></p>
<ul>
<li id="section-2-4.1">Stateful PCE<a href="#section-2-4.1" class="pilcrow">¶</a>
</li>
<li id="section-2-4.2">Active Stateful PCE<a href="#section-2-4.2" class="pilcrow">¶</a>
</li>
<li id="section-2-4.3">Passive Stateful PCE<a href="#section-2-4.3" class="pilcrow">¶</a>
</li>
<li id="section-2-4.4">Delegation<a href="#section-2-4.4" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-2-5">This document uses the following terms defined in <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>:<a href="#section-2-5" class="pilcrow">¶</a></p>
<ul>
<li id="section-2-6.1">LSP State Report (PCRpt)<a href="#section-2-6.1" class="pilcrow">¶</a>
</li>
<li id="section-2-6.2">LSP Update Request (PCUpd)<a href="#section-2-6.2" class="pilcrow">¶</a>
</li>
<li id="section-2-6.3">State Timeout Interval<a href="#section-2-6.3" class="pilcrow">¶</a>
</li>
</ul>
<p id="section-2-7">This document uses the following terms defined in <span>[<a href="#RFC8281" class="xref">RFC8281</a>]</span>:<a href="#section-2-7" class="pilcrow">¶</a></p>
<ul>
<li id="section-2-8.1">PCE-initiated LSP<a href="#section-2-8.1" class="pilcrow">¶</a>
</li>
<li id="section-2-8.2">LSP Initiate Request (PCInitiate)<a href="#section-2-8.2" class="pilcrow">¶</a>
</li>
</ul>
</section>
<div id="Overview">
<section id="section-3">
      <h2 id="name-architectural-overview">
<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-architectural-overview" class="section-name selfRef">Architectural Overview</a>
      </h2>
<div id="Motivation">
<section id="section-3.1">
        <h3 id="name-motivations">
<a href="#section-3.1" class="section-number selfRef">3.1. </a><a href="#name-motivations" class="section-name selfRef">Motivations</a>
        </h3>
<p id="section-3.1-1">A stateful PCE provides the ability to update existing LSPs and to
     instantiate new ones. There are various situations where several
     LSPs need to share common information. For example, to support
     PCE-controlled make-before-break, an association between the original
     path and the reoptimized path is desired. Similarly, for end-to-end
     protection, an association between working and protection LSPs is
     required (see <span>[<a href="#I-D.ietf-pce-stateful-path-protection" class="xref">PCE-PROTECTION</a>]</span>). For diverse paths, an
     association between a group of LSPs could be used (see <span>[<a href="#I-D.ietf-pce-association-diversity" class="xref">PCE-DIVERSITY</a>]</span>).  Another use for an LSP grouping would be to apply
     a common set of configuration parameters or behaviors to a set of LSPs.<a href="#section-3.1-1" class="pilcrow">¶</a></p>
<p id="section-3.1-2">
      For a  stateless PCE, it might be useful to associate a PCReq message to an association group, thus enabling it to associate
      a common set of policies, configuration parameters, or behaviors with the request.<a href="#section-3.1-2" class="pilcrow">¶</a></p>
<p id="section-3.1-3">Some associations could be created dynamically, such as an association
     between the working and protection LSPs of a tunnel, whereas
     some associations could be created by the operator manually, such as
     a policy-based association where the LSP could join an
     operator-configured existing association.<a href="#section-3.1-3" class="pilcrow">¶</a></p>
<p id="section-3.1-4">
     Rather than creating separate mechanisms for each use case, this document
     defines a generic mechanism that can be reused as needed.<a href="#section-3.1-4" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-3.2">
        <h3 id="name-relationship-to-the-svec-li">
<a href="#section-3.2" class="section-number selfRef">3.2. </a><a href="#name-relationship-to-the-svec-li" class="section-name selfRef">Relationship to the SVEC List</a>
        </h3>
<p id="section-3.2-1">Note that <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> defines a mechanism for the
       synchronization of a set of PCReq messages by using the SVEC
       (Synchronization VECtor) object, which specifies the list of
       synchronized requests that can be either dependent or independent. The
       SVEC object identifies the relationship between the set of
       PCReq messages, identified by "Request-ID-number" in the RP
       (Request Parameters) object. <span>[<a href="#RFC6007" class="xref">RFC6007</a>]</span> further clarifies
       the use of the SVEC list for synchronized path computations when
       computing dependent requests, and it describes a number of usage
       scenarios for SVEC lists within single-domain and multi-domain
       environments.<a href="#section-3.2-1" class="pilcrow">¶</a></p>
<p id="section-3.2-2">The motivations behind the association group defined in this document
   and the SVEC object are quite different, though some use cases may
   overlap.  PCEP extensions that define a new Association Type should
   clarify the relationship between the SVEC object and the Association
   Type, if any.<a href="#section-3.2-2" class="pilcrow">¶</a></p>
</section>
<div id="Operation-overview">
<section id="section-3.3">
        <h3 id="name-operational-overview">
<a href="#section-3.3" class="section-number selfRef">3.3. </a><a href="#name-operational-overview" class="section-name selfRef">Operational Overview</a>
        </h3>
<p id="section-3.3-1">
     LSPs are associated with other LSPs with which they interact by
     adding them to a common association group.  Association groups as
     defined in this document can be applied to LSPs originating at the same
     headend or different headends.<a href="#section-3.3-1" class="pilcrow">¶</a></p>
<p id="section-3.3-2">Some associations could be created dynamically by a PCEP speaker, and
     the associations (along with the set of LSPs) are conveyed to a PCEP
     peer. Whereas some associations are configured by the operator
     beforehand on the PCEP peers in question, a PCEP speaker could then ask
     an LSP to join the Operator-configured Association. Usage of dynamic and
     configured associations is usually dependent on the type of
     association.<a href="#section-3.3-2" class="pilcrow">¶</a></p>
<p id="section-3.3-3">For Operator-configured Associations, the association
parameters, such as the Association Identifier (Association ID), Association Type, and
the Association Source IP address, are manually configured by the
operator. In the case of a dynamic association, the association parameters,
such as the Association ID, are allocated dynamically by the
PCEP speaker. The Association Source is set as the local PCEP speaker
address unless local policy dictates otherwise, in which case the
Association Source is set based on the local policy.<a href="#section-3.3-3" class="pilcrow">¶</a></p>
<p id="section-3.3-4">The dynamically created association can be reported to the PCEP peer
     via the PCEP messages as per the stateful extensions. When the
     Operator-configured Association is known to the PCEP peer beforehand, a
     PCEP peer could ask an LSP to join the Operator-configured Association
     via the stateful PCEP messages.<a href="#section-3.3-4" class="pilcrow">¶</a></p>
<p id="section-3.3-5">The associations are properties of the LSP and thus could be stored in
    the LSP state database. The dynamic association exists as long as the LSP
state exists. In the case of PCEP session termination, the LSP state cleanup
    <span class="bcp14">MUST</span> also take care of associations.<a href="#section-3.3-5" class="pilcrow">¶</a></p>
<p id="section-3.3-6">Multiple types of associations can exist, each with its own
     Association ID space. The definition of the different Association
     Types and their behaviors is outside the scope of this document.  The
     establishment and removal of the association relationship can be done on
     a per-LSP basis. An LSP may join multiple association groups that have
     the same Association Type or different Association Types.<a href="#section-3.3-6" class="pilcrow">¶</a></p>
</section>
</div>
<div id="Range">
<section id="section-3.4">
        <h3 id="name-operator-configured-associa">
<a href="#section-3.4" class="section-number selfRef">3.4. </a><a href="#name-operator-configured-associa" class="section-name selfRef">Operator-Configured Association Range</a>
        </h3>
<p id="section-3.4-1">Some Association Types are dynamic, some are operator configured,
       and some could be both. For the Association Types that could be both
       dynamic and operator configured and use the same
       Association Source, it is necessary to distinguish a range of
       Association IDs that are marked for Operator-configured
       Associations, to avoid any Association ID clashes within the
       scope of the Association Source. This document assumes that these two
       ranges are configured.<a href="#section-3.4-1" class="pilcrow">¶</a></p>
<p id="section-3.4-2">A range of Association IDs for each Association Type (and
       Association Source) is kept for the Operator-configured
       Associations. Dynamic associations <span class="bcp14">MUST NOT</span> use the
       Association ID from this range.<a href="#section-3.4-2" class="pilcrow">¶</a></p>
<p id="section-3.4-3">This range, as set at the PCEP speaker (a PCC or PCE, as an
       Association Source), needs to be communicated to a PCEP peer in the
       Open message. A new TLV is defined in this specification for this
       purpose (<a href="#Range-tlv" class="xref">Section 5</a>). See <a href="#ex" class="xref">Appendix A</a> for an
       example.<a href="#section-3.4-3" class="pilcrow">¶</a></p>
<p id="section-3.4-4">The Association ID range for sources other than the PCEP
       speaker (for example, a Network Management System (NMS)) is not
       communicated in PCEP, and the procedure for Operator-configured
       Association Range settings is outside the scope of this document.<a href="#section-3.4-4" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="Discovery">
<section id="section-4">
      <h2 id="name-discovery-of-supported-asso">
<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-discovery-of-supported-asso" class="section-name selfRef">Discovery of Supported Association Types</a>
      </h2>
<p id="section-4-1">This section defines PCEP extensions so as to support
   the capability advertisement of the Association Types supported by a PCEP speaker.<a href="#section-4-1" class="pilcrow">¶</a></p>
<p id="section-4-2">A new PCEP ASSOC-Type-List (Association Types list) TLV is defined.  The
   PCEP ASSOC-Type-List TLV is carried within an OPEN object.  This way, during
   the PCEP session-setup phase, a PCEP speaker can advertise to a PCEP peer
   the list of supported Association Types.<a href="#section-4-2" class="pilcrow">¶</a></p>
<section id="section-4.1">
        <h3 id="name-assoc-type-list-tlv">
<a href="#section-4.1" class="section-number selfRef">4.1. </a><a href="#name-assoc-type-list-tlv" class="section-name selfRef">ASSOC-Type-List TLV</a>
        </h3>
<p id="section-4.1-1">The PCEP ASSOC-Type-List TLV is <span class="bcp14">OPTIONAL</span>.  It <span class="bcp14">MAY</span> be carried within an OPEN
   object sent by a PCEP speaker in an Open message to a PCEP peer so as to
   indicate the list of supported Association Types.<a href="#section-4.1-1" class="pilcrow">¶</a></p>
<p id="section-4.1-2">The PCEP ASSOC-Type-List TLV format is compliant with the PCEP TLV format defined
   in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>.  That is, the TLV is composed of 2 octets
   for the type, 2 octets specifying the TLV length, and a Value field.  The Length
   field defines the length of the value portion in octets.  The TLV is
   padded to 4-octet alignment, and padding is not included in the
   Length field (e.g., a 3-octet value would have a length of three, but
   the total size of the TLV would be 8 octets).<a href="#section-4.1-2" class="pilcrow">¶</a></p>
<p id="section-4.1-3">The PCEP ASSOC-Type-List TLV has the following format:<a href="#section-4.1-3" class="pilcrow">¶</a></p>
<span id="name-the-assoc-type-list-tlv-for"></span><div id="ASSOC-Type-List">
<figure id="figure-1">
          <div class="artwork art-text alignLeft" id="section-4.1-4.1">
<pre>
   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |         Type                  |            Length             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  
  |          Assoc-Type #1        |      Assoc-Type #2            |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  //                                                             //
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |          Assoc-Type #N        |       padding                 |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ </pre>
</div>
<figcaption><a href="#figure-1" class="selfRef">Figure 1</a>:
<a href="#name-the-assoc-type-list-tlv-for" class="selfRef">The ASSOC-Type-List TLV Format</a>
          </figcaption></figure>
</div>
<dl class="dlParallel" id="section-4.1-5">
          <dt id="section-4.1-5.1">Type:</dt>
<dd id="section-4.1-5.2">35<a href="#section-4.1-5.2" class="pilcrow">¶</a>
</dd>
<dt id="section-4.1-5.3">Length:</dt>
<dd id="section-4.1-5.4">N * 2 (where N is the number of Association Types).<a href="#section-4.1-5.4" class="pilcrow">¶</a>
</dd>
<dt id="section-4.1-5.5">Value:</dt>
<dd id="section-4.1-5.6">List of 2-byte Association Type code points, identifying
    the Association Types supported by the sender of the Open
    message.<a href="#section-4.1-5.6" class="pilcrow">¶</a>
</dd>
<dt id="section-4.1-5.7">Assoc-Type (2 bytes):</dt>
<dd id="section-4.1-5.8">Association Type code point identifier.
  IANA manages the "ASSOCIATION Type Field" code point registry (see <a href="#iana_assoc_type" class="xref">Section 7.4</a>).<a href="#section-4.1-5.8" class="pilcrow">¶</a>
</dd>
</dl>
<section id="section-4.1.1">
          <h4 id="name-procedure">
<a href="#section-4.1.1" class="section-number selfRef">4.1.1. </a><a href="#name-procedure" class="section-name selfRef">Procedure</a>
          </h4>
<p id="section-4.1.1-1">An ASSOC-Type-List TLV within an OPEN object in an Open
   message is included by a PCEP speaker in order to advertise a set of one or
   more supported Association Types.  The ASSOC-Type-List TLV <span class="bcp14">MUST NOT</span> appear more than
   once in an OPEN object.  If it appears more than once, the PCEP
   session <span class="bcp14">MUST</span> be rejected with Error-Type 1 and Error-value 1 (PCEP
   session establishment failure / Reception of an invalid Open
   message). As specified in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, a PCEP peer that does not recognize the
   ASSOC-Type-List TLV will silently ignore it.<a href="#section-4.1.1-1" class="pilcrow">¶</a></p>
<p id="section-4.1.1-2">The Association Type (to be defined in future documents) can specify if
the Association Type advertisement is mandatory for it. 
Thus, the ASSOC-Type-List TLV <span class="bcp14">MUST</span> be included if at least one mandatory
 Association Type needs to be advertised, and the ASSOC-Type-List TLV <span class="bcp14">MAY</span> be
 included otherwise. For an Association Type that specifies that the
 advertisement is mandatory, a missing Assoc-Type in the ASSOC-Type-List TLV
 (or a missing ASSOC-Type-List TLV) is to be interpreted as meaning that the
 Association Type is not supported by the PCEP speaker.<a href="#section-4.1.1-2" class="pilcrow">¶</a></p>
<p id="section-4.1.1-3">The absence of the ASSOC-Type-List TLV in an OPEN object <span class="bcp14">MUST</span> be
   interpreted as an absence of information in the list of supported
   Association Types (rather than an indication that the Association Type is
   not supported). In this case, the PCEP
   speaker could still use the ASSOCIATION object: if the peer does not
   support the association, it will react as per the procedure described
   in <a href="#Rules" class="xref">Section 6.4</a>.<a href="#section-4.1.1-3" class="pilcrow">¶</a></p>
<p id="section-4.1.1-4">If the use of the ASSOC-Type-List TLV is triggered by support for a
   mandatory Association Type, then it is <span class="bcp14">RECOMMENDED</span> that the PCEP
   implementation include all supported Association Types (including optional
   types) to ease the operations of the PCEP peer.<a href="#section-4.1.1-4" class="pilcrow">¶</a></p>
</section>
</section>
</section>
</div>
<div id="Range-tlv">
<section id="section-5">
      <h2 id="name-operator-configured-associat">
<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-operator-configured-associat" class="section-name selfRef">Operator-Configured Association Range TLV</a>
      </h2>
<p id="section-5-1">This section defines a PCEP extension to support
   the advertisement of the Operator-configured Association Range used for an Association Type by the PCEP speaker (as an Association Source).<a href="#section-5-1" class="pilcrow">¶</a></p>
<p id="section-5-2">A new PCEP OP-CONF-ASSOC-RANGE (Operator-configured Association Range)
   TLV is defined.  The PCEP OP-CONF-ASSOC-RANGE TLV is carried within an OPEN
   object.  This way, during the PCEP session-setup phase, a PCEP speaker can
   advertise to a PCEP peer the Operator-configured Association Range for an
   Association Type.<a href="#section-5-2" class="pilcrow">¶</a></p>
<p id="section-5-3">The PCEP OP-CONF-ASSOC-RANGE TLV is <span class="bcp14">OPTIONAL</span>.  It <span class="bcp14">MAY</span> be carried within
   an OPEN object sent by a PCEP speaker in an Open message to a PCEP peer. 
   The OP-CONF-ASSOC-RANGE TLV format is compliant with the PCEP TLV format
   defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>.  That is, the TLV is composed of 2
   bytes for the type, 2 bytes specifying the TLV length, and a Value field.
   The Length field defines the length of the value portion in bytes.<a href="#section-5-3" class="pilcrow">¶</a></p>
<p id="section-5-4">The PCEP OP-CONF-ASSOC-RANGE TLV has the following format:<a href="#section-5-4" class="pilcrow">¶</a></p>
<span id="name-the-op-conf-assoc-range-tlv"></span><div id="OP-CONF-ASSOC-RANGE">
<figure id="figure-2">
        <div class="artwork art-text alignLeft" id="section-5-5.1">
<pre>
   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |         Type                  |            Length             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |             Reserved          |          Assoc-Type #1        |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |      Start-Assoc-ID #1        |           Range #1            |        
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  //                                                             //
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |             Reserved          |          Assoc-Type #N        |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |      Start-Assoc-ID #N        |           Range #N            |        
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ </pre>
</div>
<figcaption><a href="#figure-2" class="selfRef">Figure 2</a>:
<a href="#name-the-op-conf-assoc-range-tlv" class="selfRef">The OP-CONF-ASSOC-RANGE TLV Format</a>
        </figcaption></figure>
</div>
<dl class="dlParallel" id="section-5-6">
        <dt id="section-5-6.1">Type:</dt>
<dd id="section-5-6.2">29<a href="#section-5-6.2" class="pilcrow">¶</a>
</dd>
<dt id="section-5-6.3">Length:</dt>
<dd id="section-5-6.4">N * 8 (where N is the number of Association Types).<a href="#section-5-6.4" class="pilcrow">¶</a>
</dd>
<dt id="section-5-6.5">Value:</dt>
<dd id="section-5-6.6">
          <p id="section-5-6.6.1">Includes the following fields, repeated for each
Association Type:<a href="#section-5-6.6.1" class="pilcrow">¶</a></p>
<dl class="dlParallel" id="section-5-6.6.2">
            <dt id="section-5-6.6.2.1">Reserved (2 bytes):</dt>
<dd id="section-5-6.6.2.2">
              <span class="bcp14">MUST</span> be set to 0 on transmission and <span class="bcp14">MUST</span> be
   ignored on receipt.<a href="#section-5-6.6.2.2" class="pilcrow">¶</a>
</dd>
<dt id="section-5-6.6.2.3">Assoc-Type (2 bytes):</dt>
<dd id="section-5-6.6.2.4">The Association Type (<a href="#iana_assoc_type" class="xref">Section 7.4</a>). The Association Types will be defined in future
   documents.<a href="#section-5-6.6.2.4" class="pilcrow">¶</a>
</dd>
<dt id="section-5-6.6.2.5">Start-Assoc-ID (2 bytes):</dt>
<dd id="section-5-6.6.2.6">The "start association" identifier for the
   Operator-configured Association Range for the particular Association
   Type. The values 0 and 0xffff <span class="bcp14">MUST NOT</span> be used; on receipt of these
   values in the TLV, the session is rejected, and an error message is sent
   (see <a href="#pro" class="xref">Section 5.1</a>).<a href="#section-5-6.6.2.6" class="pilcrow">¶</a>
</dd>
<dt id="section-5-6.6.2.7">Range (2 bytes):</dt>
<dd id="section-5-6.6.2.8">The number of associations marked for the
   Operator-configured Associations. Range <span class="bcp14">MUST</span> be greater than 0, and it
   <span class="bcp14">MUST</span> be such that (Start-Assoc-ID + Range) does not cross the
   largest Association ID value of 0xffff. If this condition is not satisfied, the session
   is rejected, and an error message is sent (see <a href="#pro" class="xref">Section 5.1</a>).<a href="#section-5-6.6.2.8" class="pilcrow">¶</a>
</dd>
</dl>
</dd>
</dl>
<div id="pro">
<section id="section-5.1">
        <h3 id="name-procedure-2">
<a href="#section-5.1" class="section-number selfRef">5.1. </a><a href="#name-procedure-2" class="section-name selfRef">Procedure</a>
        </h3>
<p id="section-5.1-1">A PCEP speaker <span class="bcp14">MAY</span> include an OP-CONF-ASSOC-RANGE TLV within an OPEN object in an Open
   message sent to a PCEP peer in order to advertise the Operator-configured Association Range for an Association Type. 
   The OP-CONF-ASSOC-RANGE TLV <span class="bcp14">MUST NOT</span> appear more than
   once in an OPEN object.  If it appears more than once, the PCEP
   session <span class="bcp14">MUST</span> be rejected with Error-Type 1 and Error-value 1 (PCEP
   session establishment failure / Reception of an invalid Open
   message).<a href="#section-5.1-1" class="pilcrow">¶</a></p>
<p id="section-5.1-2">As specified in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>, a PCEP peer that does not recognize the
   OP-CONF-ASSOC-RANGE TLV will silently ignore it.<a href="#section-5.1-2" class="pilcrow">¶</a></p>
<p id="section-5.1-3">The Operator-configured Association Range <span class="bcp14">SHOULD</span> be included for each
   Association Type that could be both dynamic and operator configured. For
   Association Types that are only dynamic or only operator configured, this
   TLV <span class="bcp14">MAY</span> be skipped, in which case the full range of Association IDs
   is considered dynamic or operator configured, respectively. Each
   Association Type (to be defined in future documents) can specify the default
   value for its Operator-configured Association Range.<a href="#section-5.1-3" class="pilcrow">¶</a></p>
<p id="section-5.1-4">The absence of the OP-CONF-ASSOC-RANGE TLV in an OPEN object <span class="bcp14">MUST</span> be
   interpreted as an absence of an explicit Operator-configured Association Range at the PCEP peer. 
   In this case, the default behavior as per each Association Type applies. If the Association 
   Source is not a PCEP speaker, the default value for the Operator-configured Association Range is used for the Association Source.<a href="#section-5.1-4" class="pilcrow">¶</a></p>
<p id="section-5.1-5">If the Assoc-Type is not recognized or supported by the PCEP speaker, it <span class="bcp14">MUST</span> ignore that respective (Start-Assoc-ID + Range). If the Assoc-Type is recognized/supported but Start-Assoc-ID or Range is set incorrectly, the PCEP
   session <span class="bcp14">MUST</span> be rejected with Error-Type 1 and Error-value 1 (PCEP
   session establishment failure / Reception of an invalid Open
   message). The incorrect range includes the case when the
   (Start-Assoc-ID + Range) crosses the largest Association ID value of
   0xffff.<a href="#section-5.1-5" class="pilcrow">¶</a></p>
<p id="section-5.1-6">A given Assoc-Type <span class="bcp14">MAY</span> appear more than once in the
   OP-CONF-ASSOC-RANGE TLV in the case of a non-contiguous
   Operator-configured Association Range. The PCEP speaker originating this
   TLV <span class="bcp14">MUST NOT</span> send overlapping ranges for an Association Type. If a PCEP
   peer receives overlapping ranges for an Association Type, it <span class="bcp14">MUST</span> consider
   the Open message malformed and <span class="bcp14">MUST</span> reject the PCEP session with
   Error-Type 1 and Error-value 1 (PCEP session establishment failure /
   Reception of an invalid Open message).<a href="#section-5.1-6" class="pilcrow">¶</a></p>
<p id="section-5.1-7">There may be cases where an Operator-configured Association was
   configured with association parameters (such as an Association ID, Association Type, and Association Source) at the local
   PCEP speaker, and the PCEP session is later established with the
   Association Source and a new operator-configured range is learned
   during session establishment. At this time, the local PCEP speaker <span class="bcp14">MUST</span>
   remove any associations that are not in the new operator-configured range
   (by disassociating any LSPs that are part of it (and notifying the
   PCEP peer of this change)). If a PCEP speaker receives an association for an
   Operator-configured Association and the Association ID is not in
   the Operator-configured Association Range for the Association Type and
   Association Source, it <span class="bcp14">MUST</span> generate an error (as described in <a href="#Rules" class="xref">Section 6.4</a>).<a href="#section-5.1-7" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="association">
<section id="section-6">
      <h2 id="name-association-object">
<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-association-object" class="section-name selfRef">ASSOCIATION Object</a>
      </h2>
<div id="Definition">
<section id="section-6.1">
        <h3 id="name-object-definition">
<a href="#section-6.1" class="section-number selfRef">6.1. </a><a href="#name-object-definition" class="section-name selfRef">Object Definition</a>
        </h3>
<p id="section-6.1-1">Association groups and their memberships are defined using a new
     ASSOCIATION object.<a href="#section-6.1-1" class="pilcrow">¶</a></p>
<p id="section-6.1-2">The ASSOCIATION Object-Class value is 40.<a href="#section-6.1-2" class="pilcrow">¶</a></p>
<p id="section-6.1-3">The ASSOCIATION Object-Type value is 1 for IPv4, and its format is
    shown in <a href="#Association-Object-Fmt1" class="xref">Figure 3</a>:<a href="#section-6.1-3" class="pilcrow">¶</a></p>
<span id="name-the-ipv4-association-object"></span><div id="Association-Object-Fmt1">
<figure id="figure-3">
          <div class="artwork art-text alignLeft" id="section-6.1-4.1">
<pre>
   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |         Reserved              |            Flags            |R|
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |      Association Type         |      Association ID           |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |              IPv4 Association Source                          |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  //                   Optional TLVs                             //
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  </pre>
</div>
<figcaption><a href="#figure-3" class="selfRef">Figure 3</a>:
<a href="#name-the-ipv4-association-object" class="selfRef">The IPv4 ASSOCIATION Object Format</a>
          </figcaption></figure>
</div>
<p id="section-6.1-5">The ASSOCIATION Object-Type value is 2 for IPv6, and its format is
    shown in <a href="#Association-Object-Fmt2" class="xref">Figure 4</a>:<a href="#section-6.1-5" class="pilcrow">¶</a></p>
<span id="name-the-ipv6-association-object"></span><div id="Association-Object-Fmt2">
<figure id="figure-4">
          <div class="artwork art-text alignLeft" id="section-6.1-6.1">
<pre>
   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |         Reserved              |            Flags            |R|
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |      Association Type         |      Association ID           |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |                                                               |
  |                    IPv6 Association Source                    |
  |                                                               |
  |                                                               |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  //                   Optional TLVs                             //
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ </pre>
</div>
<figcaption><a href="#figure-4" class="selfRef">Figure 4</a>:
<a href="#name-the-ipv6-association-object" class="selfRef">The IPv6 ASSOCIATION Object Format</a>
          </figcaption></figure>
</div>
<dl class="dlParallel" id="section-6.1-7">
          <dt id="section-6.1-7.1">Reserved (2 bytes):</dt>
<dd id="section-6.1-7.2">
            <span class="bcp14">MUST</span> be set to 0 and ignored upon
    receipt.<a href="#section-6.1-7.2" class="pilcrow">¶</a>
</dd>
<dt id="section-6.1-7.3">Flags (2 bytes):</dt>
<dd id="section-6.1-7.4">
            <p id="section-6.1-7.4.1">The following flag is currently defined:<a href="#section-6.1-7.4.1" class="pilcrow">¶</a></p>
<dl class="dlParallel" id="section-6.1-7.4.2">
              <dt id="section-6.1-7.4.2.1">R (Removal - 1 bit):</dt>
<dd id="section-6.1-7.4.2.2">When set, the requesting
       PCEP peer requires the removal of an LSP from the association group. 
       When unset, the PCEP peer indicates that the LSP is added or retained
       as part of the association group. This flag is used for the ASSOCIATION
       object in the Path Computation Report (PCRpt) and
       Path Computation Update (PCUpd) messages.  It is ignored in other
       PCEP messages.<a href="#section-6.1-7.4.2.2" class="pilcrow">¶</a>
</dd>
</dl>
</dd>
</dl>
<p id="section-6.1-8">The unassigned flags <span class="bcp14">MUST</span> be set to 0 on transmission and <span class="bcp14">MUST</span> be
  ignored on receipt.<a href="#section-6.1-8" class="pilcrow">¶</a></p>
<dl class="dlParallel" id="section-6.1-9">
          <dt id="section-6.1-9.1">Association Type (2 bytes):</dt>
<dd id="section-6.1-9.2">The Association Type
  (<a href="#iana_assoc_type" class="xref">Section 7.4</a>). The Association Types
  will be defined in future documents.<a href="#section-6.1-9.2" class="pilcrow">¶</a>
</dd>
<dt id="section-6.1-9.3">Association ID (2 bytes):</dt>
<dd id="section-6.1-9.4">The identifier of the association
    group.  When combined with other association parameters, such as an
    Association Type and Association Source, this value uniquely identifies an
    association group. The values 0xffff and 0x0 are reserved. The value
    0xffff is used to indicate all association groups and could be used with
    the R flag to indicate removal for all associations for the LSP within the
    scope of the Association Type and Association Source.<a href="#section-6.1-9.4" class="pilcrow">¶</a>
</dd>
<dt id="section-6.1-9.5">Association Source:</dt>
<dd id="section-6.1-9.6">Contains a valid IPv4 address (4 bytes)
    if the ASSOCIATION Object-Type is 1 or a valid IPv6 address (16 bytes) if
    the ASSOCIATION Object-Type is 2. The address provides scoping for the
    Association ID. See <a href="#AssocSrc" class="xref">Section 6.1.3</a> for details.<a href="#section-6.1-9.6" class="pilcrow">¶</a>
</dd>
<dt id="section-6.1-9.7">Optional TLVs:</dt>
<dd id="section-6.1-9.8">The optional TLVs follow the PCEP TLV format
    defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. This document defines two optional
    TLVs. Other documents can define more TLVs in the future.<a href="#section-6.1-9.8" class="pilcrow">¶</a>
</dd>
</dl>
<div id="Global-association-src">
<section id="section-6.1.1">
          <h4 id="name-global-association-source-t">
<a href="#section-6.1.1" class="section-number selfRef">6.1.1. </a><a href="#name-global-association-source-t" class="section-name selfRef">Global Association Source TLV</a>
          </h4>
<p id="section-6.1.1-1"> The Global Association Source TLV is an optional TLV for use in the ASSOCIATION object. 
        The meaning and usage of the Global Association Source TLV are as per
<span><a href="https://www.rfc-editor.org/rfc/rfc6780#section-4" class="relref">Section 4</a> of [<a href="#RFC6780" class="xref">RFC6780</a>]</span>.<a href="#section-6.1.1-1" class="pilcrow">¶</a></p>
<span id="name-the-global-association-sour"></span><div id="Global-Association-Object-Fmt1">
<figure id="figure-5">
            <div class="artwork art-text alignLeft" id="section-6.1.1-2.1">
<pre>
   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |         Type                  |            Length             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |              Global Association Source                        |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ </pre>
</div>
<figcaption><a href="#figure-5" class="selfRef">Figure 5</a>:
<a href="#name-the-global-association-sour" class="selfRef">The Global Association Source TLV Format</a>
            </figcaption></figure>
</div>
<dl class="dlParallel" id="section-6.1.1-3">
            <dt id="section-6.1.1-3.1">Type:</dt>
<dd id="section-6.1.1-3.2">30<a href="#section-6.1.1-3.2" class="pilcrow">¶</a>
</dd>
<dt id="section-6.1.1-3.3">Length:</dt>
<dd id="section-6.1.1-3.4">Fixed value of 4 bytes.<a href="#section-6.1.1-3.4" class="pilcrow">¶</a>
</dd>
<dt id="section-6.1.1-3.5">Global Association Source:</dt>
<dd id="section-6.1.1-3.6">As defined in
<span><a href="https://www.rfc-editor.org/rfc/rfc6780#section-4" class="relref">Section 4</a> of [<a href="#RFC6780" class="xref">RFC6780</a>]</span>.<a href="#section-6.1.1-3.6" class="pilcrow">¶</a>
</dd>
</dl>
</section>
</div>
<div id="EXT-association">
<section id="section-6.1.2">
          <h4 id="name-extended-association-id-tlv">
<a href="#section-6.1.2" class="section-number selfRef">6.1.2. </a><a href="#name-extended-association-id-tlv" class="section-name selfRef">Extended Association ID TLV</a>
          </h4>
<p id="section-6.1.2-1"> The Extended Association ID TLV is an optional TLV for use in
      the ASSOCIATION object. The meaning and usage of the
      Extended Association ID TLV are as per 
<span><a href="https://www.rfc-editor.org/rfc/rfc6780#section-4" class="relref">Section 4</a> of [<a href="#RFC6780" class="xref">RFC6780</a>]</span>.<a href="#section-6.1.2-1" class="pilcrow">¶</a></p>
<span id="name-the-extended-association-id"></span><div id="Ext-id-Object-Fmt1">
<figure id="figure-6">
            <div class="artwork art-text alignLeft" id="section-6.1.2-2.1">
<pre>
   0                   1                   2                   3
   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  |         Type                  |            Length             |
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
  //                Extended Association ID                      //
  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ </pre>
</div>
<figcaption><a href="#figure-6" class="selfRef">Figure 6</a>:
<a href="#name-the-extended-association-id" class="selfRef">The Extended Association ID TLV Format</a>
            </figcaption></figure>
</div>
<dl class="dlParallel" id="section-6.1.2-3">
            <dt id="section-6.1.2-3.1">Type:</dt>
<dd id="section-6.1.2-3.2">31<a href="#section-6.1.2-3.2" class="pilcrow">¶</a>
</dd>
<dt id="section-6.1.2-3.3">Length:</dt>
<dd id="section-6.1.2-3.4">Variable.<a href="#section-6.1.2-3.4" class="pilcrow">¶</a>
</dd>
<dt id="section-6.1.2-3.5">Extended Association ID:</dt>
<dd id="section-6.1.2-3.6">As defined in 
<span><a href="https://www.rfc-editor.org/rfc/rfc6780#section-4" class="relref">Section 4</a> of [<a href="#RFC6780" class="xref">RFC6780</a>]</span>.<a href="#section-6.1.2-3.6" class="pilcrow">¶</a>
</dd>
</dl>
</section>
</div>
<div id="AssocSrc">
<section id="section-6.1.3">
          <h4 id="name-association-source">
<a href="#section-6.1.3" class="section-number selfRef">6.1.3. </a><a href="#name-association-source" class="section-name selfRef">Association Source</a>
          </h4>
<p id="section-6.1.3-1">The Association Source field in the ASSOCIATION object is 
   set to a valid IP address to identify the node that originated the
   association. In the case of dynamic associations, the Association Source is
   usually set as the local PCEP speaker address unless local policy dictates
   otherwise, in which case the Association Source is set based on the local
    policy. In the case of PCE redundancy, local policy could set the source
    as a virtual IP address that identifies all instances of the PCE. In the
    case of Operator-configured Associations, the Association Source is
    manually configured, and it could be set as one of the PCEP speakers, an
    NMS, or any other valid IP address that scopes the Association ID for the Association Type.<a href="#section-6.1.3-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="id">
<section id="section-6.1.4">
          <h4 id="name-unique-identification-for-a">
<a href="#section-6.1.4" class="section-number selfRef">6.1.4. </a><a href="#name-unique-identification-for-a" class="section-name selfRef">Unique Identification for an Association Group</a>
          </h4>
<p id="section-6.1.4-1">The combination of the mandatory fields Association Type, Association
    ID, and Association Source in the ASSOCIATION object uniquely identifies
    the association group. If the optional TLVs (Global Association Source and
    Extended Association ID) are included, then they <span class="bcp14">MUST</span> be included in
    combination with mandatory fields to uniquely identify the association
    group. In this document, all these fields are collectively called
    "association parameters". Note that the ASSOCIATION object <span class="bcp14">MAY</span> include
    other optional TLVs (not defined in this document) based on the 
    Association Types. These TLVs provide "information" related to the
    Association Type. This document refers to this information as
    "association information".<a href="#section-6.1.4-1" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<section id="section-6.2">
        <h3 id="name-relationship-to-the-rsvp-as">
<a href="#section-6.2" class="section-number selfRef">6.2. </a><a href="#name-relationship-to-the-rsvp-as" class="section-name selfRef">Relationship to the RSVP ASSOCIATION Object</a>
        </h3>
<p id="section-6.2-1">The format of the PCEP ASSOCIATION object defined in this document
       is aligned with the RSVP ASSOCIATION object <span>[<a href="#RFC6780" class="xref">RFC6780</a>]</span>. Various Association Types related to RSVP
       association are defined in <span>[<a href="#RFC4872" class="xref">RFC4872</a>]</span>, <span>[<a href="#RFC4873" class="xref">RFC4873</a>]</span>, and <span>[<a href="#RFC7551" class="xref">RFC7551</a>]</span>. The PCEP extensions
       that define new Association Types should clarify how the PCEP
       associations would work with RSVP associations and vice versa.<a href="#section-6.2-1" class="pilcrow">¶</a></p>
</section>
<div id="Object-Encoding">
<section id="section-6.3">
        <h3 id="name-object-encoding-in-pcep-mes">
<a href="#section-6.3" class="section-number selfRef">6.3. </a><a href="#name-object-encoding-in-pcep-mes" class="section-name selfRef">Object Encoding in PCEP Messages</a>
        </h3>
<p id="section-6.3-1">Message formats in this document are expressed using Routing BNF
     (RBNF) as used in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> and defined in <span>[<a href="#RFC5511" class="xref">RFC5511</a>]</span>.<a href="#section-6.3-1" class="pilcrow">¶</a></p>
<section id="section-6.3.1">
          <h4 id="name-stateful-pcep-messages">
<a href="#section-6.3.1" class="section-number selfRef">6.3.1. </a><a href="#name-stateful-pcep-messages" class="section-name selfRef">Stateful PCEP Messages</a>
          </h4>
<p id="section-6.3.1-1">The ASSOCIATION object <span class="bcp14">MAY</span> be carried in the PCUpd, PCRpt, and
    Path Computation Initiate (PCInitiate) messages.<a href="#section-6.3.1-1" class="pilcrow">¶</a></p>
<p id="section-6.3.1-2">When carried in a PCRpt message, this object is used to report the
    association group membership pertaining to an LSP to a stateful PCE. 
    The PCRpt message is used for initial State Synchronization operations
    (<span><a href="https://www.rfc-editor.org/rfc/rfc8231#section-5.6" class="relref">Section 5.6</a> of [<a href="#RFC8231" class="xref">RFC8231</a>]</span>), as well as whenever the
    state of the LSP changes. If the LSP belongs to an association group, then
    the associations <span class="bcp14">MUST</span> be included during the State Synchronization
    operations.<a href="#section-6.3.1-2" class="pilcrow">¶</a></p>
<p id="section-6.3.1-3">The PCRpt message can also be used to remove an LSP from one or more
    association groups by setting the R flag to 1 in the ASSOCIATION
    object.<a href="#section-6.3.1-3" class="pilcrow">¶</a></p>
<p id="section-6.3.1-4">When an LSP is first reported to the PCE, the PCRpt message <span class="bcp14">MUST</span>
    include all the association groups that it belongs to. Any subsequent
    PCRpt message <span class="bcp14">SHOULD</span> include only the associations that are being
    modified or removed.<a href="#section-6.3.1-4" class="pilcrow">¶</a></p>
<p id="section-6.3.1-5"> The PCRpt message is defined in <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>
    and updated as shown below:<a href="#section-6.3.1-5" class="pilcrow">¶</a></p>
<div id="section-6.3.1-6">
<pre class="sourcecode lang-rbnf">
   &lt;PCRpt Message&gt; ::= &lt;Common Header&gt;
                       &lt;state-report-list&gt;
</pre><a href="#section-6.3.1-6" class="pilcrow">¶</a>
</div>
<p id="section-6.3.1-7">Where:<a href="#section-6.3.1-7" class="pilcrow">¶</a></p>
<div id="section-6.3.1-8">
<pre class="sourcecode lang-rbnf">
      &lt;state-report-list&gt; ::= &lt;state-report&gt;[&lt;state-report-list&gt;]

      &lt;state-report&gt; ::= [&lt;SRP&gt;]
                         &lt;LSP&gt;
                         [&lt;association-list&gt;]
                         &lt;path&gt;
</pre><a href="#section-6.3.1-8" class="pilcrow">¶</a>
</div>
<p id="section-6.3.1-9">Where:<a href="#section-6.3.1-9" class="pilcrow">¶</a></p>
<div id="section-6.3.1-10">
<pre class="sourcecode lang-rbnf">
      &lt;path&gt;::= &lt;intended-path&gt;
                [&lt;actual-attribute-list&gt;&lt;actual-path&gt;]
                &lt;intended-attribute-list&gt;

      &lt;association-list&gt; ::= &lt;ASSOCIATION&gt; [&lt;association-list&gt;]
</pre><a href="#section-6.3.1-10" class="pilcrow">¶</a>
</div>
<p id="section-6.3.1-11"> When an LSP is delegated to a stateful PCE, the stateful PCE can create
    a new association group for this LSP or associate it with one or more existing
    association groups. This is done by including the  ASSOCIATION object in a
    PCUpd message.  A stateful PCE can also remove a delegated
    LSP from one or more association groups by setting the R flag to 1 in the ASSOCIATION object.<a href="#section-6.3.1-11" class="pilcrow">¶</a></p>
<p id="section-6.3.1-12">The PCUpd message <span class="bcp14">SHOULD</span> include the association groups that are being modified or removed. There is no need to include associations that remain unchanged.<a href="#section-6.3.1-12" class="pilcrow">¶</a></p>
<p id="section-6.3.1-13">The PCUpd message is defined in <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>
    and updated as shown below:<a href="#section-6.3.1-13" class="pilcrow">¶</a></p>
<div id="section-6.3.1-14">
<pre class="sourcecode lang-rbnf">
 &lt;PCUpd Message&gt; ::= &lt;Common Header&gt;
                     &lt;update-request-list&gt;
</pre><a href="#section-6.3.1-14" class="pilcrow">¶</a>
</div>
<p id="section-6.3.1-15">Where:<a href="#section-6.3.1-15" class="pilcrow">¶</a></p>
<div id="section-6.3.1-16">
<pre class="sourcecode lang-rbnf">
    &lt;update-request-list&gt; ::= &lt;update-request&gt;[&lt;update-request-list&gt;]

    &lt;update-request&gt; ::= &lt;SRP&gt;
                         &lt;LSP&gt;
                         [&lt;association-list&gt;]
                         &lt;path&gt;
</pre><a href="#section-6.3.1-16" class="pilcrow">¶</a>
</div>
<p id="section-6.3.1-17">Where:<a href="#section-6.3.1-17" class="pilcrow">¶</a></p>
<div id="section-6.3.1-18">
<pre class="sourcecode lang-rbnf">
    &lt;path&gt;::= &lt;intended-path&gt;&lt;intended-attribute-list&gt;

    &lt;association-list&gt; ::= &lt;ASSOCIATION&gt; [&lt;association-list&gt;]
</pre><a href="#section-6.3.1-18" class="pilcrow">¶</a>
</div>
<p id="section-6.3.1-19">Unless a PCEP speaker wants to delete an association
    from an LSP or make changes to the association, it does not need to
    include the ASSOCIATION object in future stateful messages.<a href="#section-6.3.1-19" class="pilcrow">¶</a></p>
<p id="section-6.3.1-20">A PCE initiating a new LSP can also include the association groups that this LSP belongs to. This is done by including the ASSOCIATION object in a
    PCInitiate message. The PCInitiate message <span class="bcp14">MUST</span> include all the association groups that it belongs to.
    The PCInitiate message is defined in <span>[<a href="#RFC8281" class="xref">RFC8281</a>]</span>
    and updated as shown below:<a href="#section-6.3.1-20" class="pilcrow">¶</a></p>
<div id="section-6.3.1-21">
<pre class="sourcecode lang-rbnf">
&lt;PCInitiate Message&gt; ::= &lt;Common Header&gt;
                         &lt;PCE-initiated-lsp-list&gt;
</pre><a href="#section-6.3.1-21" class="pilcrow">¶</a>
</div>
<p id="section-6.3.1-22">Where:<a href="#section-6.3.1-22" class="pilcrow">¶</a></p>
<div id="section-6.3.1-23">
<pre class="sourcecode lang-rbnf">
&lt;PCE-initiated-lsp-list&gt; ::= &lt;PCE-initiated-lsp-request&gt;
                             [&lt;PCE-initiated-lsp-list&gt;]

&lt;PCE-initiated-lsp-request&gt; ::= (&lt;PCE-initiated-lsp-instantiation&gt;|
                                &lt;PCE-initiated-lsp-deletion&gt;)

&lt;PCE-initiated-lsp-instantiation&gt; ::= &lt;SRP&gt;
                                      &lt;LSP&gt;
                                      [&lt;END-POINTS&gt;]
                                      &lt;ERO&gt;
                                      [&lt;association-list&gt;]
                                      [&lt;attribute-list&gt;]
</pre><a href="#section-6.3.1-23" class="pilcrow">¶</a>
</div>
<p id="section-6.3.1-24">Where:<a href="#section-6.3.1-24" class="pilcrow">¶</a></p>
<div id="section-6.3.1-25">
<pre class="sourcecode lang-rbnf">
&lt;association-list&gt; ::= &lt;ASSOCIATION&gt; [&lt;association-list&gt;]
</pre><a href="#section-6.3.1-25" class="pilcrow">¶</a>
</div>
</section>
<section id="section-6.3.2">
          <h4 id="name-request-message">
<a href="#section-6.3.2" class="section-number selfRef">6.3.2. </a><a href="#name-request-message" class="section-name selfRef">Request Message</a>
          </h4>
<p id="section-6.3.2-1">
    In the case of a passive (stateful or stateless) PCE, the ASSOCIATION
    object is <span class="bcp14">OPTIONAL</span> and <span class="bcp14">MAY</span> be carried in the PCReq message.<a href="#section-6.3.2-1" class="pilcrow">¶</a></p>
<p id="section-6.3.2-2">
    When carried in a PCReq message, the ASSOCIATION object is used to
    associate the path computation request to an association group. The
    association (and the other LSPs) should be known to the PCE
    beforehand. These could be operator configured or dynamically learned
    beforehand via stateful PCEP messages. The R flag in the ASSOCIATION
    object within a PCReq message <span class="bcp14">MUST</span> be set to 0 while sending and ignored
    on receipt.<a href="#section-6.3.2-2" class="pilcrow">¶</a></p>
<p id="section-6.3.2-3">
   The PCReq message is defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> and updated in
   <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>. It is further updated below for
   association groups:<a href="#section-6.3.2-3" class="pilcrow">¶</a></p>
<div id="section-6.3.2-4">
<pre class="sourcecode lang-rbnf">
&lt;PCReq Message&gt;::= &lt;Common Header&gt;
                   [&lt;svec-list&gt;]
                   &lt;request-list&gt;
</pre><a href="#section-6.3.2-4" class="pilcrow">¶</a>
</div>
<p id="section-6.3.2-5">Where:<a href="#section-6.3.2-5" class="pilcrow">¶</a></p>
<div id="section-6.3.2-6">
<pre class="sourcecode lang-rbnf">
   &lt;svec-list&gt;::= &lt;SVEC&gt;[&lt;svec-list&gt;]
   &lt;request-list&gt;::= &lt;request&gt;[&lt;request-list&gt;]

   &lt;request&gt;::= &lt;RP&gt;
                &lt;END-POINTS&gt;
                [&lt;LSP&gt;]
                [&lt;LSPA&gt;]
                [&lt;BANDWIDTH&gt;]
                [&lt;metric-list&gt;]
                [&lt;association-list&gt;]
                [&lt;RRO&gt;[&lt;BANDWIDTH&gt;]]
                [&lt;IRO&gt;]
                [&lt;LOAD-BALANCING&gt;]
</pre><a href="#section-6.3.2-6" class="pilcrow">¶</a>
</div>
<p id="section-6.3.2-7">Where:<a href="#section-6.3.2-7" class="pilcrow">¶</a></p>
<div id="section-6.3.2-8">
<pre class="sourcecode lang-rbnf">
   &lt;association-list&gt; ::= &lt;ASSOCIATION&gt; [&lt;association-list&gt;]
</pre><a href="#section-6.3.2-8" class="pilcrow">¶</a>
</div>
<p id="section-6.3.2-9">
   Note that the LSP object <span class="bcp14">MAY</span> be present for the passive stateful
   PCE mode.<a href="#section-6.3.2-9" class="pilcrow">¶</a></p>
</section>
<section id="section-6.3.3">
          <h4 id="name-reply-message">
<a href="#section-6.3.3" class="section-number selfRef">6.3.3. </a><a href="#name-reply-message" class="section-name selfRef">Reply Message</a>
          </h4>
<p id="section-6.3.3-1">
    In the case of a passive (stateful or stateless) PCE, the ASSOCIATION
    object is <span class="bcp14">OPTIONAL</span> and <span class="bcp14">MAY</span> be carried in the PCRep message with the
    NO-PATH object. The ASSOCIATION object in the PCRep message indicates the
    association group that caused the PCE to fail to find a path.<a href="#section-6.3.3-1" class="pilcrow">¶</a></p>
<p id="section-6.3.3-2">
   The PCRep message is defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> and updated in
   <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>. It is further updated below for association groups:<a href="#section-6.3.3-2" class="pilcrow">¶</a></p>
<div id="section-6.3.3-3">
<pre class="sourcecode lang-rbnf">
&lt;PCRep Message&gt; ::= &lt;Common Header&gt;
                    &lt;response-list&gt;
</pre><a href="#section-6.3.3-3" class="pilcrow">¶</a>
</div>
<p id="section-6.3.3-4">Where:<a href="#section-6.3.3-4" class="pilcrow">¶</a></p>
<div id="section-6.3.3-5">
<pre class="sourcecode lang-rbnf">
   &lt;response-list&gt;::=&lt;response&gt;[&lt;response-list&gt;]

   &lt;response&gt;::=&lt;RP&gt;
                [&lt;LSP&gt;]
                [&lt;NO-PATH&gt;]
                [&lt;association-list&gt;]
                [&lt;attribute-list&gt;]
                [&lt;path-list&gt;]
</pre><a href="#section-6.3.3-5" class="pilcrow">¶</a>
</div>
<p id="section-6.3.3-6">Where:<a href="#section-6.3.3-6" class="pilcrow">¶</a></p>
<div id="section-6.3.3-7">
<pre class="sourcecode lang-rbnf">
   &lt;association-list&gt; ::= &lt;ASSOCIATION&gt; [&lt;association-list&gt;]
</pre><a href="#section-6.3.3-7" class="pilcrow">¶</a>
</div>
<p id="section-6.3.3-8">
   Note that the LSP object <span class="bcp14">MAY</span> be present for the passive stateful
   PCE mode.<a href="#section-6.3.3-8" class="pilcrow">¶</a></p>
</section>
</section>
</div>
<div id="Rules">
<section id="section-6.4">
        <h3 id="name-processing-rules">
<a href="#section-6.4" class="section-number selfRef">6.4. </a><a href="#name-processing-rules" class="section-name selfRef">Processing Rules</a>
        </h3>
<p id="section-6.4-1">
    Association groups can be operator configured on the necessary PCEP
    speakers, and the PCEP speakers can join the existing association groups. 
    In addition, a PCC or a PCE can create association groups dynamically, and
    the PCEP speaker can also report the associations to its peer via PCEP
    messages. The Operator-configured Associations are created via
    configurations (where all association parameters are manually set) and
    exist until explicitly removed via configurations. The PCEP speaker can
    add LSPs to these configured associations and provide this information
    via stateful PCEP messages. The dynamic associations are created
    dynamically by the PCEP speaker (where all association parameters are
    populated dynamically). The association group is attached to the LSP
    state, and the association group exists until there is at least one LSP as
    part of the association. As described in <a href="#id" class="xref">Section 6.1.4</a>, the
    association parameters are the combination of Association Type,
    Association ID, and Association Source, as well as the optional Global
    Association Source and Extended Association ID TLVs; this combination
    uniquely identifies an association group. The information
    related to the Association Types encoded via the TLVs of a particular
    Association Type (not described in this document) is the association
    information (<a href="#id" class="xref">Section 6.1.4</a>).<a href="#section-6.4-1" class="pilcrow">¶</a></p>
<p id="section-6.4-2">If a PCEP speaker does not recognize the ASSOCIATION object in the
    stateful message, it will return a PCErr message with Error-Type  "Unknown
    Object" as described in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. In the case of a PCReq
    message, the PCE would react based on the P flag as per <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. If a PCEP speaker understands the ASSOCIATION object
    but does not support the Association Type, it <span class="bcp14">MUST</span> return a PCErr message
    with Error-Type 26 "Association Error" and
    Error-value 1 "Association Type is not supported". If any association
    parameters are invalid in the ASSOCIATION object, the PCEP speaker would
    consider this object malformed and process it as a malformed message <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. On receiving a PCEP message with an ASSOCIATION
    object, if a PCEP speaker finds that too many LSPs belong to the
    association group, it <span class="bcp14">MUST</span> return a PCErr message with Error-Type 26
     "Association Error" and Error-value 2 "Too
    many LSPs in the association group". If a PCEP speaker cannot handle a new
    association, it <span class="bcp14">MUST</span> return a PCErr message with Error-Type 26
     "Association Error" and Error-value 3 "Too many
    association groups". These numbers <span class="bcp14">MAY</span> be set by the operator or chosen
    based on a local policy.<a href="#section-6.4-2" class="pilcrow">¶</a></p>
<p id="section-6.4-3">If a PCE peer is unwilling or unable to process the ASSOCIATION object
    in the stateful message, it <span class="bcp14">MUST</span> return a PCErr message with the
    Error-Type "Not supported object" and follow the relevant procedures
    described in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. In the case of a PCReq message, the
    PCE would react based on the P flag as per <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>. On
    receiving a PCEP message with an ASSOCIATION object, if a PCEP speaker
    could not add the LSP to the association group for any reason, it <span class="bcp14">MUST</span>
    return a PCErr message with Error-Type 26 
    "Association Error" and Error-value 7 "Cannot join the association
    group".<a href="#section-6.4-3" class="pilcrow">¶</a></p>
<p id="section-6.4-4">If a PCEP speaker receives an ASSOCIATION object for an Operator-configured Association 
      and the Association ID is not in the Operator-configured Association Range
      for the Association Type and Association Source, it <span class="bcp14">MUST</span> return a PCErr message with Error-Type 26 
      "Association Error" and Error-value 8 "Association ID not in range".<a href="#section-6.4-4" class="pilcrow">¶</a></p>
<p id="section-6.4-5">If a PCEP speaker receives an ASSOCIATION object in a PCReq message
      and the association is not known (the association is not configured, 
      was not created dynamically, or was not learned from a PCEP peer), it <span class="bcp14">MUST</span> return a
      PCErr message with Error-Type 26 "Association
      Error" and Error-value 4 "Association unknown".<a href="#section-6.4-5" class="pilcrow">¶</a></p>
<p id="section-6.4-6">If the association information (related to the association group as a
    whole) received from the peer does not match the local operator-configured
    information, it <span class="bcp14">MUST</span> return a PCErr message with Error-Type 26 "Association Error" and Error-value 5
    "Operator-configured association information mismatch". On receiving
    association information (related to the association group as a whole) that
    does not match the association information previously received about the
    same association from a peer, it <span class="bcp14">MUST</span> return a PCErr message with
    Error-Type 26 "Association Error" and
    Error-value 6 "Association information mismatch". Note that information
    related to each LSP within the association as part of the association
    information TLVs could be different.<a href="#section-6.4-6" class="pilcrow">¶</a></p>
<p id="section-6.4-7">If a PCEP speaker receives an ASSOCIATION object with the R bit set for
    removal and the association group (identified by association parameters)
    is not known, it <span class="bcp14">MUST</span> return a PCErr message with Error-Type 26
     "Association Error" and Error-value 4
    "Association unknown".<a href="#section-6.4-7" class="pilcrow">¶</a></p>
<p id="section-6.4-8">The dynamic associations are cleared along with the LSP state
    information as per <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>. When a PCEP session is
    terminated, after expiry of the State Timeout Interval at the PCC, the LSP
    state associated with that PCEP session is reverted to operator-defined
    default parameters or behaviors. The same procedure is also followed for
    the association groups. On session termination at the PCE, when the LSP
    state reported by the PCC is cleared, the association groups are also
    cleared. When there are no LSPs in an association group, the association
    is considered empty and thus deleted.<a href="#section-6.4-8" class="pilcrow">¶</a></p>
<p id="section-6.4-9">If the LSP is delegated to another PCE on session failure,
    the associations (and association information) set by the PCE remain
    intact, unless updated by the new PCE that takes over.<a href="#section-6.4-9" class="pilcrow">¶</a></p>
<p id="section-6.4-10">Upon LSP delegation revocation, the PCC <span class="bcp14">MAY</span> clear the association
    created by the PCE, but in order to avoid traffic loss, it <span class="bcp14">SHOULD</span>
    perform this action in a make-before-break fashion (same as <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>).<a href="#section-6.4-10" class="pilcrow">¶</a></p>
</section>
</div>
</section>
</div>
<div id="IANA-considerations">
<section id="section-7">
      <h2 id="name-iana-considerations">
<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-iana-considerations" class="section-name selfRef">IANA Considerations</a>
      </h2>
<p id="section-7-1">IANA maintains the "Path Computation Element Protocol (PCEP) Numbers"
    registry at <span>&lt;<a href="https://www.iana.org/assignments/pcep">https://www.iana.org/assignments/pcep</a>&gt;</span>.<a href="#section-7-1" class="pilcrow">¶</a></p>
<section id="section-7.1">
        <h3 id="name-pcep-object">
<a href="#section-7.1" class="section-number selfRef">7.1. </a><a href="#name-pcep-object" class="section-name selfRef">PCEP Object</a>
        </h3>
<p id="section-7.1-1">The "Path Computation Element Protocol (PCEP) Numbers" registry
        contains a subregistry called "PCEP Objects". IANA has allocated the
        following code point in the "PCEP Objects" registry.<a href="#section-7.1-1" class="pilcrow">¶</a></p>
<span id="name-pcep-object-2"></span><div id="tab-1">
<table class="center" id="table-1">
          <caption>
<a href="#table-1" class="selfRef">Table 1</a>:
<a href="#name-pcep-object-2" class="selfRef">PCEP Object</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Object-Class Value</th>
              <th class="text-left" rowspan="1" colspan="1">Name</th>
              <th class="text-left" rowspan="1" colspan="1">Object-Type</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="3" colspan="1">40</td>
              <td class="text-left" rowspan="3" colspan="1">ASSOCIATION</td>
              <td class="text-left" rowspan="1" colspan="1">0: Reserved</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">1: IPv4</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">2: IPv6</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
          </tbody>
        </table>
</div>
</section>
<section id="section-7.2">
        <h3 id="name-pcep-tlv">
<a href="#section-7.2" class="section-number selfRef">7.2. </a><a href="#name-pcep-tlv" class="section-name selfRef">PCEP TLV</a>
        </h3>
<p id="section-7.2-1">IANA has allocated the following
   code points in the "PCEP TLV Type Indicators" registry.<a href="#section-7.2-1" class="pilcrow">¶</a></p>
<span id="name-pcep-tlv-type-indicators"></span><div id="tab-2">
<table class="center" id="table-2">
          <caption>
<a href="#table-2" class="selfRef">Table 2</a>:
<a href="#name-pcep-tlv-type-indicators" class="selfRef">PCEP TLV Type Indicators</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Value</th>
              <th class="text-left" rowspan="1" colspan="1">Meaning</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">29</td>
              <td class="text-left" rowspan="1" colspan="1">Operator-configured Association Range</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">30</td>
              <td class="text-left" rowspan="1" colspan="1">Global Association Source</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">31</td>
              <td class="text-left" rowspan="1" colspan="1">Extended Association ID</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
          </tbody>
        </table>
</div>
<p id="section-7.2-3">IANA has corrected the capitalization in the meaning for value 31 in the above registry
   to "Extended Association ID"; it was previously listed as "Extended
   Association Id".<a href="#section-7.2-3" class="pilcrow">¶</a></p>
<p id="section-7.2-4">IANA has made a new assignment in
   the existing "PCEP TLV Type Indicators" registry as follows:<a href="#section-7.2-4" class="pilcrow">¶</a></p>
<span id="name-assoc-type-list-pcep-tlv-ty"></span><div id="tab-3">
<table class="center" id="table-3">
          <caption>
<a href="#table-3" class="selfRef">Table 3</a>:
<a href="#name-assoc-type-list-pcep-tlv-ty" class="selfRef">ASSOC-Type-List PCEP TLV Type Indicator</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Value</th>
              <th class="text-left" rowspan="1" colspan="1">Meaning</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">35</td>
              <td class="text-left" rowspan="1" colspan="1">ASSOC-Type-List</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
          </tbody>
        </table>
</div>
</section>
<section id="section-7.3">
        <h3 id="name-association-flags">
<a href="#section-7.3" class="section-number selfRef">7.3. </a><a href="#name-association-flags" class="section-name selfRef">Association Flags</a>
        </h3>
<p id="section-7.3-1">Per this document, IANA has created a subregistry of the
    "Path Computation Element Protocol (PCEP) Numbers" registry
    for the bits carried in the Flags field of the ASSOCIATION object.
    The subregistry is called "ASSOCIATION Flag Field". New values are
    assigned by Standards Action <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>.  Each bit is
    tracked with the following qualities:<a href="#section-7.3-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-7.3-2.1">Bit number (counting from bit 0 as the most significant bit)<a href="#section-7.3-2.1" class="pilcrow">¶</a>
</li>
<li id="section-7.3-2.2">Capability description<a href="#section-7.3-2.2" class="pilcrow">¶</a>
</li>
<li id="section-7.3-2.3">Defining RFC<a href="#section-7.3-2.3" class="pilcrow">¶</a>
</li>
</ul>
<span id="name-new-association-flag-field"></span><div id="tab-4">
<table class="center" id="table-4">
          <caption>
<a href="#table-4" class="selfRef">Table 4</a>:
<a href="#name-new-association-flag-field" class="selfRef">New ASSOCIATION Flag Field</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Bit</th>
              <th class="text-left" rowspan="1" colspan="1">Description</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">15</td>
              <td class="text-left" rowspan="1" colspan="1">R (Removal)</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
          </tbody>
        </table>
</div>
</section>
<div id="iana_assoc_type">
<section id="section-7.4">
        <h3 id="name-association-type">
<a href="#section-7.4" class="section-number selfRef">7.4. </a><a href="#name-association-type" class="section-name selfRef">Association Type</a>
        </h3>
<p id="section-7.4-1">Per this document, IANA has created a subregistry of the
        "Path Computation Element Protocol (PCEP) Numbers" registry for
        the Association Type field of the ASSOCIATION object.
        The subregistry is called "ASSOCIATION Type Field". New values are
        assigned by Standards Action <span>[<a href="#RFC8126" class="xref">RFC8126</a>]</span>.  Each
        value is tracked with the following qualities:<a href="#section-7.4-1" class="pilcrow">¶</a></p>
<ul>
<li id="section-7.4-2.1">Type<a href="#section-7.4-2.1" class="pilcrow">¶</a>
</li>
<li id="section-7.4-2.2">Name<a href="#section-7.4-2.2" class="pilcrow">¶</a>
</li>
<li id="section-7.4-2.3">Reference<a href="#section-7.4-2.3" class="pilcrow">¶</a>
</li>
</ul>
<span id="name-new-association-type-field"></span><div id="tab-5">
<table class="center" id="table-5">
          <caption>
<a href="#table-5" class="selfRef">Table 5</a>:
<a href="#name-new-association-type-field" class="selfRef">New ASSOCIATION Type Field</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Type</th>
              <th class="text-left" rowspan="1" colspan="1">Name</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">0</td>
              <td class="text-left" rowspan="1" colspan="1">Reserved</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
          </tbody>
        </table>
</div>
<p id="section-7.4-4">
 Values 2-65535 are Unassigned. Future
          documents should request the assignment of Association Types from
          this subregistry.<a href="#section-7.4-4" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-7.5">
        <h3 id="name-pcep-error-object">
<a href="#section-7.5" class="section-number selfRef">7.5. </a><a href="#name-pcep-error-object" class="section-name selfRef">PCEP-Error Object</a>
        </h3>
<p id="section-7.5-1">IANA has allocated the following
        code points within the "PCEP-ERROR Object Error Types and Values"
        subregistry of the "Path Computation Element Protocol (PCEP) Numbers"
        registry as follows:<a href="#section-7.5-1" class="pilcrow">¶</a></p>
<span id="name-pcep-error-types-and-names"></span><div id="tab-6">
<table class="center" id="table-6">
          <caption>
<a href="#table-6" class="selfRef">Table 6</a>:
<a href="#name-pcep-error-types-and-names" class="selfRef">PCEP-ERROR Types and Names</a>
          </caption>
<thead>
            <tr>
              <th class="text-left" rowspan="1" colspan="1">Error-Type</th>
              <th class="text-left" rowspan="1" colspan="1">Meaning</th>
              <th class="text-left" rowspan="1" colspan="1">Error-value</th>
              <th class="text-left" rowspan="1" colspan="1">Reference</th>
            </tr>
          </thead>
          <tbody>
            <tr>
              <td class="text-left" rowspan="9" colspan="1">26</td>
              <td class="text-left" rowspan="9" colspan="1">Association Error</td>
              <td class="text-left" rowspan="1" colspan="1">0: Unassigned</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">1: Association Type is not supported</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">2: Too many LSPs in the association group</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">3: Too many association groups</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">4: Association unknown</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">5: Operator-configured association information mismatch</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">6: Association information mismatch</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">7: Cannot join the association group</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
            <tr>
              <td class="text-left" rowspan="1" colspan="1">8: Association ID not in range</td>
              <td class="text-left" rowspan="1" colspan="1">RFC 8697</td>
            </tr>
          </tbody>
        </table>
</div>
</section>
</section>
</div>
<div id="Security">
<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">The security considerations described in <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span> and <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> apply to the
   extensions described in this document as well.  Additional considerations
   related to a malicious PCEP speaker are introduced, as associations could
   be spoofed and could be used as an
   attack vector. An attacker could attempt to create too many associations in
   an attempt to load the PCEP peer. The PCEP peer responds with a PCErr
   message as described in <a href="#Rules" class="xref">Section 6.4</a>. An attacker could impact
   LSP operations by creating bogus associations. Further, association groups
   could provide an adversary with the opportunity to eavesdrop on the
   relationship between the LSPs. Thus, securing the PCEP session using
   Transport Layer Security (TLS) <span>[<a href="#RFC8253" class="xref">RFC8253</a>]</span>, as per the
   recommendations and best current practices in <span>[<a href="#RFC7525" class="xref">RFC7525</a>]</span>, is
   <span class="bcp14">RECOMMENDED</span>.<a href="#section-8-1" class="pilcrow">¶</a></p>
<p id="section-8-2">Much of the information carried in the ASSOCIATION object as per this
  document is not extra sensitive. It often reflects information that can
  also be derived from the LSP database, but the association provides a much
  easier grouping of related LSPs and messages. Implementations and operators
  can, and should, use indirect values in the ASSOCIATION object as a way to
  hide any sensitive business relationships.<a href="#section-8-2" class="pilcrow">¶</a></p>
</section>
</div>
<section id="section-9">
      <h2 id="name-manageability-consideration">
<a href="#section-9" class="section-number selfRef">9. </a><a href="#name-manageability-consideration" class="section-name selfRef">Manageability Considerations</a>
      </h2>
<p id="section-9-1">
  All manageability requirements and considerations listed in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> and <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span> apply to PCEP protocol
  extensions defined in this document. In addition, requirements and
  considerations listed in this section apply.<a href="#section-9-1" class="pilcrow">¶</a></p>
<section id="section-9.1">
        <h3 id="name-control-of-function-and-pol">
<a href="#section-9.1" class="section-number selfRef">9.1. </a><a href="#name-control-of-function-and-pol" class="section-name selfRef">Control of Function and Policy</a>
        </h3>
<p id="section-9.1-1">
  A PCE or PCC implementation <span class="bcp14">MUST</span> allow Operator-configured Associations and
  <span class="bcp14">SHOULD</span> allow the setting of the Operator-configured Association Range (<a href="#Range" class="xref">Section 3.4</a>) as described in this document.<a href="#section-9.1-1" class="pilcrow">¶</a></p>
</section>
<section id="section-9.2">
        <h3 id="name-information-and-data-models">
<a href="#section-9.2" class="section-number selfRef">9.2. </a><a href="#name-information-and-data-models" class="section-name selfRef">Information and Data Models</a>
        </h3>
<p id="section-9.2-1">The PCEP YANG module is defined in <span>[<a href="#PCEP-YANG" class="xref">PCEP-YANG</a>]</span>. In the
   future, this YANG module should be extended or augmented to provide
   the following additional information related to association groups.<a href="#section-9.2-1" class="pilcrow">¶</a></p>
<p id="section-9.2-2">An implementation <span class="bcp14">SHOULD</span> allow the operator to view the associations
  configured or created dynamically. Future implementations <span class="bcp14">SHOULD</span> allow
  the viewing of associations reported by each peer and the current set of
  LSPs in the association.<a href="#section-9.2-2" class="pilcrow">¶</a></p>
<p id="section-9.2-3">It might also be useful to find out how many associations for each
  Association Type currently exist and to know how many free Association IDs are available for a particular Association Type and source.<a href="#section-9.2-3" class="pilcrow">¶</a></p>
</section>
<section id="section-9.3">
        <h3 id="name-liveness-detection-and-moni">
<a href="#section-9.3" class="section-number selfRef">9.3. </a><a href="#name-liveness-detection-and-moni" class="section-name selfRef">Liveness Detection and Monitoring</a>
        </h3>
<p id="section-9.3-1">
  Mechanisms defined in this document do not imply any new liveness detection and monitoring requirements in addition to those already listed in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span>.<a href="#section-9.3-1" class="pilcrow">¶</a></p>
</section>
<section id="section-9.4">
        <h3 id="name-verifying-correct-operation">
<a href="#section-9.4" class="section-number selfRef">9.4. </a><a href="#name-verifying-correct-operation" class="section-name selfRef">Verifying Correct Operation</a>
        </h3>
<p id="section-9.4-1">
  Mechanisms defined in this document do not imply any new operation verification requirements in addition to those already listed in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> 
  and <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span>.<a href="#section-9.4-1" class="pilcrow">¶</a></p>
</section>
<section id="section-9.5">
        <h3 id="name-requirements-on-other-proto">
<a href="#section-9.5" class="section-number selfRef">9.5. </a><a href="#name-requirements-on-other-proto" class="section-name selfRef">Requirements on Other Protocols</a>
        </h3>
<p id="section-9.5-1">Mechanisms defined in this document do not imply any new requirements on other protocols.<a href="#section-9.5-1" class="pilcrow">¶</a></p>
</section>
<section id="section-9.6">
        <h3 id="name-impact-on-network-operation">
<a href="#section-9.6" class="section-number selfRef">9.6. </a><a href="#name-impact-on-network-operation" class="section-name selfRef">Impact on Network Operations</a>
        </h3>
<p id="section-9.6-1">
  Mechanisms defined in <span>[<a href="#RFC5440" class="xref">RFC5440</a>]</span> 
  and 
  <span>[<a href="#RFC8231" class="xref">RFC8231</a>]</span> also apply to PCEP extensions defined in this document.<a href="#section-9.6-1" class="pilcrow">¶</a></p>
</section>
</section>
<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="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">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>
<dt id="RFC5440">[RFC5440]</dt>
<dd>
<span class="refAuthor">Vasseur, JP., Ed.</span><span class="refAuthor"> and JL. Le Roux, Ed.</span>, <span class="refTitle">"Path Computation Element (PCE) Communication Protocol (PCEP)"</span>, <span class="seriesInfo">RFC 5440</span>, <span class="seriesInfo">DOI 10.17487/RFC5440</span>, <time datetime="2009-03">March 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5440">https://www.rfc-editor.org/info/rfc5440</a>&gt;</span>. </dd>
<dt id="RFC5511">[RFC5511]</dt>
<dd>
<span class="refAuthor">Farrel, A.</span>, <span class="refTitle">"Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications"</span>, <span class="seriesInfo">RFC 5511</span>, <span class="seriesInfo">DOI 10.17487/RFC5511</span>, <time datetime="2009-04">April 2009</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc5511">https://www.rfc-editor.org/info/rfc5511</a>&gt;</span>. </dd>
<dt id="RFC6780">[RFC6780]</dt>
<dd>
<span class="refAuthor">Berger, L.</span><span class="refAuthor">, Le Faucheur, F.</span><span class="refAuthor">, and A. Narayanan</span>, <span class="refTitle">"RSVP ASSOCIATION Object Extensions"</span>, <span class="seriesInfo">RFC 6780</span>, <span class="seriesInfo">DOI 10.17487/RFC6780</span>, <time datetime="2012-10">October 2012</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6780">https://www.rfc-editor.org/info/rfc6780</a>&gt;</span>. </dd>
<dt id="RFC7525">[RFC7525]</dt>
<dd>
<span class="refAuthor">Sheffer, Y.</span><span class="refAuthor">, Holz, R.</span><span class="refAuthor">, and P. Saint-Andre</span>, <span class="refTitle">"Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)"</span>, <span class="seriesInfo">BCP 195</span>, <span class="seriesInfo">RFC 7525</span>, <span class="seriesInfo">DOI 10.17487/RFC7525</span>, <time datetime="2015-05">May 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7525">https://www.rfc-editor.org/info/rfc7525</a>&gt;</span>. </dd>
<dt id="RFC8051">[RFC8051]</dt>
<dd>
<span class="refAuthor">Zhang, X., Ed.</span><span class="refAuthor"> and I. Minei, Ed.</span>, <span class="refTitle">"Applicability of a Stateful Path Computation Element (PCE)"</span>, <span class="seriesInfo">RFC 8051</span>, <span class="seriesInfo">DOI 10.17487/RFC8051</span>, <time datetime="2017-01">January 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8051">https://www.rfc-editor.org/info/rfc8051</a>&gt;</span>. </dd>
<dt id="RFC8126">[RFC8126]</dt>
<dd>
<span class="refAuthor">Cotton, M.</span><span class="refAuthor">, Leiba, B.</span><span class="refAuthor">, and T. Narten</span>, <span class="refTitle">"Guidelines for Writing an IANA Considerations Section in RFCs"</span>, <span class="seriesInfo">BCP 26</span>, <span class="seriesInfo">RFC 8126</span>, <span class="seriesInfo">DOI 10.17487/RFC8126</span>, <time datetime="2017-06">June 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>&gt;</span>. </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">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>
<dt id="RFC8231">[RFC8231]</dt>
<dd>
<span class="refAuthor">Crabbe, E.</span><span class="refAuthor">, Minei, I.</span><span class="refAuthor">, Medved, J.</span><span class="refAuthor">, and R. Varga</span>, <span class="refTitle">"Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE"</span>, <span class="seriesInfo">RFC 8231</span>, <span class="seriesInfo">DOI 10.17487/RFC8231</span>, <time datetime="2017-09">September 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8231">https://www.rfc-editor.org/info/rfc8231</a>&gt;</span>. </dd>
<dt id="RFC8281">[RFC8281]</dt>
<dd>
<span class="refAuthor">Crabbe, E.</span><span class="refAuthor">, Minei, I.</span><span class="refAuthor">, Sivabalan, S.</span><span class="refAuthor">, and R. Varga</span>, <span class="refTitle">"Path Computation Element Communication Protocol (PCEP) Extensions for PCE-Initiated LSP Setup in a Stateful PCE Model"</span>, <span class="seriesInfo">RFC 8281</span>, <span class="seriesInfo">DOI 10.17487/RFC8281</span>, <time datetime="2017-12">December 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8281">https://www.rfc-editor.org/info/rfc8281</a>&gt;</span>. </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="RFC4657">[RFC4657]</dt>
<dd>
<span class="refAuthor">Ash, J., Ed.</span><span class="refAuthor"> and J.L. Le Roux, Ed.</span>, <span class="refTitle">"Path Computation Element (PCE) Communication Protocol Generic Requirements"</span>, <span class="seriesInfo">RFC 4657</span>, <span class="seriesInfo">DOI 10.17487/RFC4657</span>, <time datetime="2006-09">September 2006</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4657">https://www.rfc-editor.org/info/rfc4657</a>&gt;</span>. </dd>
<dt id="RFC4872">[RFC4872]</dt>
<dd>
<span class="refAuthor">Lang, J.P., Ed.</span><span class="refAuthor">, Rekhter, Y., Ed.</span><span class="refAuthor">, and D. Papadimitriou, Ed.</span>, <span class="refTitle">"RSVP-TE Extensions in Support of End-to-End Generalized Multi-Protocol Label Switching (GMPLS) Recovery"</span>, <span class="seriesInfo">RFC 4872</span>, <span class="seriesInfo">DOI 10.17487/RFC4872</span>, <time datetime="2007-05">May 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4872">https://www.rfc-editor.org/info/rfc4872</a>&gt;</span>. </dd>
<dt id="RFC4873">[RFC4873]</dt>
<dd>
<span class="refAuthor">Berger, L.</span><span class="refAuthor">, Bryskin, I.</span><span class="refAuthor">, Papadimitriou, D.</span><span class="refAuthor">, and A. Farrel</span>, <span class="refTitle">"GMPLS Segment Recovery"</span>, <span class="seriesInfo">RFC 4873</span>, <span class="seriesInfo">DOI 10.17487/RFC4873</span>, <time datetime="2007-05">May 2007</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc4873">https://www.rfc-editor.org/info/rfc4873</a>&gt;</span>. </dd>
<dt id="RFC6007">[RFC6007]</dt>
<dd>
<span class="refAuthor">Nishioka, I.</span><span class="refAuthor"> and D. King</span>, <span class="refTitle">"Use of the Synchronization VECtor (SVEC) List for Synchronized Dependent Path Computations"</span>, <span class="seriesInfo">RFC 6007</span>, <span class="seriesInfo">DOI 10.17487/RFC6007</span>, <time datetime="2010-09">September 2010</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc6007">https://www.rfc-editor.org/info/rfc6007</a>&gt;</span>. </dd>
<dt id="RFC7551">[RFC7551]</dt>
<dd>
<span class="refAuthor">Zhang, F., Ed.</span><span class="refAuthor">, Jing, R.</span><span class="refAuthor">, and R. Gandhi, Ed.</span>, <span class="refTitle">"RSVP-TE Extensions for Associated Bidirectional Label Switched Paths (LSPs)"</span>, <span class="seriesInfo">RFC 7551</span>, <span class="seriesInfo">DOI 10.17487/RFC7551</span>, <time datetime="2015-05">May 2015</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc7551">https://www.rfc-editor.org/info/rfc7551</a>&gt;</span>. </dd>
<dt id="RFC8253">[RFC8253]</dt>
<dd>
<span class="refAuthor">Lopez, D.</span><span class="refAuthor">, Gonzalez de Dios, O.</span><span class="refAuthor">, Wu, Q.</span><span class="refAuthor">, and D. Dhody</span>, <span class="refTitle">"PCEPS: Usage of TLS to Provide a Secure Transport for the Path Computation Element Communication Protocol (PCEP)"</span>, <span class="seriesInfo">RFC 8253</span>, <span class="seriesInfo">DOI 10.17487/RFC8253</span>, <time datetime="2017-10">October 2017</time>, <span>&lt;<a href="https://www.rfc-editor.org/info/rfc8253">https://www.rfc-editor.org/info/rfc8253</a>&gt;</span>. </dd>
<dt id="PCEP-YANG">[PCEP-YANG]</dt>
<dd>
<span class="refAuthor">Dhody, D., Ed.</span><span class="refAuthor">, Hardwick, J.</span><span class="refAuthor">, Beeram, V.</span><span class="refAuthor">, and J. Tantsura</span>, <span class="refTitle">"A YANG Data Model for Path Computation Element Communications Protocol (PCEP)"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-pce-pcep-yang-13</span>, <time datetime="2019-10-31">31 October 2019</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-pce-pcep-yang-13">https://tools.ietf.org/html/draft-ietf-pce-pcep-yang-13</a>&gt;</span>. </dd>
<dt id="I-D.ietf-pce-stateful-path-protection">[PCE-PROTECTION]</dt>
<dd>
<span class="refAuthor">Ananthakrishnan, H.</span><span class="refAuthor">, Sivabalan, S.</span><span class="refAuthor">, Barth, C.</span><span class="refAuthor">, Minei, I.</span><span class="refAuthor">, and M. Negi</span>, <span class="refTitle">"PCEP Extensions for Associating Working and Protection LSPs with Stateful PCE"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-pce-stateful-path-protection-11</span>, <time datetime="2019-09-25">25 September 2019</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-pce-stateful-path-protection-11">https://tools.ietf.org/html/draft-ietf-pce-stateful-path-protection-11</a>&gt;</span>. </dd>
<dt id="I-D.ietf-pce-association-diversity">[PCE-DIVERSITY]</dt>
<dd>
<span class="refAuthor">Litkowski, S.</span><span class="refAuthor">, Sivabalan, S.</span><span class="refAuthor">, Barth, C.</span><span class="refAuthor">, and M. Negi</span>, <span class="refTitle">"Path Computation Element Communication Protocol (PCEP) Extension for LSP Diversity Constraint Signaling"</span>, <span class="refContent">Work in Progress</span>, <span class="seriesInfo">Internet-Draft, draft-ietf-pce-association-diversity-14</span>, <time datetime="2020-01-26">26 January 2020</time>, <span>&lt;<a href="https://tools.ietf.org/html/draft-ietf-pce-association-diversity-14">https://tools.ietf.org/html/draft-ietf-pce-association-diversity-14</a>&gt;</span>. </dd>
</dl>
</section>
</section>
<div id="ex">
<section id="section-appendix.a">
      <h2 id="name-example-of-an-operator-conf">
<a href="#section-appendix.a" class="section-number selfRef">Appendix A. </a><a href="#name-example-of-an-operator-conf" class="section-name selfRef">Example of an Operator-Configured Association Range</a>
      </h2>
<p id="section-appendix.a-1">Consider an Association Type T1 (which allows both dynamic and
    Operator-configured Associations with a default range of
    &lt;0x1000, 0xffff&gt;). Consider that, because of the needs of the
    network, the PCE needs to create more dynamic associations and would like
    to change the Association Range to &lt;0xbffe, 0xffff&gt; instead. During
    PCEP session establishment, the PCE would advertise the new range. The PCC
    could skip advertising, as the default values are used. If a PCC is
    creating a dynamic association (with the PCC as the Association Source),
    it needs to pick a free Association ID for type T1 in the range
    &lt;0x1, 0x0fff&gt;, whereas if a PCE is creating a dynamic association
    (with the PCE as the Association Source), it needs to pick a free
    Association ID from the range &lt;0x1, 0xbffd&gt;. Similarly, if
    an Operator-configured Association is manually configured with the PCC as
    the Association Source, it should be from the range &lt;0x1000,
    0xffff&gt;, whereas if the PCE is the Association Source, it should be
    from the range &lt;0xbffe, 0xffff&gt;. If the Association Source is
    not a PCEP peer (for example, an NMS), then the default range of
    &lt;0x1000, 0xffff&gt; is considered.<a href="#section-appendix.a-1" class="pilcrow">¶</a></p>
</section>
</div>
<div id="Acknowledgments">
<section id="section-appendix.b">
      <h2 id="name-acknowledgments">
<a href="#name-acknowledgments" class="section-name selfRef">Acknowledgments</a>
      </h2>
<p id="section-appendix.b-1">We would like to thank <span class="contact-name">Yuji Kamite</span> and <span class="contact-name">Joshua George</span> for
     their contributions to this document. Thanks also to <span class="contact-name">Venugopal Reddy</span>,
     <span class="contact-name">Cyril Margaria</span>, <span class="contact-name">Rakesh      Gandhi</span>, <span class="contact-name">Mike Koldychev</span>, and <span class="contact-name">Adrian Farrel</span> for their useful comments.<a href="#section-appendix.b-1" class="pilcrow">¶</a></p>
<p id="section-appendix.b-2">We would like to thank <span class="contact-name">Julien Meuric</span> for shepherding this
   document and providing comments with text suggestions.<a href="#section-appendix.b-2" class="pilcrow">¶</a></p>
<p id="section-appendix.b-3">Thanks to <span class="contact-name">Stig Venaas</span> for the RTGDIR review comments.<a href="#section-appendix.b-3" class="pilcrow">¶</a></p>
<p id="section-appendix.b-4">Thanks to <span class="contact-name">Alvaro Retana</span>, <span class="contact-name">Mirja Kühlewind</span>, <span class="contact-name">Martin Vigoureux</span>,
      <span class="contact-name">Barry Leiba</span>, <span class="contact-name">Eric Vyncke</span>,
      <span class="contact-name">Suresh Krishnan</span>, and <span class="contact-name">Benjamin Kaduk</span> for the IESG comments.<a href="#section-appendix.b-4" class="pilcrow">¶</a></p>
</section>
</div>
<div id="Contributors">
<section id="section-appendix.c">
      <h2 id="name-contributors">
<a href="#name-contributors" class="section-name selfRef">Contributors</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Stephane Litkowski</span></div>
<div dir="auto" class="left"><span class="org">Orange</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:stephane.litkowski@orange.com" class="email">stephane.litkowski@orange.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Xian Zhang</span></div>
<div dir="auto" class="left"><span class="org">Huawei Technologies</span></div>
<div dir="auto" class="left"><span class="extended-address">F3-1-B RnD Center, Huawei Base</span></div>
<div dir="auto" class="left"><span class="street-address">Bantian, Longgang District</span></div>
<div dir="auto" class="left">
<span class="region">Shenzhen</span>, <span class="postal-code">518129</span>
</div>
<div dir="auto" class="left"><span class="country-name">China</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:zhang.xian@huawei.com" class="email">zhang.xian@huawei.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Mustapha Aissaoui</span></div>
<div dir="auto" class="left"><span class="org">Nokia</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:mustapha.aissaoui@nokia.com" class="email">mustapha.aissaoui@nokia.com</a>
</div>
</address>
</section>
</div>
<div id="authors-addresses">
<section id="section-appendix.d">
      <h2 id="name-authors-addresses">
<a href="#name-authors-addresses" class="section-name selfRef">Authors' Addresses</a>
      </h2>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Ina Minei</span></div>
<div dir="auto" class="left"><span class="org">Google, Inc.</span></div>
<div dir="auto" class="left"><span class="street-address">1600 Amphitheatre Parkway</span></div>
<div dir="auto" class="left">
<span class="locality">Mountain View</span>, <span class="region">CA</span> <span class="postal-code">94043</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:inaminei@google.com" class="email">inaminei@google.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Edward Crabbe</span></div>
<div dir="auto" class="left"><span class="org">Individual Contributor</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:edward.crabbe@gmail.com" class="email">edward.crabbe@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Siva Sivabalan</span></div>
<div dir="auto" class="left"><span class="org">Cisco Systems, Inc.</span></div>
<div dir="auto" class="left"><span class="street-address">170 West Tasman Dr.</span></div>
<div dir="auto" class="left">
<span class="locality">San Jose</span>, <span class="region">CA</span> <span class="postal-code">95134</span>
</div>
<div dir="auto" class="left"><span class="country-name">United States of America</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:msiva@cisco.com" class="email">msiva@cisco.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Hariharan Ananthakrishnan</span></div>
<div dir="auto" class="left"><span class="org">Netflix</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:hari@netflix.com" class="email">hari@netflix.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Dhruv Dhody</span></div>
<div dir="auto" class="left"><span class="org">Huawei</span></div>
<div dir="auto" class="left"><span class="street-address">Divyashree Techno Park, Whitefield</span></div>
<div dir="auto" class="left">
<span class="locality">Bangalore</span> <span class="postal-code">560066</span>
</div>
<div dir="auto" class="left"><span class="region">KA</span></div>
<div dir="auto" class="left"><span class="country-name">India</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:dhruv.ietf@gmail.com" class="email">dhruv.ietf@gmail.com</a>
</div>
</address>
<address class="vcard">
        <div dir="auto" class="left"><span class="fn nameRole">Yosuke Tanaka</span></div>
<div dir="auto" class="left"><span class="org">NTT Communications Corporation</span></div>
<div dir="auto" class="left">
<span class="street-address">Granpark Tower 3-4-1 Shibaura, Minato-ku</span>, <span class="region">Tokyo</span>
</div>
<div dir="auto" class="left"><span class="postal-code">108-8118</span></div>
<div dir="auto" class="left"><span class="country-name">Japan</span></div>
<div class="email">
<span>Email:</span>
<a href="mailto:yosuke.tanaka@ntt.com" class="email">yosuke.tanaka@ntt.com</a>
</div>
</address>
</section>
</div>
<script>var toc = document.getElementById("toc");
var tocToggle = toc.querySelector("h2");
var tocNav = toc.querySelector("nav");

// mobile menu toggle
tocToggle.onclick = function(event) {
    if (window.innerWidth < 1024) {
 var tocNavDisplay = tocNav.currentStyle ? tocNav.currentStyle.display : getComputedStyle(tocNav, null).display;
 if (tocNavDisplay == "none") {
     tocNav.style.display = "block";
 } else {
     tocNav.style.display = "none";
 }
    }
}

// toc anchor scroll to anchor
tocNav.addEventListener("click", function (event) {
    event.preventDefault();
    if (event.target.nodeName == 'A') {
 if (window.innerWidth < 1024) {
     tocNav.style.display = "none";
 }
 var href = event.target.getAttribute("href");
 var anchorId = href.substr(1);
 var anchor =  document.getElementById(anchorId);
 anchor.scrollIntoView(true);
 window.history.pushState("","",href);
    }
});

// switch toc mode when window resized
window.onresize = function () {
    if (window.innerWidth < 1024) {
 tocNav.style.display = "none";
    } else {
 tocNav.style.display = "block";
    }
}
</script>
</body>
</html>