One document matched: draft-ietf-homenet-routing-consensus-call-01.xml

<?xml version="1.0" encoding="us-ascii"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc2629 version 1.0.28 -->

<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC7368 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7368.xml">
<!ENTITY RFC6126 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.6126.xml">
<!ENTITY RFC7557 SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml/reference.RFC.7557.xml">
<!ENTITY I-D.boutier-babel-source-specific SYSTEM "http://xml2rfc.ietf.org/public/rfc/bibxml3/reference.I-D.boutier-babel-source-specific.xml">
]>

<?rfc toc="yes"?>
<?rfc symrefs="yes"?>

<rfc ipr="trust200902" docName="draft-ietf-homenet-routing-consensus-call-01" category="info">

  <front>
    <title>Homenet Routing Consensus Call</title>

    <author initials="R." surname="Bellis" fullname="Ray Bellis">
      <organization abbrev="ISC">Internet Systems Consortium, Inc.</organization>
      <address>
        <postal>
          <street>950 Charter Street</street>
          <city>Redwood City</city>
          <code>CA 94063</code>
          <country>USA</country>
        </postal>
        <phone>+1 640 423 1200</phone>
        <email>ray@isc.org</email>
      </address>
    </author>
    <author initials="W.M." surname="Townsley" fullname="Mark Townsley">
      <organization>Cisco</organization>
      <address>
        <email>mark@townsley.net</email>
      </address>
    </author>

    <date year="2016" month="January"/>

    <area>Internet</area>
    <workgroup>Homenet Working Group</workgroup>
    <keyword>Internet-Draft</keyword>

    <abstract>


<t>In order to support arbitrary network topologies and multi-homing the
IETF Homenet Architecture <xref target="RFC7368"/> requires that a routing protocol
operates inside each home network.  For interoperability reasons it is
necessary for there be a single “mandatory to implement” routing
protocol.  With the Homenet Working Group unable to reach clear
consensus on which protocol that should be the Working Group Chairs
(with the support of the Internet Area Director) declared rough consensus
that the chosen protocol is BABEL <xref target="RFC6126"/>.  This document (not intended
for publication as an RFC) serves as an additional record of that decision.</t>



    </abstract>


  </front>

  <middle>


<section anchor="statement" title="Statement">

<t>On the 27th of October, 2015, the Working Group Chairs and the Internet
Area Director made the following statement to the Homenet Mailing List:</t>

<t><list style='empty'>
  <t>The Chairs believe that there is WG consensus that a single “mandatory to
implement” routing protocol must be chosen. We also believe that further
delaying the direction here has long passed the point of diminishing
returns.</t>
</list></t>

<t><list style='empty'>
  <t>Based on the feedback received in Prague and on the WG mailing list
thereafter, we are therefore declaring rough consensus that BABEL <xref target="RFC6126"/>
shall be the “mandatory to implement” routing protocol for Homenet
routers, albeit only on an Experimental basis at this time.</t>
</list></t>

<t><list style='empty'>
  <t>The aim in making this decision is to allow the non-routing-protocol
aspects of Homenet to move forward in the near term, while allowing time
for additional implementation, experimentation and specification. To
that end, we solicit Experimental Internet Drafts to document
Homenet-specific profiles of any applicable routing solution and to
report results of any relevant experimentation and implementation.</t>
</list></t>

<t><list style='empty'>
  <t>We expect that this decision will be revisited in a future Standards
Track document based on specifications and running code available at
that time.</t>
</list></t>

<t><list style='empty'>
  <t>Vendors looking to ship Homenet routers in the near term should refer to
<xref target="RFC6126"/>, <xref target="RFC7557"/>,
<xref target="I-D.boutier-babel-source-specific"/>, and available open
source implementations thereof for the routing protocol portion of the
Homenet solution space.</t>
</list></t>

</section>
<section anchor="iana-considerations" title="IANA Considerations">

<t>This document has no IANA considerations.</t>

</section>
<section anchor="security-considerations" title="Security Considerations">

<t>This document has no security considerations.</t>

</section>
<section anchor="acknowledgements" title="Acknowledgements">

<t>We wish to thank Terry Manderson (INT Area AD) for his support.</t>

</section>


  </middle>

  <back>


    <references title='Informative References'>

&RFC7368;
&RFC6126;
&RFC7557;
&I-D.boutier-babel-source-specific;


    </references>



  </back>
</rfc>