<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-pce-inter-layer-ext" target="https://datatracker.ietf.org/doc/html/draft-ietf-pce-inter-layer-ext-12">
   <front>
      <title>Extensions to the Path Computation Element Communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering</title>
      <author initials="E." surname="Oki" fullname="Eiji Oki">
         <organization>University of Electro-Communications</organization>
      </author>
      <author initials="T." surname="Takeda" fullname="Tomonori Takeda">
         <organization>NTT</organization>
      </author>
      <author initials="A." surname="Farrel" fullname="Adrian Farrel">
         <organization>Juniper Networks</organization>
      </author>
      <author initials="F." surname="Zhang" fullname="Fatai Zhang">
         <organization>Huawei Technologies Co., Ltd.</organization>
      </author>
      <date month="January" day="3" year="2017" />
      <abstract>
	 <t>The Path Computation Element (PCE) provides path computation functions in support of traffic engineering in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks.

 MPLS and GMPLS networks may be constructed from layered service networks. It is advantageous for overall network efficiency to provide end-to-end traffic engineering across multiple network layers through a process called inter-layer traffic engineering. PCE is a candidate solution for such requirements.

 The PCE Communication Protocol (PCEP) is designed as a communication protocol between Path Computation Clients (PCCs) and PCEs. This document presents PCEP extensions for inter-layer traffic engineering.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-pce-inter-layer-ext-12" />
   
</reference>
