<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.koldychev-pce-operational" target="https://datatracker.ietf.org/doc/html/draft-koldychev-pce-operational-01">
   <front>
      <title>PCEP Operational Clarification</title>
      <author initials="M." surname="Koldychev" fullname="Mike Koldychev">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="S." surname="Sivabalan" fullname="Siva Sivabalan">
         <organization>Cisco Systems, Inc.</organization>
      </author>
      <author initials="M. S." surname="Negi" fullname="Mahendra Singh Negi">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="D." surname="Achaval" fullname="Diego Achaval">
         <organization>Nokia</organization>
      </author>
      <author initials="H." surname="Kotni" fullname="Hari Kotni">
         <organization>Juniper Networks, Inc</organization>
      </author>
      <date month="February" day="27" year="2020" />
      <abstract>
	 <t>   This document is meant to provide better clarity about how PCEP
   operates and hence to facilitate better interoperability between
   different equipment vendors.  The content of this document has been
   compiled based on the feedback from several multi-vendor interop
   exercises.  Several constructs are introduced to facilitate this,
   such as the LSP-DB and the ASSO-DB.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-koldychev-pce-operational-01" />
   
</reference>
