<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pce-pcep-bfd-parameters" target="https://datatracker.ietf.org/doc/html/draft-ietf-pce-pcep-bfd-parameters-00">
   <front>
      <title>PCEP Extensions to support BFD parameters</title>
      <author initials="O." surname="Bachar" fullname="Orly Bachar">
         <organization>Ribbon Communications</organization>
      </author>
      <author initials="M." surname="Fizgeer" fullname="Marina Fizgeer">
         <organization>Ribbon Communications</organization>
      </author>
      <date month="February" day="11" year="2025" />
      <abstract>
	 <t>   This document proposes extension to PCEP to configure LSP parameters.
   Some of LSP parameters are needed to configure S-BFD for candidate
   paths.  Each candidate path is identified in PCEP by its uniquely
   assigned PLSP-ID.  The mechanism proposed in this document is
   applicable to to all path setup types.  The need for these
   definitions first appeared for Segment Routing path setup type, both
   MPLS and IPv6 data planes of SR.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pce-pcep-bfd-parameters-00" />
   
</reference>
