<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.gao-mpls-teas-rsvpte-state-update" target="https://datatracker.ietf.org/doc/html/draft-gao-mpls-teas-rsvpte-state-update-06">
   <front>
      <title>State-updating mechanism in RSVP-TE for MPLS network</title>
      <author initials="J." surname="Gao" fullname="Jun Gao">
         </author>
      <author initials="J." surname="Dai" fullname="Jinyou Dai">
         </author>
      <date month="June" day="28" year="2023" />
      <abstract>
	 <t>   RSVP-TE has the following advantages: source routing capability,
   and the ability to reserve resources hop by hop along the LSP path.
   The two advantages are used by Deterministic Networking (DetNet)
   to provide DetNet Quality of Service (QoS) in a fully distributed
   control plane utilizing dynamic signaling protocols or in a
   Combined Control Plane (partly centralized, partly distributed).

   RSVP takes a &quot;soft state&quot; approach to manage the reservation
   state in routers and hosts. The use of &#x27;Refresh messages&#x27; to cover
   many possible failures has resulted in a number of operational
   problems.  One problem relates to scaling, another relates to the
   reliability and latency of RSVP Signaling.

   This document describes a number of mechanisms that can be used to
   reduce processing overhead requirements of refresh messages. These
   extension present no backwards compatibility issues.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-gao-mpls-teas-rsvpte-state-update-06" />
   
</reference>
