<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.izh-ccamp-flexe-fwk" target="https://datatracker.ietf.org/doc/html/draft-izh-ccamp-flexe-fwk-00">
   <front>
      <title>GMPLS Routing and Signaling Framework for Flexible Ethernet (FlexE)        </title>
      <author initials="I." surname="Hussain" fullname="Iftekhar Hussain">
         </author>
      <author initials="R." surname="Valiveti" fullname="Radha Valiveti">
         </author>
      <author initials="K." surname="Pithewan" fullname="Khuzema Pithewan">
         </author>
      <author initials="Q." surname="Wang" fullname="Qilei Wang">
         </author>
      <author initials="L." surname="Andersson" fullname="Loa Andersson">
         </author>
      <author initials="F." surname="Zhang" fullname="Fatai Zhang">
         </author>
      <author initials="M." surname="Chen" fullname="Mach Chen">
         </author>
      <author initials="J." surname="Dong" fullname="Jie Dong">
         </author>
      <author initials="Z." surname="Du" fullname="Zongpeng Du">
         </author>
      <author initials="H." surname="Zheng" fullname="Haomian Zheng">
         </author>
      <author initials="X." surname="Zhang" fullname="Xian Zhang">
         </author>
      <author initials="J." surname="Huang" fullname="Jing Huang">
         </author>
      <author initials="Q." surname="Zhong" fullname="Qiwen Zhong">
         </author>
      <date month="October" day="20" year="2016" />
      <abstract>
	 <t>   Traditionally, Ethernet MAC rates were constrained to match the rates
   of the Ethernet PHY(s).  OIF&#x27;s implementation agreement [OIFMLG3] was
   the first step in allowing MAC rates to be different than the PHY
   rates.  OIF has recently approved another implementation agreement
   [OIFFLEXE1] which allows complete decoupling of the MAC data rates
   and the Ethernet PHY(s) that support them.  This includes support for
   (a) MAC rates which are greater than the rate of a single PHY
   (satisfied by bonding of multiple PHY(s)), (b) MAC rates which are
   less than the rate of a PHY (sub-rate), (c) support of multiple FlexE
   client signals carried over a single PHY, or over a collection of
   bonded PHY(s).  The FlexE SHIM functions which bond multipe Ethernet
   PHY(s) to form a large &quot;pipe&quot; view the connectivity between two FlexE
   aware devices as a collection of multiple point-to-point links (one
   link per Ethernet PHY).  These logical point-to-point links can
   either be direct links (without an intervening transport network), or
   realized via a Optical transport network.  This draft catalogs the
   usecases that capture the FlexE deployment scenarios -- including the
   cases that include/exclude OTNs.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-izh-ccamp-flexe-fwk-00" />
   
</reference>
