<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.xu-ospf-mpls-elc" target="https://datatracker.ietf.org/doc/html/draft-xu-ospf-mpls-elc-01">
   <front>
      <title>Signaling Entropy Label Capability Using OSPF</title>
      <author initials="X." surname="Xu" fullname="Xiaohu Xu">
         <organization>Huawei</organization>
      </author>
      <author initials="S." surname="Kini" fullname="Sriganesh Kini">
         <organization>Ericsson</organization>
      </author>
      <author initials="S." surname="Sivabalan" fullname="Siva Sivabalan">
         <organization>Cisco</organization>
      </author>
      <author initials="C." surname="Filsfils" fullname="Clarence Filsfils">
         <organization>Cisco</organization>
      </author>
      <author initials="S." surname="Litkowski" fullname="Stephane Litkowski">
         <organization>Orange</organization>
      </author>
      <date month="October" day="10" year="2014" />
      <abstract>
	 <t>   Multi Protocol Label Switching (MPLS) has defined a mechanism to load
   balance traffic flows using Entropy Labels (EL).  An ingress LSR
   cannot insert ELs for packets going into a given tunnel unless an
   egress LSR has indicated via signaling that it can process ELs on
   that tunnel.  This draft defines a mechanism to signal that
   capability using OSPF.  This mechanism is useful when the label
   advertisement is also done via OSPF.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-xu-ospf-mpls-elc-01" />
   
</reference>
