One document matched: draft-yang-mpls-ff-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
    <!ENTITY rfc2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
    <!ENTITY mplsfastreroutemib SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.ietf-mpls-fastreroute-mib.xml">
]>

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<?rfc strict="yes" ?>
<?rfc comments="yes" ?>
<?rfc inline="yes" ?>
<?rfc editing="no" ?>
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc symrefs="no"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>

<rfc category="std"
     docName="draft-yang-mpls-ff-00.txt"
     ipr="trust200902"
     iprExtract="">

  <front>
    <title abbrev="MPLS-ff Extension">MPLS-ff for Supporting Flow-Based Routing</title>

<!-- NOTE: There is a limit of 5 authors.  One common practice is to
     explicitly create an Authors section at the end of the draft,
     and add remaining authors there.

     For now, to get it to compile, I've commented out Hao and Rich.

     I'm commenting out Hao to avoid including him by mistake without
     approval from Google's lawyers (he can be uncommented later).
     I'm commenting out myself because I don't want to make someone
     else feel bad :)
       - Rich
-->

<!--
    <author fullname="Ye Wang" initials="Y." surname="Wang">
      <organization>Yale University</organization>
      <address>
        <email>ye.wang@yale.edu</email>
      </address>
    </author>
-->

<!--
    <author fullname="Hao Wang" initials="H." surname="Wang">
      <organization>Google</organization>
      <address>
        <email>wanghao@google.com</email>
      </address>
    </author>
-->

<!--
    <author fullname="Ajay Mahimkar" initials="A." surname="Mahimkar">
      <organization>University of Texas at Austin</organization>
      <address>
        <email>mahimkar@cs.utexas.edu</email>
      </address>
    </author>
-->

<!--
    <author fullname="Richard Alimi" initials="R." surname="Alimi">
      <organization>Yale University</organization>
      <address>
        <email>richard.alimi@yale.edu</email>
      </address>
    </author>
-->

    <author fullname="Lili Qiu" initials="L." surname="Qiu">
      <organization>University of Texas at Austin</organization>
      <address>
        <email>lili@cs.utexas.edu</email>
      </address>
    </author>

    <author fullname="Y. Richard Yang" initials="Y." surname="Yang">
      <organization>Yale University</organization>
      <address>
        <email>yry@cs.yale.edu</email>
      </address>
    </author>

    <author fullname="Yin Zhang" initials="Y." surname="Zhang">
      <organization>University of Texas at Austin</organization>
      <address>
        <email>yzhang@cs.utexas.edu</email>
      </address>
    </author>

    <date day="5" month="July" year="2010" />

    <area>Routing Area</area>
    <workgroup>MPLS WG</workgroup>

    <?rfc include="abstract" ?>

    <note title="Requirements Language">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in <xref
      target="RFC2119">RFC 2119</xref>.</t>
    </note>

  </front>

  <middle>
      <?rfc include="introduction" ?>
      <?rfc include="data-plane" ?>
      <?rfc include="control-plane" ?>
      <?rfc include="use-cases" ?>
      <?rfc include="iana" ?>
      <?rfc include="security" ?>
  </middle>

  <back>

    <references title="Normative References">
      &rfc2119;
    </references>

    <references title="Informative References">
      &mplsfastreroutemib;
      <reference anchor="R3">
        <front>
          <title>R3: Resilient Routing Reconfiguration</title>
          <author>
            <organization>Y. Wang, H. Wang, A. Mahimkar, R. Alimi, Y. Zhang, L. Qiu, Y.R. Yang.</organization>
          </author>
          <date year="In SIGCOMM 2010; available at http://cs-www.cs.yale.edu/homes/yry/projects/reinforce/r3-sigcomm10.pdf" />
        </front>
      </reference>

      <reference anchor="PathGen">
        <front>
          <title>Reliability as an Interdomain Service</title>
          <author>
            <organization>Hao Wang, Yang R. Yang, Paul H. Liu, Jia Wang, Alex Gerber, and Albert Greenberg.</organization>
          </author>
          <date year="In SIGCOMM 2007" />
        </front>
      </reference>

      <reference anchor="COPE">
        <front>
          <title>COPE: Traffic Engineering in Dynamic Networks </title>
          <author>
            <organization>Hao Wang, Haiyong Xie, Lili Qiu, Yang Richard Yang, Yin Zhang, and Albert Greenberg.</organization>
          </author>
          <date year="In SIGCOMM 2006" />
        </front>
      </reference>

      <reference anchor="TeXCP">
        <front>
          <title>Walking the
Tightrope: Responsive yet Stable Traffic Engineering</title>
          <author>
            <organization>S. Kandula, D. Katabi, B. Davie, and A. Charny.</organization>
          </author>
          <date year="In SIGCOMM 2005" />
        </front>
      </reference>

      <reference anchor="FRRChallenges">
        <front>
          <title>Building a highly adaptive, resilient, and scalable MPLS
backbone</title>
          <author>
            <organization>N. So and H. Huang.</organization>
          </author>
          <date year="In MPLS World Congress 2007" />
        </front>
      </reference>


    </references>

    <section title="Acknowledgments" anchor="Acknowledgments">
    
      <t>The proposed design is based on <xref target="R3" />. We
      thank Dave Wang from WANDL for valuable discussions. We thank
      Richard Alimi for creating an XML skeleton for this draft.</t>

    </section>
   
  </back>
</rfc>