<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.39 (Ruby 3.3.8) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="trust200902" docName="draft-yang-pce-pcep-over-quic-08" category="std" consensus="true" submissionType="IETF" xml:lang="en">
  <front>
    <title abbrev="PCEP over QUIC">PCEP over QUIC</title>

    <author initials="F." surname="Yang" fullname="Feng Yang">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <street>Xuanwumen West Street</street>
          <city>Beijing</city>
          <country>CN</country>
        </postal>
        <email>yangfeng@chinamobile.com</email>
      </address>
    </author>
    <author initials="C." surname="Lin" fullname="Changwang Lin">
      <organization>New H3C Technologies</organization>
      <address>
        <postal>
          <street>Yongjia North Rd</street>
          <city>Beijing</city>
          <country>CN</country>
        </postal>
        <email>linchangwang.04414@h3c.com</email>
      </address>
    </author>
    <author initials="S." surname="Sidor" fullname="Samuel Sidor">
      <organization>Cisco Systems, Inc.</organization>
      <address>
        <postal>
          <street>Pribinova 10</street>
          <city>Bratislava</city>
          <code>811 09</code>
          <country>SK</country>
        </postal>
        <email>ssidor@cisco.com</email>
      </address>
    </author>
    <author initials="X." surname="Zhang" fullname="Xiaoqiu Zhang">
      <organization>China Mobile</organization>
      <address>
        <postal>
          <street>Xuanwumen West Street</street>
          <city>Beijing</city>
          <country>CN</country>
        </postal>
        <email>zhangxiaoqiu@chinamobile.com</email>
      </address>
    </author>

    <date year="2026" month="November" day="17"/>

    <area>RTG</area>
    <workgroup>pce</workgroup>
    <keyword>pcep</keyword> <keyword>quic</keyword>

    <abstract>



<t>This document specifies the use of QUIC streams to implement the PCEP protocol for efficient and secure data transmission.</t>



    </abstract>



  </front>

  <middle>



<section anchor="introduction"><name>Introduction</name>

<t>The PCEP <xref target="RFC5440"></xref> facilitates communication between PCCs and PCEs, as well as among PCEs, to optimize network routing and resource utilization.</t>

<t>QUIC <xref target="RFC9369"></xref> is a transport protocol based on UDP, offering low-latency connections, multiplexing, improved congestion control, and built-in encryption, similar to TLS <xref target="RFC7301"></xref>.</t>

<t>Implementing PCEP over QUIC offers several key benefits. Three operational scenarios illustrate the transport limitations that motivate this work.</t>

<t>Use Case 1: Under current PCEP specifications, including <xref target="RFC5440"></xref> and <xref target="RFC8408"></xref>, all Path Setup Types, including SR-MPLS, SRv6, RSVP-TE, PCEP-LS, share the same session error domain. A fatal error for one PST (e.g., malformed PCEP message) forces teardown of the entire PCEP session per RFC5440, disrupting all other PSTs and topology reporting functions.</t>

<t>Use Case 2: Head-of-line blocking during bulk state synchronization. Planned PE upgrades trigger synchronized bursts of PCRpt, PCUpd. TCP's in-order delivery causes large, delayed bulk report messages to block subsequent latency-sensitive signaling such as PCReq.</t>

<t>This document primarily describes the protocol adaptations necessary for using a QUIC connection with the PCEP protocol. The protocol process fully adheres to the specifications described in RFC 5440.</t>

<section anchor="requirements-language"><name>Requirements Language</name>

<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>


</section>
</section>
<section anchor="terminology"><name>Terminology</name>

<t>PCEPoQ: PCEP using QUIC.</t>

</section>
<section anchor="summary-of-operations"><name>Summary of Operations</name>

<t>A PCEP-over-QUIC session consists of one mandatory control channel (stream0) plus one or more PST data channel-groups. There will be one outbound channel-group and one inbound channel-group for that PST. And each channel-group contains exactly two QUIC unidirectional streams: High-priority and Low-priority.</t>

<t>Static message mapping inside every channel-group: 
- High priority: PCReq, PCRep, PCUpd
- Low priority: PCRpt, LSRpt</t>

<section anchor="establish-pcepquic-connection"><name>Establish PCEP/QUIC Connection</name>

<t>The process of establishing a PCEP session is described in <xref target="RFC5440"></xref>.</t>

<t>Before two PCEPoQ speakers start exchanging routing information, they must establish a PCEP session.  It is established in two phases:</t>

<t>First, a QUIC connection is established at the transport layer as described in <xref target="RFC9000"></xref>. During the TLS handshake, the Application-Layer Protocol Negotiation (ALPN) token "pcepoq" is used.</t>

<t>Second, establish a PCEPoQ session over this transport connection. For PCC-to-PCE communication, the PCC acts as the QUIC Client, and the PCE serves as the QUIC Server. For PCE-to-PCE communication, the PCE that actively initiates the connection operates as the QUIC Client, while the PCE receiving the connection functions as the QUIC Server.</t>

<t>If both ends initiate PCEPoQ connections simultaneously, collision-resolution procedure defined in Appendix A of <xref target="RFC5440"></xref> should be followed.</t>

<t>PCEP over QUIC defines a Control Channel and multiple Data Channels; each Data Channel is bound to a single Path Setup Type (PST), and distinct PSTs run separate PCEP finite state machines for isolation.</t>

</section>
<section anchor="establish-pcepquic-control-channel"><name>Establish PCEP/QUIC Control Channel</name>

<t>After PCEPoQ session is established, the PCEPoQ speaker establishes a bidirectional stream for the "PCEPoQ control channel." The control channel is used to establish a PCEPoQ relationship between PCC and PCE, or between PCEs. Open messages are used to establish the PCEPoQ control channel. After the channel is established, Keepalive messages are sent to maintain the control channel. Close messages are used to terminate the control channel. Notify messages are used to send specified notifications. When an error occurs, a PCErr message is sent through the PCEPoQ control channel to notify the PCEPoQ peer.</t>

</section>
<section anchor="establish-pcepquic-data-channel"><name>Establish PCEP/QUIC Data Channel</name>

<t>After establishing the control channel, each PCEPoQ speaker may create data channels using unidirectional QUIC streams. These data channels are used to carry PCEReq and PCERep messages.  For IPv4 and IPv6 address families, separate data channels can also be established.  The advantage of separating the control channel from the data channels is that it allows for higher priority handling of the control channel's traffic, ensuring timely processing of control messages without delay caused by handling data messages.  Moreover, if PCEPoQ supports other address families in the future, using separate data channels can ensure that different address families do not interfere with each other.</t>

<t>Multiple PCEPoQ sessions <bcp14>MAY</bcp14> share the same QUIC connection. The "pcepoq" ALPN token is not session-specific.</t>

</section>
</section>
<section anchor="protocol-definitions"><name>Protocol Definitions</name>

<section anchor="pcep-over-quic-capability"><name>PCEP over QUIC Capability</name>

<t>Once a QUIC connection is established between a PCC and a PCE, or between two PCEs, the PCEPoQ speakers initiate the PCEPoQ session establishment process, during which various session parameters are negotiated. These parameters are carried within Open messages and include the Keepalive timer, DeadTimer, and policy rules that specify the conditions under which path computation requests may be sent to the PCE, as well as the supported PCEPoQ capabilities and other detailed capabilities. If the PCEPoQ session establishment phase fails because the PCEPoQ peers disagree on the session parameters or one of the PCEPoQ peers does not respond after the expiration of the establishment timer, successive retries are permitted. However, an implementation should use an exponential back-off procedure for session establishment retries.</t>

<t>To negotiate PCEPoQ-related capabilities, this document extends the PCEPoQ Capability TLV <xref target="f1"/>.</t>

<figure anchor="f1">
<name>PCEPoQ Capability TLV</name><artwork type="ascii-art" align="center"><![CDATA[
 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 (TBD1)         |          Length (4)           |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                            Capability                       |D|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

    Type      : 2 bytes (TBD1)
    Length    : 2 bytes (4)
    Capability:
      D: Bit 0, support data channel, this document

]]></artwork></figure>

<t>When sending an Open message to establish a PCEPoQ session, the local PCEPoQ capabilities are included. If capability negotiation fails, the PCEPoQ session establishment is aborted. After a failure, if no other sessions exist, a QUIC connection may choose to remain open or close based on specific implementation, though this document does not elaborate further.</t>

</section>
<section anchor="stream-id-mapping"><name>Stream-ID Mapping</name>

<t>After successful channel-group negotiation, the receiver builds a static mapping table:</t>

<t>QUIC Stream-ID -&gt; (PST, Priority)</t>

<t>All subsequent messages arriving on this stream are dispatched to the corresponding PST FSM.</t>

</section>
<section anchor="maintenance-of-control-channel"><name>Maintenance of Control Channel</name>

<t>Once a PCEPoQ session has been established, a PCE or PCC over QUIC may want to know that its PCEPoQ peer is still available for use.</t>

<t>PCEPoQ includes a keep-alive mechanism based on a Keepalive timer, a DeadTimer, and a Keepalive message. The PCEP Keepalive message is sent through the PCEPoQ control channel.</t>

<t>If no Keepalive message is received within the DeadTimer period, the PCEPoQ session <bcp14>SHOULD</bcp14> be reset and a new session <bcp14>SHOULD</bcp14> be attempted. While resetting the PCEPoQ session, the corresponding PCEPoQ data channel should also be reset.</t>

<t>The Notification message can be sent by either a PCE to a PCC, or by a PCC to a PCE, or by a PCE to a PCE, to notify of a specific event. This message is transmitted through the PCEPoQ control channel.</t>

<t>There are several circumstances in which a PCE over QUIC may want to notify a PCC or PCE over QUIC of a specific event.  For example, suppose that the PCE over QUIC suddenly gets overloaded, potentially leading to unacceptable response times.</t>

<t>The PCE over QUIC may want to notify one or more PCCs/PCEs over QUIC that some of their requests (listed in the notification) will not be satisfied or may experience unacceptable delays.  Upon receiving such notification, the PCC/PCE over QUIC may decide to redirect its path computation requests to another PCE over QUIC should an alternate PCE be available.  Similarly, a PCC/PCE over QUIC may desire to notify a PCE over QUIC of a particular event such as the cancellation of pending requests.</t>

</section>
<section anchor="pcepoq-connection-termination"><name>PCEPoQ Connection Termination</name>

<t>When one of the PCEP over QUIC peers wishes to terminate a PCEPoQ session, it first sends a Close message.  This message is transmitted through the PCEPoQ control channel.  The sender then closes the PCEPoQ session.  Upon receiving the Close Message, the recipient closes the corresponding PCEPoQ session.</t>

<t>If there are no other PCEPoQ sessions, the QUIC connection can be closed or kept permanently active depending on the implementation. This document assumes that the QUIC connection remains open. The following state machine descriptions are based on this assumption and will not restate it.</t>

<t>The PCEP over QUIC Error message is sent in several situations: when a protocol error condition is met or when the request is not compliant with the PCEP over QUIC specification (e.g., capability not supported, reception of a message with a mandatory missing object, policy violation, unexpected message, unknown request reference).</t>

<t>This message is transmitted through the PCEPoQ control channel.</t>

</section>
<section anchor="pcepoq-framing-layer"><name>PCEPoQ Framing Layer</name>

<t>Some PCEPoQ messages, although sent in the control channel, are meant for a function channel, such as the responding Open message or Keepalive message for a function channel.  These messages need to carry the corresponding function channel/stream ID information.</t>

<t>There are two types of PCEPoQ Frames: Control and Data.</t>

<t>Data frames have the following format:</t>

<figure><artwork><![CDATA[
PCEPoQ Data Frame Format {
   Type (16) = 0,
   Length (16),
   Frame Payload (...)
}

PCEPoQ Control Frame Format {
  Type (16) = 1,
  Length (16),
  Stream ID (62),
  padding (2) = 0,
  Frame Payload (...)
}

]]></artwork></figure>

<t>Type: two octets, identifying the frame type.</t>

<t>Length: The two-byte unsigned integer that describes the length in bytes of the frame payload.</t>

<t>Stream ID: A 62-bit integer indicating the receiving stream ID of this message.</t>

<t>Frame Payload: PCEP messages.</t>

<t><xref target="t1"/> lists the frame type to be used when PCEP messages are sent in different channels.</t>

<table anchor="t1">
<name>PCEPoQ Frame Type Mapping</name>
<thead>
<tr>
<th>&#160;</th>
<th>Control Channel</th>
<th>Data Channel</th>
</tr>
</thead>
<tbody>
<tr>
<td>Open</td>
<td>Control</td>
<td>Data</td>
</tr>
<tr>
<td>Keepalive</td>
<td>Control</td>
<td>Data</td>
</tr>
<tr>
<td>Notification</td>
<td>Control</td>
<td>Data</td>
</tr>
<tr>
<td>PCErr</td>
<td>Control</td>
<td>Data</td>
</tr>
<tr>
<td>PCReq</td>
<td>/</td>
<td>Data</td>
</tr>
<tr>
<td>PCRep</td>
<td>/</td>
<td>Data</td>
</tr>
<tr>
<td>Close</td>
<td>Control</td>
<td>Data</td>
</tr>
</tbody>
</table>

</section>
<section anchor="path-computation-request-and-reply"><name>Path Computation Request and Reply</name>

<t>Once a PCC/PCE has successfully established a PCEPoQ session with one or more PCEs, if an event is triggered that requires the computation of a set of paths, the PCC/PCE first selects one or more PCEs. Once the PCC/PCE has selected a PCE, it sends a path computation request to the PCE (PCReq message) by PCEPoQ connection.</t>

<t>The PCReq message can only be sent and received through the PCEPoQ data channel.  If this message is received on the control channel, it will be ignored.</t>

<t>Upon receiving a path computation request from a PCC/PCE, the PCE initiates a path computation. The result is then sent to the PCC/PCE via a PCRep message through the PCEPoQ data channel.</t>

<t>The PCRep message can only be sent and received through the PCEPoQ data channel.  If this message is received on the control channel, it will be ignored.</t>

</section>
</section>
<section anchor="pcepoq-finite-state-machine-fsm"><name>PCEPoQ Finite State Machine (FSM)</name>

<section anchor="events-for-the-pcepoq-fsm"><name>Events for the PCEPoQ FSM</name>

<section anchor="optional-events-linked-to-optional-session-attributes"><name>Optional Events Linked to Optional Session Attributes</name>

<t>The Inputs to the PCEPoQ FSM are events.  Events can either be mandatory or optional.  Some optional events are linked to optional session attributes.  Optional session attributes enable several groups of FSM functionality.</t>

<t>The linkage between FSM functionality, events, and the optional session attributes are described below.</t>

<figure><artwork><![CDATA[
Group 1: Automatic Administrative Events (Start/Stop)

  Optional Session Attributes: AllowAutoStart,
                               AllowAutoStop,
                               DampPeerOscillations,
                               IdleHoldTime, 
                               IdleHoldTimer

Group 2: Unconfigured Peers

  Optional Session Attributes: AcceptConnectionsUnconfiguredPeers

Group 3: QUIC processing

  Optional Session Attributes: PassiveQuicEstablishment, 
                               TrackQuicState

Group 4:  PCEPoQ Message Processing

  Optional Session Attributes: DelayOpen, 
                               DelayOpenTime,
                               DelayOpenTimer,
                               SendNotificationWithoutOpen,
                               CollisionDetectEstablishedState
 
]]></artwork></figure>

</section>
<section anchor="administrative-events"><name>Administrative Events</name>

<t>Event 1: ManualStart</t>

<t>Event 2: ManualStop</t>

<t>Event 3: AutoStart</t>

<t>Event 4: ManualStart_with_PassiveQuicEstablishment</t>

<t>Event 5: AutoStart_with_PassiveQuicEstablishment</t>

<t>Event 6: AutoStart_with_DampPeerOscillations</t>

<t>Event 7: AutoStart_with_DampPeerOscillations_and_PassiveQuicEstablishment</t>

<t>Event 8: AutoStop</t>

</section>
<section anchor="timer-events"><name>Timer Events</name>

<t>Event 9: ConnectRetryTimer_Expires</t>

<t>Event 10: HoldTimer_Expires</t>

<t>Event 11: KeepaliveTimer_Expires</t>

<t>Event 12: DelayOpenTimer_Expires</t>

<t>Event 13: IdleHoldTimer_Expires</t>

</section>
<section anchor="quic-connection-based-events"><name>QUIC Connection-Based Events</name>

<t>Event 14: QuicConnection_Valid</t>

<t>Event 15: QUIC_CR_Invalid</t>

<t>Event 16: QUIC_CR_Acked</t>

<t>Event 17: QuicConnectionConfirmed</t>

<t>Event 18: QuicConnectionFails</t>

</section>
<section anchor="pcepoq-message-based-events"><name>PCEPoQ Message-Based Events</name>

<t>Event 19: PCEPOpen</t>

<t>Event 20: PCEPOpen_with_DelayOpenTimer_Running</t>

<t>Event 21: PCEPHeaderErr</t>

<t>Event 22: PCEPOpenMsgErr</t>

<t>Event 23: OpenCollisionDump</t>

<t>Event 24: NotifMsgVerErr</t>

<t>Event 25: NotifMsg</t>

<t>Event 26: KeepaliveMsg</t>

<t>Event 27: NotificationMsg</t>

<t>Event 28: ErrorMsg</t>

</section>
</section>
<section anchor="description-of-fsm"><name>Description of FSM</name>

<t>The section describes the PCEPoQ finite state machine (FSM).</t>

<figure anchor="f2">
<name>PCEPoQ Finite State Machine</name><artwork type="ascii-art" align="center"><![CDATA[
            +-----------+<------+
+-----------| SessionUP |<---+  |
|           +-----------+    |  |
|                            |  |
|        +->+-----------+    |  |
|        |  | KeepWait  |----+  |
|        +--|           |<---+  |
|  +--------+-----------+    |  |
|  |             |           |  |
|  |             V           |  |
|  |     +->+-----------+----+  |
|  |     |  | OpenWait  |-------+
|  |     +--|           |<------+
|  |  +-----+-----------+<---+  |
|  |  |          |           |  |
|  |  |          V           |  |
|  |  |  +->+-----------+    |  |
|  |  |  |  |  Pending  |----+  |
|  |  |  +--+-----------+<---+  |
|  |  |          |           |  |
|  |  |          V           |  |
|  |  +----->+-------+       |  |
|  +-------->| Idle  |-------+  |
+----------->+-------+----------+

]]></artwork></figure>

<t>PCEPoQ defines the following set of variables:</t>

<t>Connect: the timer (in seconds) started after having initialized a QUIC connection using the ALPN token registered for PCEP over QUIC. The value of the Connect timer is 60 seconds.</t>

<t>ConnectRetry: the number of times the system has tried to establish a QUIC connection with a PCEPoQ peer without success.</t>

<t>ConnectMaxRetry: the maximum number of times the system tries to establish a QUIC connection using the ALPN token registered for PCEP over QUIC before going back to the Idle state. The value of the ConnectMaxRetry is 5.</t>

<t>OpenWait: the timer that corresponds to the amount of time a PCEPoQ peer will wait to receive a PCEPoQ Open message from the PCEPoQ peer after the expiration of which the system releases the PCEPoQ resource and goes back to the Idle state. The OpenWait timer has a fixed value of 60 seconds.</t>

<t>KeepWait: the timer that corresponds to the amount of time a PCEPoQ peer will wait to receive a Keepalive or a PCEoQErr message from the PCEPoQ peer after the expiration of which the system releases the PCEPoQ resource and goes back to the Idle state. The KeepWait timer has a fixed value of 60 seconds.</t>

<t>OpenRetry: the number of times the system has received a PCEPoQ Open message with unacceptable PCEPoQ session characteristics.</t>

<t>The following two state variables are defined:</t>

<t>RemoteOK: a boolean that is set to 1 if the system has received an acceptable PCEPoQ Open message.</t>

<t>LocalOK: a boolean that is set to 1 if the system has received a PCEPoQ Keepalive message acknowledging that the PCEPoQ Open message sent to the peer was valid.</t>

<section anchor="idle-state"><name>Idle State:</name>

<t>The idle state is the initial PCEPoQ state where the PCEPoQ (also referred to as "the system") waits for an initialization event that can either be manually triggered by the user(configuration) or automatically triggered by various events. In the Idle state, PCEPoQ resources are allocated (memory, process, etc.), but no PCEPoQ messages are accepted from any peer.</t>

<t>The following set of variables are initialized:</t>

<t><ul>
  <li>QUICRetry=0,</li>
  <li>LocalOK=0,</li>
  <li>RemoteOK=0,</li>
  <li>OpenRetry=0.</li>
</ul></t>

<t>In this state, PCEP FSM refuses all incoming PCEP connections for this peer. No resources are allocated to the peer. In response to a ManualStart event (Event 1) or an AutoStart event (Event 3), the local system:</t>

<t><ul>
  <li>Initiates a QUIC connection with the PCEP peer,</li>
  <li>starts the ConnectRetryTimer with the initial value,</li>
  <li>changes its state to Pending.</li>
</ul></t>

<t>The ManualStop event (Event 2) and AutoStop (Event 8) event are ignored in the Idle state.</t>

<t>In response to a ManualStart_with_PassiveQuicEstablishment event (Event 4) or AutoStart_with_PassiveQuicEstablishment event (Event 5), the local system:</t>

<t><ul>
  <li>Initiates a QUIC connection with the PCEP peer,</li>
  <li>sets the ConnectRetryCounter to zero,</li>
  <li>starts the ConnectRetryTimer with the initial value,</li>
  <li>changes its state to OpenWait.</li>
</ul></t>

<t>If the DampPeerOscillations attribute is set to TRUE, the following three additional events may occur within the Idle state:</t>

<t><ul>
  <li>AutoStart_with_DampPeerOscillations (Event 6),</li>
  <li>AutoStart_with_DampPeerOscillations_and_PassiveQuicEstablishment (Event 7),</li>
  <li>IdleHoldTimer_Expires (Event 13).</li>
</ul></t>

<t>Upon receiving these 3 events, the local system will use these events to prevent peer oscillations. The method of preventing persistent peer oscillation is outside the scope of this document.</t>

<t>Any other event (Events 9-12, 15-28) received in the Idle state does not cause change in the state of the local system.</t>

</section>
<section anchor="pending-state"><name>Pending State:</name>

<t>In this state, PCEP FSM is waiting for the QUIC connection to be completed.</t>

<t>The start events (Events 1, 3-7) are ignored in the Pending state.</t>

<t>In response to a ManualStop event (Event 2), the local system:</t>

<t><ul>
  <li>drops the QUIC connection,</li>
  <li>releases all PCEP resources,</li>
  <li>sets ConnectRetryCounter to zero,</li>
  <li>stops the ConnectRetryTimer and sets ConnectRetryTimer to zero, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>In response to the ConnectRetryTimer_Expires event (Event 9), the local system:</t>

<t><ul>
  <li>drops the QUIC connection,</li>
  <li>restarts the ConnectRetryTimer,</li>
  <li>stops the DelayOpenTimer and resets the timer to zero,</li>
  <li>initiates a QUIC connection to the other PCEP peer,</li>
  <li>continues to listen for a QUIC connection that may be initiated by the remote PCEP peer, and</li>
  <li>stays in the Pending state.</li>
</ul></t>

<t>If the DelayOpenTimer_Expires event (Event 12) occurs in the Connect state, the local system:</t>

<t><ul>
  <li>sends an Open message to its peer,</li>
  <li>sets the HoldTimer to a large value, and</li>
  <li>changes its state to OpenWait.</li>
</ul></t>

<t>If the PCEP FSM receives a QuicConnection_Valid event (Event 14), the QUIC connection is processed, and the connection remains in the Pending state.</t>

<t>If the PCEP FSM receives a QUIC_CR_Invalid event (Event 15), the local system rejects the QUIC connection, and the connection remains in the Pending state.</t>

<t>If the QUIC connection succeeds (Event 16 or Event 17), the local system checks the DelayOpen attribute prior to processing. If the DelayOpen attribute is set to TRUE, the local system:</t>

<t><ul>
  <li>stops the ConnectRetryTimer (if running) and sets the ConnectRetryTimer to zero,</li>
  <li>sets the DelayOpenTimer to the initial value, and</li>
  <li>stays in the Pending state.</li>
</ul></t>

<t>If the DelayOpen attribute is set to FALSE, the local system:</t>

<t><ul>
  <li>stops the ConnectRetryTimer (if running) and sets the ConnectRetryTimer to zero,</li>
  <li>completes PCEP initialization</li>
  <li>sends an Open message to its peer,</li>
  <li>sets the HoldTimer to a large value, and</li>
  <li>changes its state to OpenWait.</li>
</ul></t>

<t>A HoldTimer value of 4 minutes is suggested.</t>

<t>If the QUIC connection fails (Event 18), the local system checks the DelayOpenTimer. If the DelayOpenTimer is running, the local system:</t>

<t><ul>
  <li>restarts the ConnectRetryTimer with the initial value,</li>
  <li>stops the DelayOpenTimer and resets its value to zero,</li>
  <li>continues to listen for a QUIC connection that may be initiated by the remote PCEP peer, and</li>
  <li>Remains in the Pending state.</li>
</ul></t>

<t>If the DelayOpenTimer is not running, the local system:</t>

<t><ul>
  <li>stops the ConnectRetryTimer to zero,</li>
  <li>drops the QUIC connection,</li>
  <li>releases all PCEP resources, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If an Open message is received while the DelayOpenTimer is running (Event 20), the local system:</t>

<t><ul>
  <li>stops the ConnectRetryTimer (if running) and sets the ConnectRetryTimer to zero,</li>
  <li>completes the PCEP initialization,</li>
  <li>stops and clears the DelayOpenTimer (sets the value to zero),</li>
  <li>sends an Open message,</li>
  <li>sends a Keepalive message,</li>
  <li>and changes its state to KeepWait.</li>
</ul></t>

<t>If the value of the Autonomous System field is the same as the local Autonomous System number, set the connection status to an internal; otherwise set it to "external".</t>

<t>If PCEP message header checking (Event 21) or Open message checking detects an error (Event 22), the local system:</t>

<t><ul>
  <li>(optionally) If the SendNotificationWithoutOpen attribute is set to TRUE, then the local system first sends a Notification message with the appropriate error code, and then</li>
  <li>stops the ConnectRetryTimer (if running) and sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If a PCErr message is received with a version error (Event 24), the
local system checks the DelayOpenTimer. If the DelayOpenTimer is
running, the local system:</t>

<t><ul>
  <li>stops the ConnectRetryTimer (if running) and sets the ConnectRetryTimer to zero,</li>
  <li>stops and resets the DelayOpenTimer (sets to zero),</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the DelayOpenTimer is not running, the local system:</t>

<t><ul>
  <li>stops the ConnectRetryTimer and sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>performs peer oscillation damping if the DampPeerOscillations attribute is set to True, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>In response to any other events (Events 8, 10-11, 13, 19, 23,
25-28), the local system:</t>

<t><ul>
  <li>if the ConnectRetryTimer is running, stops and resets the ConnectRetryTimer (sets to zero),</li>
  <li>if the DelayOpenTimer is running, stops and resets the DelayOpenTimer (sets to zero),</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>performs peer oscillation damping if the DampPeerOscillations attribute is set to True, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>The start events (Events 1, 3-7) are ignored in the Pending state.</t>

<t>In response to a ManualStop event (Event 2), the local system:</t>

<t><ul>
  <li>If the DelayOpenTimer is running and the SendNotificationWithoutOpen session attribute is set, the local system sends a PCErr with a Cease,</li>
  <li>releases all PCEP resources including stopping the DelayOpenTimer</li>
  <li>drops the QUIC connection,</li>
  <li>sets ConnectRetryCounter to zero,</li>
  <li>stops the ConnectRetryTimer and sets the ConnectRetryTimer to zero, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>In response to a ConnectRetryTimer_Expires event (Event 9), the local system:</t>

<t><ul>
  <li>restarts the ConnectRetryTimer (with initial value),</li>
  <li>initiates a QUIC connection to the other PCEP peer,</li>
  <li>continues to listen for a QUIC connection that may be initiated by a remote PCEP peer, and</li>
  <li>changes its state to OpenWait.</li>
</ul></t>

<t>If the local system receives a DelayOpenTimer_Expires event (Event 12), the local system:</t>

<t><ul>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>stops and clears the DelayOpenTimer (set to zero),</li>
  <li>completes the PCEP initialization,</li>
  <li>sends the Open message to its remote peer,</li>
  <li>sets its hold timer to a large value, and</li>
  <li>changes its state to OpenWait.</li>
</ul></t>

<t>A HoldTimer value of 4 minutes is also suggested for this state transition.</t>

<t>If the local system receives a QuicConnection_Valid event (Event 14), the local system processes the QUIC connection flags and stays in the Pending state.</t>

<t>If the local system receives a QUIC_CR_Invalid event (Event 15), the local system rejects the QUIC connection and stays in the Pending State.</t>

<t>In response to the success of a QUIC connection (Event 16 or Event 17), the local system checks the DelayOpen optional attribute prior to processing.</t>

<t>If the DelayOpen attribute is set to TRUE, the local system:</t>

<t><ul>
  <li>stops the ConnectRetryTimer and sets the ConnectRetryTimer to zero,</li>
  <li>sets the DelayOpenTimer to the initial value (DelayOpenTime), and</li>
  <li>stays in the Pending state.</li>
</ul></t>

<t>If the DelayOpen attribute is set to FALSE, the local system:</t>

<t><ul>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>completes the PCEP initialization,</li>
  <li>sends the Open message to its peer,</li>
  <li>sets its HoldTimer to a large value, and</li>
  <li>changes its state to OpenWait.</li>
</ul></t>

<t>A HoldTimer value of 4 minutes is suggested as a "large value" for the HoldTimer.</t>

<t>If the local system receives a QUICConnectionFails event (Event 18), the local system:</t>

<t><ul>
  <li>restarts the ConnectRetryTimer (with the initial value),</li>
  <li>stops and clears the DelayOpenTimer (sets the value to zero),</li>
  <li>releases all PCEP resource,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>optionally performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If an Open message is received and the DelayOpenTimer is running (Event 20), the local system:</t>

<t><ul>
  <li>stops the ConnectRetryTimer (if running) and sets the ConnectRetryTimer to zero,</li>
  <li>stops and clears the DelayOpenTimer (sets to zero),</li>
  <li>completes the PCEP initialization,</li>
  <li>sends an Open message,</li>
  <li>sends a Keepalive message,</li>
  <li>if the HoldTimer value is non-zero,</li>
  <li>starts the KeepaliveTimer to initial value,</li>
  <li>resets the HoldTimer to the negotiated value, else if the HoldTimer is zero</li>
  <li>resets the KeepaliveTimer (set to zero),</li>
  <li>resets the HoldTimer to zero, and</li>
  <li>changes its state to KeepWait.</li>
</ul></t>

<t>If the value of the Autonomous System field is the same as the local Autonomous System number, set the connection status to an internal connection; otherwise it is "external".</t>

<t>If PCEP message header checking (Event 21) or Open message checking detects an error (Event 22), the local system:</t>

<t><ul>
  <li>(optionally) sends a PCErr message with the appropriate error code if the SendNotificationWithoutOpen attribute is set to TRUE,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If a PCErr message is received with a version error (Event 24), the local system checks the DelayOpenTimer.  If the DelayOpenTimer is running, the local system:</t>

<t><ul>
  <li>stops the ConnectRetryTimer (if running) and sets the ConnectRetryTimer to zero,</li>
  <li>stops and resets the DelayOpenTimer (sets to zero),</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the DelayOpenTimer is not running, the local system:</t>

<t><ul>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>In response to any other event (Events 8, 10-11, 13, 19, 23, 25-28), the local system:</t>

<t><ul>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by one,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

</section>
<section anchor="openwait"><name>OpenWait:</name>

<t>In this state, PCEP FSM waits for an Open message from its peer. The start events (Events 1, 3-7) are ignored in the OpenWait state.</t>

<t>If a ManualStop event (Event 2) is issued in the OpenWait state, the local system:</t>

<t><ul>
  <li>sends the Close with a Cease,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>sets the ConnectRetryCounter to zero, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If an AutoStop event (Event 8) is issued in the OpenWait state, the local system:</t>

<t><ul>
  <li>sends the Close with a Cease,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all the PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the HoldTimer_Expires (Event 10) event occurs, the local system:</t>

<t><ul>
  <li>sends a PCErr message with the error code Hold Timer Expired,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If a QUICConnection_Valid (Event 14), QUIC_CR_Acked (Event 16), or a QUICConnectionConfirmed event (Event 17) is received, a second QUIC connection may be in progress.</t>

<t>This second QUIC connection is tracked per Connection Collision processing until an Open message is received.</t>

<t>A QUIC Connection Request for an Invalid port (QUIC_CR_Invalid (Event 15)) is ignored.</t>

<t>If a QUICConnectionFails event (Event 18) is received, the local system:</t>

<t><ul>
  <li>closes the PCEP connection,</li>
  <li>restarts the ConnectRetryTimer,</li>
  <li>continues to listen for a QUIC connection that may be initiated by the remote PCEP peer, and</li>
  <li>changes its state to Pending.</li>
</ul></t>

<t>When an Open message is received, all fields are checked for correctness. If there are no errors in the Open message (Event 19), the local system:</t>

<t><ul>
  <li>resets the DelayOpenTimer to zero,</li>
  <li>sets the PCEP ConnectRetryTimer to zero,</li>
  <li>sends a Keepalive message, and</li>
  <li>sets a KeepaliveTimer as described below,</li>
  <li>sets the HoldTimer according to the negotiated value,</li>
  <li>changes its state to KeepWait.</li>
</ul></t>

<t>If the negotiated hold time value is zero, then the HoldTimer and KeepaliveTimer are not started. If the value of the Autonomous System field is the same as the local Autonomous System number, then the connection is an "internal" connection; otherwise, it is an "external" connection. If the PCEP message header checking (Event 21) or Open message checking detects an error (Event 22), the local system:</t>

<t><ul>
  <li>sends a PCErr message with the appropriate error code,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>Collision detection mechanisms need to be applied when a valid PCEP Open message is received (Event 19 or Event 20). A CollisionDetectDump event occurs when the PCEP implementation determines, by means outside the scope of this document, that a connection collision has occurred. If a connection in the OpenWait state is determined to be the connection that must be closed, an OpenCollisionDump (Event 23) is signaled to the state machine. If such an event is received in the OpenWait state, the local system:</t>

<t><ul>
  <li>sends a PCErr with a Cease,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If a PCErr message is received with a version error (Event 24), the local system:</t>

<t><ul>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>In response to any other event (Events 9, 11-13, 20, 25-28), the local system:</t>

<t><ul>
  <li>sends the PCErr with the Error Code Finite State Machine Error,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

</section>
<section anchor="keepwait-state"><name>KeepWait State:</name>

<t>In this state, PCEP waits for a Keepalive or PCErr message.</t>

<t>Any start event (Events 1, 3-7) is ignored in the KeepWait state.</t>

<t>In response to a ManualStop event (Event 2) initiated by the operator, the local system:</t>

<t><ul>
  <li>sends the PCErr message with a Cease,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>sets the ConnectRetryCounter to zero,</li>
  <li>sets the ConnectRetryTimer to zero, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>In response to the AutoStop event initiated by the system (Event 8), the local system:</t>

<t><ul>
  <li>sends the PCErr message with a Cease,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the HoldTimer_Expires event (Event 10) occurs before a Keepalive message is received, the local system:</t>

<t><ul>
  <li>sends the PCErr message with the Error Code Hold Timer Expired,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the local system receives a KeepaliveTimer_Expires event (Event 11), the local system:</t>

<t><ul>
  <li>sends a Keepalive message,</li>
  <li>restarts the KeepaliveTimer, and</li>
  <li>remains in the KeepWait state.</li>
</ul></t>

<t>In the event of a QUICConnection_Valid event (Event 14), or the success of a QUIC connection (Event 16 or Event 17) while in KeepWait, the local system needs to track the second connection.</t>

<t>If a QUIC connection is attempted with an invalid port (Event 15), the local system will ignore the second connection attempt.</t>

<t>If the local system receives a QUICConnectionFails event (Event 18) from the underlying QUIC or a PCErr message (Event 25), the local system:</t>

<t><ul>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the local system receives a PCErr message with a version error (NotifMsgVerErr (Event 24)), the local system:</t>

<t><ul>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the local system receives a valid Open message (PCEPOpen (Event 19)), the collision detect function is processed. If this connection is to be dropped due to connection collision, the local system:</t>

<t><ul>
  <li>sends a PCErr with a Cease,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If an Open message is received, all fields are checked for correctness. If the PCEP message header checking (PCEPHeaderErr (Event 21)) or Open message checking detects an error (PCEPOpenMsgErr (Event 22)), the local system:</t>

<t><ul>
  <li>sends a PCErr message with the appropriate error code,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If, during the processing of another Open message, the PCEP implementation determines, by a means outside the scope of this document, that a connection collision has occurred and this connection is to be closed, the local system will issue an OpenCollisionDump event (Event 23). When the local system receives an OpenCollisionDump event (Event 23), the local system:</t>

<t><ul>
  <li>sends a PCErr with a Cease,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the local system receives a Keepalive message (KeepaliveMsg(Event 26)), the local system:</t>

<t><ul>
  <li>restarts the HoldTimer and</li>
  <li>changes its state to SessionUP.</li>
</ul></t>

<t>In response to any other event (Events 9, 12-13, 20, 27-28), the local system:</t>

<t><ul>
  <li>sends a PCErr with a code of Finite State Machine Error,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

</section>
<section anchor="sessionup-state"><name>SessionUP State:</name>

<t>In the SessionUP state, the PCEP FSM can exchange PCReq, PCRep, PCErr, and Keepalive messages with its peer.</t>

<t>Any Start event (Events 1, 3-7) is ignored in the SessionUP state. In response to a ManualStop event (initiated by an operator) (Event 2), the local system:</t>

<t><ul>
  <li>sends the Close message with a Cease,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>sets the ConnectRetryCounter to zero, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>In response to an AutoStop event (Event 8), the local system:</t>

<t><ul>
  <li>sends a PCErr with a Cease,</li>
  <li>sets the ConnectRetryTimer to zero</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>One reason for an AutoStop event is when a PCEP instance receives a PCNtf message that exceeds the configured maximum number of prefixes. The local system automatically disconnects the peer.</t>

<t>If the HoldTimer_Expires event occurs (Event 10), the local system:</t>

<t><ul>
  <li>sends a PCErr message with the Error Code Hold Timer Expired,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the KeepaliveTimer_Expires event occurs (Event 11), the local system:</t>

<t><ul>
  <li>sends a Keepalive message, and</li>
  <li>restarts its KeepaliveTimer, unless the negotiated HoldTime value is zero.</li>
</ul></t>

<t>Each time the local system sends a Keepalive or PCNtf message, it restarts its KeepaliveTimer, unless the negotiated HoldTime value is zero.</t>

<t>A QUICConnection_Valid (Event 14), received for a valid port, will cause the second connection to be tracked.</t>

<t>An invalid QUIC connection (QUIC_CR_Invalid event (Event 15)) will be ignored.</t>

<t>In response to an indication that the QUIC connection is successfully established (Event 16 or Event 17), the second connection <bcp14>SHALL</bcp14> be tracked until it sends an Open message.</t>

<t>If a valid Open message (PCEPOpen (Event 19)) is received, and if the CollisionDetect SessionUP State optional attribute is TRUE, the Open message will be checked to see if it collides with any other connection. If the PCEP implementation determines that this connection needs to be terminated, it will process an OpenCollisionDump event (Event 23). If this connection needs to be terminated, the local system:</t>

<t><ul>
  <li>sends a PCErr with a Cease,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the local system receives a PCErr message (Event 24 or Event 25) or a QUICConnectionFails (Event 18) from the underlying QUIC, the local system:</t>

<t><ul>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all the PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>If the local system receives a Keepalive message (Event 26), the local system:</t>

<t><ul>
  <li>restarts its HoldTimer, if the negotiated HoldTime value is non-zero, and</li>
  <li>remains in the SessionUP state.</li>
</ul></t>

<t>If the local system receives a PCNtf message (Event 27), the local system:</t>

<t><ul>
  <li>processes the message,</li>
  <li>restarts its HoldTimer, if the negotiated HoldTime value is non-zero, and</li>
  <li>remains in the SessionUP state.</li>
</ul></t>

<t>If the local system receives a PCNtf message, and the PCNtf message error handling procedure detects an error (Event 28), the local system:</t>

<t><ul>
  <li>sends a PCErr message with an error,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

<t>In response to any other event (Events 9, 12-13, 20-22), the local system:</t>

<t><ul>
  <li>sends a PCErr message with the Error Code Finite State Machine Error,</li>
  <li>sets the ConnectRetryTimer to zero,</li>
  <li>releases all PCEP resources,</li>
  <li>drops the QUIC connection,</li>
  <li>increments the ConnectRetryCounter by 1,</li>
  <li>(optionally) performs peer oscillation damping if the DampPeerOscillations attribute is set to TRUE, and</li>
  <li>changes its state to Idle.</li>
</ul></t>

</section>
</section>
</section>
<section anchor="pcepoq-fsm-for-stateful-pcep"><name>PCEPoQ FSM for Stateful PCEP</name>

<t><xref target="RFC8231"></xref> describes the stateful PCEP negotiation process. Based on QUIC, after achieving SessionUP through the same negotiation process as stateless PCEPoQUIC, a data channel is established. Through this data channel, PCInitiate (LSP Initiate Request), PCUpd (Path Computation LSP Update Request), and PCRpt (Path Computation LSP State Report) messages are exchanged, thereby enabling LSP lifecycle management and state synchronization functions.</t>

</section>
<section anchor="stream-multiplexing"><name>Stream Multiplexing</name>

<t>QUIC offers stream multiplexing but does not provide a mechanism for exchanging stream priority information. Instead, it relies on receiving priority information from the application. PCEPoQ separates streams into control and data channels, assigning different priorities to each, ensuring that control messages receive higher priority processing.</t>

</section>
<section anchor="network-migration"><name>Network Migration</name>

<t>QUIC connections are not strictly bound to a single network path. Connection migration uses connection identifiers to allow connections to transfer to a new network path. In the current version of QUIC, only clients can migrate. The PCEPoQ protocol inherits this feature, allowing PCC over QUIC to perform network migration. PCE over QUIC should not identify PCC over QUIC by network address but rather use connection identifiers to recognize different PCC over QUIC instances.</t>

</section>
<section anchor="flow-control"><name>Flow Control</name>

<t>QUIC's flow control mechanism manages individual streams as well as the entire connection. A QUIC receiver controls the maximum amount of data a sender can transmit on any single stream and across all streams at any given time. PCEPoQ utilizes QUIC's flow control mechanism, separating control streams from data streams by using a control channel and a data channel.</t>

</section>
<section anchor="security-considerations"><name>Security Considerations</name>

<t>Security considerations for QUIC are described in <xref target="RFC9000"></xref>, and for the TLS handshake used to secure QUIC in <xref target="RFC9001"></xref>. Implementations that enable 0-RTT <bcp14>MUST</bcp14> implement anti-replay measures as described in Section 8 of <xref target="RFC9001"></xref>. Implementations may consider a fallback mechanism for TCP-based PCEP (as defined in <xref target="RFC5440"></xref>) when QUIC cannot be established.</t>

</section>
<section anchor="iana-considerations"><name>IANA Considerations</name>

<section anchor="registration-of-the-pcep-identification-string"><name>Registration of the PCEP Identification String</name>

<t>This document creates a new registration for the identification of PCEP in the "TLS Application-Layer Protocol Negotiation (ALPN) Protocol IDs" registry.</t>

<t>The "pcepoq" string identifies PCEP over QUIC:</t>

<t>protocol: PCEP over QUIC</t>

<t>Identification Sequence: "pcepoq"</t>

<t>Specification: This document</t>

</section>
<section anchor="pcepoq-capability-tlv"><name>PCEPoQ Capability TLV</name>

<t>IANA is asked to assign a new TLV code from PCEP TLV Type Indicators <xref target="RFC5440"></xref> for the PCEP over QUIC Capability as follows:</t>

<table anchor="t3">
<name>PCEPoQ Capability Registration</name>
<thead>
<tr>
<th>Value</th>
<th>TBD1</th>
</tr>
</thead>
<tbody>
<tr>
<td>Description</td>
<td>PCEPoQ Capability</td>
</tr>
<tr>
<td>Reference</td>
<td>This Document</td>
</tr>
<tr>
<td>Change Controller</td>
<td>IETF</td>
</tr>
</tbody>
</table>

<figure><artwork><![CDATA[
Capability:
    D: Bit 0, support data channel, this document
]]></artwork></figure>

</section>
</section>


  </middle>

  <back>


<references anchor="sec-combined-references">
<name>References</name>

    <references anchor="sec-normative-references">
<name>Normative References</name>



<reference anchor="RFC8231">
  <front>
    <title>Path Computation Element Communication Protocol (PCEP) Extensions for Stateful PCE</title>
    <author fullname="E. Crabbe" initials="E." surname="Crabbe"/>
    <author fullname="I. Minei" initials="I." surname="Minei"/>
    <author fullname="J. Medved" initials="J." surname="Medved"/>
    <author fullname="R. Varga" initials="R." surname="Varga"/>
    <date month="September" year="2017"/>
    <abstract>
      <t>The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Client (PCC) requests.</t>
      <t>Although PCEP explicitly makes no assumptions regarding the information available to the PCE, it also makes no provisions for PCE control of timing and sequence of path computations within and across PCEP sessions. This document describes a set of extensions to PCEP to enable stateful control of MPLS-TE and GMPLS Label Switched Paths (LSPs) via PCEP.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8231"/>
  <seriesInfo name="DOI" value="10.17487/RFC8231"/>
</reference>
<reference anchor="RFC5440">
  <front>
    <title>Path Computation Element (PCE) Communication Protocol (PCEP)</title>
    <author fullname="JP. Vasseur" initials="JP." role="editor" surname="Vasseur"/>
    <author fullname="JL. Le Roux" initials="JL." role="editor" surname="Le Roux"/>
    <date month="March" year="2009"/>
    <abstract>
      <t>This document specifies the Path Computation Element (PCE) Communication Protocol (PCEP) for communications between a Path Computation Client (PCC) and a PCE, or between two PCEs. Such interactions include path computation requests and path computation replies as well as notifications of specific states related to the use of a PCE in the context of Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering. PCEP is designed to be flexible and extensible so as to easily allow for the addition of further messages and objects, should further requirements be expressed in the future. [STANDARDS-TRACK]</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="5440"/>
  <seriesInfo name="DOI" value="10.17487/RFC5440"/>
</reference>
<reference anchor="RFC8408">
  <front>
    <title>Conveying Path Setup Type in PCE Communication Protocol (PCEP) Messages</title>
    <author fullname="S. Sivabalan" initials="S." surname="Sivabalan"/>
    <author fullname="J. Tantsura" initials="J." surname="Tantsura"/>
    <author fullname="I. Minei" initials="I." surname="Minei"/>
    <author fullname="R. Varga" initials="R." surname="Varga"/>
    <author fullname="J. Hardwick" initials="J." surname="Hardwick"/>
    <date month="July" year="2018"/>
    <abstract>
      <t>A Path Computation Element (PCE) can compute Traffic Engineering (TE) paths through a network; these paths are subject to various constraints. Currently, TE paths are Label Switched Paths (LSPs) that are set up using the RSVP-TE signaling protocol. However, other TE path setup methods are possible within the PCE architecture. This document proposes an extension to the PCE Communication Protocol (PCEP) to allow support for different path setup methods over a given PCEP session.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="8408"/>
  <seriesInfo name="DOI" value="10.17487/RFC8408"/>
</reference>
<reference anchor="RFC9000">
  <front>
    <title>QUIC: A UDP-Based Multiplexed and Secure Transport</title>
    <author fullname="J. Iyengar" initials="J." role="editor" surname="Iyengar"/>
    <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
    <date month="May" year="2021"/>
    <abstract>
      <t>This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9000"/>
  <seriesInfo name="DOI" value="10.17487/RFC9000"/>
</reference>
<reference anchor="RFC9001">
  <front>
    <title>Using TLS to Secure QUIC</title>
    <author fullname="M. Thomson" initials="M." role="editor" surname="Thomson"/>
    <author fullname="S. Turner" initials="S." role="editor" surname="Turner"/>
    <date month="May" year="2021"/>
    <abstract>
      <t>This document describes how Transport Layer Security (TLS) is used to secure QUIC.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9001"/>
  <seriesInfo name="DOI" value="10.17487/RFC9001"/>
</reference>
<reference anchor="RFC9369">
  <front>
    <title>QUIC Version 2</title>
    <author fullname="M. Duke" initials="M." surname="Duke"/>
    <date month="May" year="2023"/>
    <abstract>
      <t>This document specifies QUIC version 2, which is identical to QUIC version 1 except for some trivial details. Its purpose is to combat various ossification vectors and exercise the version negotiation framework. It also serves as a template for the minimum changes in any future version of QUIC.</t>
      <t>Note that "version 2" is an informal name for this proposal that indicates it is the second version of QUIC to be published as a Standards Track document. The protocol specified here uses a version number other than 2 in the wire image, in order to minimize ossification risks.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9369"/>
  <seriesInfo name="DOI" value="10.17487/RFC9369"/>
</reference>
<reference anchor="RFC2119">
  <front>
    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
    <author fullname="S. Bradner" initials="S." surname="Bradner"/>
    <date month="March" year="1997"/>
    <abstract>
      <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="2119"/>
  <seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC8174">
  <front>
    <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
    <author fullname="B. Leiba" initials="B." surname="Leiba"/>
    <date month="May" year="2017"/>
    <abstract>
      <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="8174"/>
  <seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>



    </references>

    <references anchor="sec-informative-references">
<name>Informative References</name>



<reference anchor="RFC7301">
  <front>
    <title>Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension</title>
    <author fullname="S. Friedl" initials="S." surname="Friedl"/>
    <author fullname="A. Popov" initials="A." surname="Popov"/>
    <author fullname="A. Langley" initials="A." surname="Langley"/>
    <author fullname="E. Stephan" initials="E." surname="Stephan"/>
    <date month="July" year="2014"/>
    <abstract>
      <t>This document describes a Transport Layer Security (TLS) extension for application-layer protocol negotiation within the TLS handshake. For instances in which multiple application protocols are supported on the same TCP or UDP port, this extension allows the application layer to negotiate which protocol will be used within the TLS connection.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="7301"/>
  <seriesInfo name="DOI" value="10.17487/RFC7301"/>
</reference>



    </references>

</references>



  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA+19e3fbNrbv//oUuM4fY7WSYtnOS2faU0d2pj5jJx7LaWdO
V1YXRUIyxxTJkpQdte58lvtZ7ic7+wGAAEk97DhNzp14pis2CeKxsZ8/bADd
breVF14c/OxFSSwHosjmshWmGf2WF7s7Oy92dlu+VwxEXgStfD6ehXkeJnGx
SKH48dHFq5aXSW8gzi/+0rqZDkTqy1YrSPzYm0GBIPMmRXfhxdMuvMD/0m5y
LbPuL/PQ7+48bz0SyThPIlnIfCAeiXM5g9cinIg4KUQsZSCDx+cyjTyo9pGY
p4FHJcW6sq0iLCLowNnw6Exgi+Jvb4+HLW88zuR17XEEHRwIGbeubgYtIbo4
ipR+wX5Cw9jsQOzu7O52d/D/otulZyLMxSSMIhmIMBbevEhmXhH6XhQtxHgh
3s+i3Wzi6z5Ow2toA0pdJtmg1RUZDBzbC2MY0que+Ad0A/5k0r2S8VQ/STLo
3vAyjD1xmozDSMKzvMikhHn5+9yLb+YzGYsfZV6IET2G935YLAbipQz/GVId
fjKPiwweDV/DX3LmhdFA4MxMoKHvfKx8RnX3/GRW7dywJ07C2PRteAnf3cB/
6qnuyz+SePrP0BOvk6y4FOeB7vpreSO+3xuKC+lfxkmUTEOZb9rFKIx93Vxv
Z3+/v//d5Z7f1MlRT4zCIMlMN0febC4j85CpGOZ+IkaLvJCzvCOOY79nDeAs
C8dhnFx7or9TdjCDOc0j79qjPgZQ8/N+X+y8sLs8+mvZZZAQaPE7H5tq6ujf
e+K/L+25/nvoJb+Ec/P0o833r9jAe26tNufA5z5INpAA+DhDcQQCSmx47hfz
TAovF8y8MCl50RFQTkwTmcOoisT+NoequppXvAxoHYuXSTbz4hjeqPG9jUEc
sjwsCqCwxAFd/PcxvVad9b1x8l3xa9iD4vR8noUDcVkUaT54/BjkqpenrBd0
W//lLcShF8lF2QqqKHEQzMIYuowTmcTi5GRotyPfS78bhJn0oevfhbKYmBbN
mOCzgbilZ4KaSbPkOgSNI4pLKb766u+nJ199JWg80EAyocfAYqCNCtlrPeIv
Ly69QtwAGUGtgPK4lFE6mUe9VitG4hRAD+SR81fD57t7ffXrk/39Hf10f+e5
+vXFzs5O+asu+2Lv6YtBK4wnleqe7WER6IJ870GX5LmcnIbxgDulNOUF/iN+
Oj86OzkYHr3jd1pX0R+ayn9BNYa/itE8w38rHynKb4dTGBZQ6FIi78SLG2/R
XlNTX/+yq6vK+e9BvQTwJyt9AcMVo9SDGb6kinMhCxDrDTujdfvOU5dCb+A7
RSEvm6LoIesB593c3PRUMZSbx3cmI/UIqoce/8ocWSnPXeq/eL7f3dlvtbpg
bbwxsq9ftFoXl2B0wMKiDihEnko/nIA+JY6b5xKZD40aKQxvBs8TEWJfqTgW
IuMH/FskfhIR8eRkEvohvgdfQOTSR2mHTnjgBnhxrmx+j3syC4MANBL09BiE
IwlAOcBL7Jeq+ifFte/ExPPDKCzQZoMozWbzGGwjDXgsixsJIn82HObUKHwJ
6hhE40ZGEWmaGRgT9RiGkKRFOAt/lTDnxU2SXYFGBamEEvhxJvNknvkw/gLa
Y5pCb4kMPym5eIe2Wg0oBftUUmDs5cAY0Km3h2cdIN9EZlhxlNx0UXpjf4F6
IJY0TujNbB4VIRD0PZTqIG1BFUAFUGYKGhlHR2ojiTrUufE8jIouuAdQU7ZI
sUBH5DCYyMtwZBcnI+okCuk76PWxnqyQx285Kty5HGYInniRuJLgZshYTsIi
74F2AVMAhJKs5uB97svYy8IENHQUzUn/SdZMhgoRdKSg8shBoJ5mCSgOLgcE
Q1JDn94CXw2BTKKPejuA7gCLZMgw1EHFhDy3QCEw2dE8wP6XvICk+EkpsXdA
GZjlMw+8hJEs5qm4AH/S+XB03j09Oxl14Jfrpx1xPvrhrHtx1KH2uvg8vwTH
kwaTk5WSxKNCZhkwdAB+WBj3xAGwYAGE4KfI6uDmirPRhdiWvWkP5tKLUFnK
gAcCuiP3prKNRX2UKellQXJjNDrOSqbYXLcI9NZ6uiOCMM/mKTMmjDCBjzJs
j5m8SFL0fhbAsEh8LDWZx8xXNpV3B+J76QXdZNIF90eKcZT4V1g6mBNrjufR
Fcg3zlK+APcoS7Qm6YkzcGZjHM8RuMvTzAtwGFk4nUJHysIS+RIMc44jOxue
pwWS9m0aABsNz/6EJr2bZDjRgYzQToMMeKBdchGhMuzgY29BtUBXeDiaeqRy
qMugvce5/GWOjKJEqZvLGGw+VAkyMAUmxfHkc/8SZR46In/pVVVcmoUz4GJw
qWEsPphjpeyMAHuBl2oeBjHFXkB/cbbnOc0EC08pxOImBM6r6UIUIata+AXr
gilCd94L0HTQ2IjpHJY3PaM4ALhBIDvASB5hnALWnhwcoPYJ+F9zoBGrS5Rf
kLAgF1unb0cXWx3+V7x+Q7+fH0G/z48O8ffR9wcnJ+aXliox+v7N25PD8rfy
y+Gb09Oj14f8MTwVzqPW1unBP7ZYP229Obs4fvP64GQL+144pCcRg8mU6OLJ
LM0gUAtgplrOeF8Oz/7f/+3vi99++z8w9N1+/8Xvv6s/nvef7cMfN5cy5taS
GGjJfwIZFy0vTUHGKHoCefG9FLRRxJYgv0TJQ6oDIb/6CSnzbiD+PPbT/v63
6gEO2HmoaeY8JJrVn9Q+ZiI2PGpoxlDTeV6htNvfg384f2u6Ww///J8k793+
8//8toUm9kJm4LqS0mi1kFmTv6nolVkbGRvZDLyi2Qy5HsT5jbYAeat1wAqT
Ym72CpTWAmHIQyX/qBPBNweDn2QLbbwERl0xhE/b7EjstEUKNoQKg2TNkowV
KbkJqmx3ClY5JVOEbtYNWB3kHfpkXowhIgncooolkL2a3qIIk1GChkCZw3vp
gaZwC2F/Qdnn6Lr5BXAX+Acs8OBusFuvrCE7RKBbw+llF7RKkkHMRF04AVuv
H/REqzVCdeJrhQbESVOkNrQCPr+QrA/tXgwEBHlYr9DVDFibdeifVGlXKARN
uWVQ9Z6M4B/SFkeg1scRerI4cY9pHEOjuFqipVQUaSaYO6nLs6JzLFNY0UvG
GAPHvJQTnEGkFbMVajTvirwL8HcLoCaF3VitdrVMYJEo6QVXCEJQ04VK+z0h
jgvshCnA3cA200uwc/mg1XoVZhhK1lV05TuvqDouYH4yVBO1IWJs9K4nDtlW
4lfoYsFgAvAZriR1XRykaaS0d/eEqjrTev+1nIIPxH7q9sHJ2es26MArcFa3
EBZKftnCvoEtDICMIwldDjo1GiA91SyQ90Zqtex8Oc6eeAVMDm5wt0i68KXr
J3eUkRoKYO0cR4t/M1NE6LCzUlWWDJrMrqVbbISPMt3K0cpWjljYoCkwzyBI
EDMjHZS5teaGfUzZ3KGbyzCSpkYQPxle64mw6jCOT1N3wQueiDF4T+BxBbnp
iCat5Y6jJw3+uBfLZJ5Hiw68i2AecFoxKogodGeBCSiqAWc5Zl4BFoDaw/fg
JYIglZ4q2J15FKDimkBdyQ1NdMUR52owoBgqdTlU6hLnQ0cI4hCVo3qT/wdr
L/sZchIrPrCynkCVDl9V/GKxDeqvzTMN/iWIol+wT5nNY5jz1Ms0bcQESSWV
bzjzEOKBXqIeDYEYOjBarmfsoYD1mBQyq/KzK5iGdywVYr1HCo0btLBS7VJs
lVNqW53eFvliVVukBA+p1SBxmeQRgjJM7QhTB5gdNFzl8yMwVGAr49JvRXen
Xr81wGovBVOIWLvsokOev0qYIHSh3WZyisYTgXEKmi8tHm71wyjJZXP/CvIM
dEBX+/I1qLDJovlTaDswwEGA0HTpyfbEj+CcAcVUzJT4EOmhP4YkyDJjEsNc
DQHiifl0FZGwxZh7YxVKJYn5Ek60ZQRsHlPZMXUNg+6wfFV4ceaBqQaWK6Tj
quTKgar4CDZyQm5MXv3MJqTvZeAIQINg6DWTgbE3VAcLiHr3+Ox6n17DL08h
kAgyCiu8WQgqE2hrRNhtyffQKc7J/bZYqidINLzg2gPOmRLgo2pYQhgxyZIZ
vXAbCFXIHxbofCc3rCguwYsBuhn/CA0nRWkqBq5U/ieyawggAf3jXBndcIYG
RPkp6mP9oeFJjMLAteBYkuPLAJdNTIvUXYuYp+CyoA7u4IqKnud5iiY1V7F2
lbpCidZkjhB2R836CorTGCQTJggRb6FAqFptQEzNYdGEnV20VsiA1BHg7VNt
BVwFmgsIBKrwRcX74UjU+BvohCgfBOYM21V1dXUYSjGA8WAOJdkBDgFAxCrG
a+il3hiBOYgp3sS+XO99aaXpGXXq1RSqciXzJotgmXD7pcZsdEsq3Cem6Wiw
A/wJIOo14ljzvERdYP5mEI1mLJGx8tlQPFhqKwVQVFHZ4TQBS1T0fhwo6In7
V+psZGRgt0PpBRf8K5ZNE/AdF2B+I6lEiOdhoQUkYOKDdkEIhUeQolUHvyud
M1YB5uqXucQQDFXUuDQJikIOGkqMwpyusCpUtHoeQzUGFoFAgkHBJUn7fU8c
TzagPbrlwOQhCMNYkkRWlXaOPog3JaiRRathShTQlkwavsYFI2RhkKc0QU4y
JlS+T0O1RKPxNqd3ajLyuU9aBaYnk0UWKuuWokEsiAO+B6ftmierxL65YuXc
4cBQ2N9DFxDU8xAG9q+6yWRiOYuoDpsJpRpGrCopmU+NtEuOSGUCOhVoRb4v
yLe1CFTKJUQsP4jffpv0f/8dmvhtAPo5nMbfbPkS9c0WdN2/TLJvtiZ9+D0j
QLyLS/LfbHm5H4ZdeLbFKxLfbDVWvvV7q/Wvf/2r1RI7ov7Tb3i22/BsDz/v
w6s9sS+eiKfimXguXtzlWevr7gf+r3VrdYjd5YuXh/22eWa9P5HxFIRwe79t
fXP7wH2o/ViUb/65PXyIPrQMAehnAOQeLzBIY3q0LAK4r/f5XdnNQYurOByI
l+Ab7HS06nHMZYWhFT+R94gOJq/NOIp2iduuJIztRpT4IIuNCi6TWkkHpM38
kq6xFbKT9uqs13W4HDQmfardeI++JTeBMjaUPjV2W74Pm7EK8jEvE/TVYYgZ
ritTkByjIvTJhzeLTNpiVxQTdlg50raWMNoSNAp0FnXMZJ4pBwMs+4hc1e7x
oThljEoHbUpJTuZRBS6zSMVE4ggdPsGFqgADtlyhXwr1QqLJgVpOKxvsfkuB
aQeTJshTbEPbYK0szN+KPjIGARKFMKsoEOcUzAmYRv9ShTVkQDNlHGgJbHQh
Xo1OebynGC7J2EOvBWxELWJV7kxl4sGqgTmTsRuZUTHB6IvlHeFk3nhsiq/i
5Eb7yLltxyj+KRDf9K6BZ5BCasFB9jRQq7kVSXoFHkVXh4E4IWE+K3nCq3sc
XtXn8OqRJHuJ5NzV3t0hQGO0Bdi9sRLFHsZzwnpM19DohknQKG0KOR8jh+Wy
UIOI5U1DCa/AXAkSxR8JPqJPTDzTpCgqTMIlbP2kTb0OoajKHi+8vLZCXjNY
9P61GwZRiAw5oGBgLGHflz3ehXKE1dMj++mR9bSMfIFXvVL0wTmJC5w9oK9F
arXYjj7MZtPGMDvDCbwi7IcZaA7M6fM59mHfU7F6I4+rHvKIGCV0VpwbOk5R
rUqBUMYhVyGTxv3KGvJ5EEhc9ZlKjNLgeZR4AQpgmhTse8HLCFiKpjsBp9kD
3ZWS2lFeYs5ykfdMmsHqwTiLFMNh/hgDE+sT9tmTmXZRw6z0xrcxuUkh1dCW
jY60eUkD9TEyCqaFEYKSMMwA3iSIg0QV5IyB4luMX9+m5PZrRJSWPe36Ddz7
uD7CAKYgUPaFEQvSScujCmTDWC1AuxOi5ALRBTAVsXJcSQ61MoPOjjhFATFV
b2mf8pBXCC0mqnEPxAVgTuaY7kD8Y5Z7SYyRU6PIeP2pch30MHomgEUftjS5
Fwr+otQTcjoqAYfVCw48bhiPdKCzug8C/s4ElyTIhyF814bgCHv5IKFl8AYr
56AnZv8gb9BzdYbBMtyfU+6AseBhSuk7Vl2N+lHXTBq/MNrDuDoVpKJTAvOW
t6P0JLVFvH8FjE7hl4exFK6V0woCsIeeTRUpui6PUoDlYnOez2c6oG5qmB2r
nDwrtn0M0JMs2Yi3WhNK1fpCZrlf5H1QS/SWrJIR6kxyNWHRs/KZSkY6Iki0
amHD2KjfPCzmjKMOaJEbuV+DMoynGnBAEBsVSD8qyRNJTK9BHhTrKETN5uYr
WKJsZyHonBbbL0aoSMMGHeKkVEuaQda4ds9aAqaEL5y28T+B9B2Nd1yHagmh
A/oNlZ2PTD/TrDiP0V0yGgj+JfDMl22d0vEhtq7UAq8yb4a9o2W7VmuEaly9
0g4n5hcpf1pPUSNgjKwxk0hhdN48syhVlrB1lSVPTlgDn9Zdp+YKWf5tTB9z
GEssuS651RoeK9cZPHBrPdZxBhCJQzRAJfcYomHmvPaYke8RZYcPCWyf0Hvw
lK8Z8Skli9sYqPhOVUffUJ3oC8B78VvLxN/9p23xDYSNLSvkhmf0N39z5i3Q
CRDbvV6v3frdVKt7V6vZrriPFVXqHRmibD/dpSepFxD9tndNZ5a0TeO6oA0N
SLkEuLrAXLQAnZPJQiteohDRFWjGzQ9ICcFHXQylQQAwpYlch0JOpcpdcJOW
Iu43MCRH38piceUpdw3XlfV4BuJAPN3tjsPC1BoCY/gl2G/5E4YIVGspcFCh
M/aBk+2GNva334r+779TXndeGa1KACJwnjSV8225mAVDKvFyDalD1RVs5La2
YnrrLonetm4HXetn4P7Z+AQeQTsklPV2yifUjtMZ+KoU3bt85UQQG3/Fa2h3
7SElkpRlHrsEXfVVeuev2L24Ww+X45NFvwpDMh+SOCvEAqFIVO7oyA4tR/Zc
mRHUVLitZ2FF9+yMYlhf4hzgdzgJI9V4lKycGxjgYkU4ISD4WkFCKlWSrJJX
kC0LM+NSlb3juAjt94R88Nz13bUPGUnM26i22hM0EvsDGgsVl2ZxJSy90GVu
vrVeILaZT0wO63hRz5cwfo1Vkhw6ysvT0S/nVKu4v8E622E2Zvm42sZBDZIl
ljcsTHqYSs3HBFjX3V0xbFrRNJxQJrCUKSv1j9llhMmcRzzVCqq0iMhzcR16
VLe1lLuWCiVd08+PrqXrxOkhI/JyT5WzvP1qdNrmpfhrSlLVuRn6o9Epvn0E
+lWtkqtyJ2F8xc6LeTNSwnZQ8L4ZmTNhjmOYhdziVlUxmQ8SPoyPVb20DMvo
y9jOTMRVJdUQxqcUvuuGuQ6qLjLdMm+1DvBMt6CCN8vfChlT5K79es5rRFnH
PmuXzEMfW808NopzpFdDa+U6qotlxtaK3jEwahLbxhJ8sZ7yVP5CMG4fHAO9
3dDZ3wR2TJFxe4SJfI9HRZK2cXVgxSRBZejuYY30UaclVv9YxZN0belDb5ae
QRD+JvdDFevnaz86DiL5fRIR0NgRdymdaSLt4m4FEJFJOJ2jSsc+5OtJQchN
iTXkdh2qCq5/b6AABpPnsLbyM49WLv82D/0jezli/QgvMs+/wu9IenUX9gdC
i5PCBDANYNPeHCIyhW7T+uZNUZqPO5XO1hYfgZmzPaofOTOEerbu26FO+DuU
BUzYUekDMKEEiw0qsEY5abXoX5SoUy+eexFJgH66Wz5NUv1wj4XPKbjvfP4z
ehs/L5ts/c0Tq57Nvnha+6JJtnTpZxuV/hk3gK9r+LmuCqmAtGT83yXhi4GG
6M5lkS2oyM9HuKovSzLvDIQR1NpLmATjjzeX2B1UmKtWAmbH0QZlAex3JaO6
+5KQoQorwGQiJcpiP/8AXQrM+ycs+D8Pz38+jq+dV0/LVwc+2CHz4lm1ziEq
Fdx7ZIo8rxZ5hWuZ3G9XyJu7/YIDOySN4d+d8pliAZd65/M4JlWhyve5PO4/
khlEK+bFblnRaT613wDB8WkpiPOZEZVdICVJNnzzg1vhk/KNefbUmn/7+bOB
E3HZr4BohMvRMyDUYYn9KYPNFjpXKKIbjyuyNuXNsmO0Ov9id+P8iybXq8zC
sH6+tsLar/+s/m3ZT2+1Ln97Jm6xxNccuy2pAx/cVkvUftwSX3e/XVMH/kVz
9aMHPqe47db68TX21GrA7qmpfGkrbmdv3d8bSvywtER1LHZPb8uxIAtbYyGq
W3XUx2KV+Lo+lj+7rdw6vWvqqfV4yVhuV8+L/f8zBby782I6+7F7yvWbrn5d
KWGa//aWVLVFcs7HKX/KOqwea6nRYZNKxndxSxWcY+Ig+vK42UTr/QHvJSEL
tk3wPcLyeZu3vkidk3bpXfO2F4wpI9o0Wc/94IRS2lJSZmlmcoqLiJnanO6i
9hyHgtWYmwUr1S/VJYjznu7oTvXKbpNR5b7H89kYSuLn4UwNPadDLQhJKCjX
sZJu07gJ0sAklNWgM3IVqmK1feq9t5qfee/D2Xy2qhucmLemC3cnHsRCtHFp
mtBGWHCJdVBJjEQKfDmB9SiQxE964BoaqbdZgpCfEoU3Yas3wzM19GhrpIOo
+wb1By3RUpheFnHWC0w6tv39sjRIXsC3CJvJSHqVFUOzAR5jSzqSYxVljKbj
4SLDeGAB3wPBDdFcBtR6/mNRqcRgE5VxkfzN3m3wqSlm7NzGFEMaby6vBtZp
ZhiSVCeloIJt+pceHg4hM9we5FMH3OVRXNhg58boQ4Ux0HYo1I14nlIh3/x1
gFt2kgRIFqvUp5x0KZCmj2jp0q7Hot5BexjYqxNM7/uANnS99fU2mL04uYlk
MGWVUuai1MhpY37MldAGefE99rVp+slTG7DvGBp+UMChNgpmIujdDS3BWc1u
U/IRLYRmrJChpa1ydFttEgaG3DBZWZsaZmZGpVnQqpjYnNJmSrh6zIuH81xm
2xquUEkrWLdzNJXzlc6s1yjccVwRgU5VZph1cMuIT2nO2zNgnWzRKVP38fyV
Nh8QFJsNps6SEbMKqnhCcuOF3hFUWdavGHGVBWoMMjKu+IosA0nbN7TQ95Xm
M/2n5m39t5HOb3CT/rFJSjSjJfwO5o2OPMCd6WHsJzNzIoe9AZHRUvicBgBh
ylI6WSxHZC5zmzBjzEIP1MRvq7COZzAuY3n3/V7bTp1lxlJ0Obbg8DVnIEiG
ab5iHyi3rWYZzJcfaf4n9ccf0n5hzDorFClxXMoRVRNbQinuEHbbpIc1wqAf
P2+rYjTr6gSfsMqfPINLibkaWHH7sU+k3hCTcT998sCzIBvmYIiWVdKpMb/K
LPkY86V9A5Mi1AjellC1pbkvzt+qlRjL7tCZNLgU7+L0mD1GWwvttNJyShXh
NgCvNPk5DWCjT1biXbq+Z6q+RiTJSOZeu75qVVB+x56B+6tMwT6Q2lmT69UP
JGCaMUeRTUqsHrMTMpPgnAe04MgFsbUUjxzDA9bqn+HUgDNPRxaQyfGTVJrU
AJ12BQM4AO3L+V82R+fiRbe/2xH9J91dEERjg2uTVSap84Yh5itdjosoN9ym
g7K1OlLV5naZMsbDiIAvVUZKY34YJypQ1hSeU6J0Tl5qzNwMrd8Re91n7SbF
oju0VrfUldhSDRBkSZo39ZmZzDiodCoSjtiYEEsbbKAJdCt1RcAHe1Vq4Ve6
DiyzXDHgfNep0diYEROHPC8+gDyrdFx17C6+qc8H0+q0cIZMn4Yr1LMaYpkd
aaloXHsN4zlHuZQ0HKusr1otdLAW7/LTrRmPLSPfxKrczAOMepEvZctJw2ib
Kd8H88r7uHVlGm9QQrZkWlTyQX0TDyUe102V0ZMsJ3RSlDI4q3mrbnQsH4zU
Ds1NAyJfGeh+uzllFb0z9k1p44dagG1ILV1N7MZeuesAlQ41eQXw9T8pLaSJ
4e/fueqYCcORQWmsnqJvoxcjmvrlX0r/qiJElqWnHeFsp/QCo9lV2lS+yTNo
4rIVWmsbYsGMFyjapQprLuuqQl2uog2UPLve0P0ErnGkrw5ORn/wULW94/1J
lRDyk8nxgVWLgUj2BYRQlN+AFJtP8bxEstNLWJg3Imv+fb4pz1Krdda80OCq
IvPSaVptb1b61JuYISQZk6Qyjx/ZnJxvpEbq5KLM+DUkW8XZzig/wBPazD+Z
1Bjd2cRmDidayhbGndtZ7rB8ZEE2tsYVZpvFsGIfaJU1ctu2adNhtHZnuT5w
XtXxNX7tqSPaatTXAGnJRw78jlFZnMwQZuKjt8UklFGgwTQ6AkMl2TO16x8w
gtphRevaR+zFXG144hM5INL8D3babsJc0jcMOW/htnt8vcU9tXOZxSWtebNK
sRmBARiHp0yZgJJO8vLAHP3RimhgW2d+RYu21lIrMmBWm9S4rhPdDUyNex2N
DvNSsOZg2XEe9Q6VQBo3JP547L426FmjKsLY16dqLsNJQCX2O3WSQ8yMmxry
esQceDM+6O9e0Mem+kmlgS/bZAsF9EHiLksp77b1oQaw9SHa/P4umdFbVjjW
rLccbfUBfLLpjHwcu/fZCsNH4P9srW/YjB94LvRUAjTPO6K/0+334Z89+O9F
R+zudVq7hEUtnY1wsoTWttPXyIcNfN7AiuFaj/ITMPn/rvn/XBC5dcGBicNX
GeZa4rYiSUOcoq0xq36l5oc452sZwDoVHdkr1SkTbt834ZIHhBFX67R7qYIH
ABLXRG7bRHcnbNOS/ekwQG9FyLYhWlZBlww2tSE4uAIAvKtpXx2SVJTepgGP
OSerCb9QxKvAGPjmMoEIw+C9Hw3HoCV+A2aUy8GqNtznHBb2pvul03UHgNOp
QkObjZIvJpE35cnZBN5a2rcHhTmXd2fUrOMpSuSkNN56V63ww0BOsxVnNdq5
IQh4b7jzYyGcYtsp1P4DEc8Hxj5WqoIGHfAHQ5l0cY3YsprZMquVppLNhK2y
CaAicCuc4I1sYI1F2nfT5MvBpeWOzD081TJq/+RB+wpQUbuKnx+keIfpvL9l
vg+QqOaqKlgUdcfdxuQWd18QyXwdf7eiLkf08UF5RqzWADLKZb0r0AnsQLW+
SvsN/syyxjdwiT8//NQqYEOpIeVqfn4wqhtfbQhz6rm/F/h6J/v2Bey8J9i5
8Wrf/Zf7vqCdG6OdX7j93tDmamRTrEE2Py/KJ7H8zGjPx1OorTzLkwidZPv6
nhwdRHC+5V1hSrOtxoqfVmGTONAwz+fLaliTl0XzQ6f11NHEP4pdNspS3mQC
hVBOtkkBd4j1/LMjlvGL/w00G0+O49bWMqF3dKq+vjBm5XQs9dMs3wzb0qcM
UGPB5+ZyfY6zVAUPFIpo44fO8QQlcNbuCANcNxxSUAEgnrVtV65Dh2Hh5rfG
s9EJ8kYgbYqXqOAFe3Qc5JIv+HRI6hzerVr2pTzqw75ZBqYijFbF5wThVI59
MKeLKVugYU065X67CnaWMCfrIXOwUgPBm9Eal1hLZKNyEuy98qA/ehbZ6l0+
wIT6/qhl08F3/1L8qq5mQadeIee0n9QvYmKT6hm1pBxyW/+b+jWlV68NLYdM
G3BVGvtaEHYZylEirFifV0UPnHsL6XinpTmYng9E0WdjN+IYd4EVrI/N+kgJ
vrC9LnRWkdUJkNPqEGhSCr1n3qSbfCzgwvTKVRXAaVsas9hqBi06CrXAoga4
cG5bsvO7/2gY417IxedmCv8Ar+UuhrA0FDwjnPqm7l0oz9wdE3mjUJ9s6vEu
YCbRUrjX6JpyqWl3p42XjVeOosJzcByvqDzpmSFV92oi7CoeTI6pruMFnUu8
yQauDmtyzzmi24wft09T45kSUadcoyvN98aqvmg6VQSPjQfe/mpOAu9ope+c
A2QkYI9sIN/5Xe6FdQ7cof7xgcvWiZzVjWfr/X7RIFefLkb6LITnvs7kA4J3
fxySsekAN8NrXnREv99FrGZ3ZwOcxrrTK7P2CvDR8UMMbBoP4aT3XxhzM6TH
HMexatOohfW454s4PK22v+a1bfUl1FN6/FoFmfbvkZFW97X5NuUk25ipKuf2
b5ZF9nB4zqZMet/9pBUIqEYvtRZgoKEHoNsXkdtgzaAO/rhR7o7ZZarOaGqI
izaKg1fOW0WZfv4o0Wc8o8vyT5qP4KxMd399SLNk8d/BMdy2yu5XNr02qVwC
DNm9Xgp81dPnVDrOPbLJ1O4x6JHuTcMSZUx7blGVZXSg1KXUOJcVcFrIUTWc
1TehKS2FProNTa1KuKODJdhUNbera3+YDKTyVC665jaimzL42qes5jpq+7fi
mJQvIvsBItto4SrOuXsOq+Wsf/be+rrRs4S4iKA+rNbCBtv66kAXHSjv2LHP
CeiZ8/cr2DTFwzieFKQ04AS4pth7Q8TnizfykMl4d0WX12B+zlHIFgR4JwzQ
PTbZwgS/gIKfgHvMxfLYgrWOhI6Aui/RSWfcFK/zPgJip1JLl+ggjbstcQRw
tbwZk3ND0r023rratJG41LCb1PIp9d3/zwy7mateGj77AHU9O09X6BrHHXeW
fJZ3zhxAvnneE+JouyWO9mwDHK3CMpQWgEe6fwHQPhBAK8+PdxA0ab2w0HWT
PkWHkL5X57vRHVIdvvKowxPVcdcJyxM/ed+dzq5iyK1+kuUqyK3SsRXnZ5aQ
m7vNLjZAW3uD/aHVtKEHxI4+ZZ5VXViXZlx9RHX+byx9b2JMrvDyJNapJ1W4
M9drkWrbRU6Xebux3utiYt1MBr4ESCXjDrxMpy88qp/TnmYSz61WR0o6VsU9
IzgIc0VxrlVJ7hosUAGAJSR4Xw/3C8T3MH7DSiivMlv3QvQswE65EdibKqo3
jyME27B2KwNFc5GbgAKdP/LwBHd8U/N96j2hJR1LIijd4yF7c7A+p84si/J6
U4nYddgZ55NRm0E5tcDOKW9kHA3mV8Ml123DbTfc/ldX+foGWb2Q38D6vK1x
yd2aqzbb1sc3+v7g5MQaosrYK2+3dKN5DY5uiulUon9o2xwD4mRjVJ2epk2/
Js1EJxpYionJquEEIGQuaQNRWHDwFmg/p3SAl6UYLQ0k9XS4AZ+BlJGG+u76
oLzrUQWxm8Z6DbDWsha+AFiNmvmj47cGmrVSjJ60m/JzX1WOSFwKyj8sxGtY
+SNO2MNGxSYQXh8HOxvHO5oTVloKs2t12fpVNX7ZgCFsJ093v+lIA9V99xSI
5gW3z29k5YG37oAZ1QQOCCI65hwHF8zpxpIlKZYbRyxuKKeq+fdQXH/IBjcb
6Ol+QObrl5Sph0J89A0sdCkx0JToCG4dPW+1fjp/NXy+u9d/V7kbMbeLGS1h
bb/oCb6GEp6wieErmXB+JN2FUOoG+7ZryvpuqA4zwalN8s65z1ytczM20sDy
RjGS1XUjyG6VRFhKX74htk9GZ+YqDr3/o41F3qbg0tbun8fi8MYtjMrqbHie
Fks+YA49l+j6t90bbzRwxm5VJoFR6JZppBN+GoUT6S/8iG73ga/oNgp1Tg5e
TbmIfRhnrO8G0muWOU3wqMikNxOn86gIwbd8Tzd68lr8ZCIzpCsVmFkF6Hoe
c3cDzME1Llt4ZaI08YrqNp8LQ3XQyThhsQBpQJZWd6sfxyDZXqCCrwgvf3Ou
xWj6qnRWKA3bV1WZy61SL6MzubhhtDi81EpXniNp7MnGA4JzzC+mRbgQh40U
VO3qy+iANztA91wvAdEdZlyhmS19L9llOEXtZnrunAT0SLyWdPGnOA2nfNOS
onipNHJrk0QW+gVeBQ9qgi+CElhRhILA1eB19T17i9JM1yvoFiI7NgtgZOEk
xInFqvC2FadZTj+J84k++CaWN5WGFOBL60xAJp0qkEyUKNPF9T7Mo76Rnbuj
LkTT97BlSZFA9AMzA5QKSS2CDE6kV4Ct7nDP+NakoXWHH3RJ6UPTKTNYmn6r
bH6ZzKOAiKiGvajUBoKka/GCAHeYEWdDdTh7dCPJUtLBVCfAMb9Ki2Pc2jUA
x3L2Cik9ZIbh6f4TDFeRX3GRlh4W45yibRCtOZo/xcig6G4kmCC19QW7lEkn
XFQ71hQrZrp65dwpWK+8ao8EwSOLioXxWjWc/xkII522tdDcpmQYhcfzsyRn
U2j6VVDZKTQZE/5ihHEOITuQKRcrx9zRQotzrt/qyknYqaP6Ccwc3wDpmcJa
x1MHHflmPSeBYVEWYQ5wlTXTF16bF77zglQYUZJvu9NbrsB3Rav3Ymdn5x1r
dX1M08XJiNzO/NK7ouvUVKzvo/OpOEJ/238HcuTE8iqCJ8UuxU73/OJCnL4d
XZQhPzRWhN1MppFHezxAE8nc3Q8GDYwUuz7HyV3RGu7f0yPGKwlhMukeQ1eH
XwzPumOy1GTJt6k1uvhPD+bJ/v7OuzYjz6zEgOYJ7e6wTS1OwfHB64Ma+R89
AqM3VVersxoxIeKxEjmFOIGpIut0YS+JC/Cr1PGLqKoyuy49M6FbTzLRCDm9
3cKJOyjNSPfEWwBNzrSGem35G9t422i7fHd8mG/pNhfqkNKt1Acr/ssWqW50
z7TiUAs4RkOQM6sV4aDyEt9Vx4/OBCiUgWkCC41S6ZsyA+EQh8ir5HDopd4Y
RBE4/eLkB/DJcTYwbzC/0hcMog1UdIQivGpKskddw0cXi1SCASAQEHdUGg4w
tHZHYbfq5ep6L7xQ91b8QHGicK4Bvnh52Bfus9btoFv9GTQ+gzrtG7x1nfXh
Y8lzSTrbl3brSLpDzVd84/CQlyyV4o5gWLfi+OjiVbWXy2/6LvaqF3pbXbFZ
X9/pXb4etLDyw4F4Cdp4B1TkPKVcTtdTdTJE+H7j/wHAJUrJn70AAA==

-->

</rfc>

