draft-lamparter-homenet-isis-profile.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc strict="yes" ?>
<?rfc toc="yes"?>
<?rfc tocdepth="4"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no" ?>
<rfc category="std" docName="draft-lamparter-homenet-isis-profile-02" ipr="trust200902">
  <front>
    <title abbrev="Homenet IS-IS Profile"
                  >Homenet IS-IS Profile</title>
    <author fullname="David Lamparter" initials="D." surname="Lamparter">
      <organization>NetDEF</organization>
      <address>
        <postal>
          <street/>
          <code>04229</code>
          <city>Leipzig</city>
          <country>Germany</country>
        </postal>
        <email>david@opensourcerouting.org</email>
      </address>
    </author>

    <date day="17" month="April" year="2016" />

    <area>Internet Engineering Task Force</area>

    <workgroup>Homenet Working Group</workgroup>
    <keyword>Homenet IS-IS Profile Requirements References</keyword>

    <abstract>
      <t>
        This (pointer) document describes the neccessary bits and pieces of
        IS-IS that a homenet targeted implementation would need to implement.
      </t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>Homenet, as seen by the IETF Homenet working group, operates as a
        set of IPv6 routers performing source/destination based routing.  Since
        an arbitrary number of routers in an arbitrary dynamic topology is to
        be supported, a dynamic routing protocol is needed.  This document
        outlines how to apply IS-IS for this.</t>

      <section 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"></xref>.</t>
      </section>
    </section>

    <?rfc needLines="5" ?>

    <section anchor="specs" title="Required specifications">
      <t>The following (parts of) specifications MUST be implemented for a
        homenet IS-IS router:</t>

      <t>Parts of <xref target="IS-IS">ISO 10589-2002:</xref>
        <list style="symbols">
          <t>Section 6.1, Level 1 Intermediate System</t>
          <t>Section 6.2, bullet a) - broadcast subnetworks</t>
          <t>Section 6, remainder (6.3 - 6.8.4)</t>
          <t>Section 7, Level 1 IS function only
            <list style="symbols">
              <t>exclude Section 7.2.2 (replaced by wide metrics)</t>
              <t>exclude Section 7.2.9 (Level 2 interactions)</t>
              <t>exclude Section 7.2.10 (Partition repair)</t>
              <t>exclude Section 7.4 (Forwarding process), replaced by
                IPv6 forwarder behavior</t>
            </list>
          </t>
          <t>Sections 8.2 and 8.4</t>
          <t>Section 9, excluding PDU types specific to Level 2 operation</t>
          <t>Sections 10.1 and 10.2</t>
        </list>

        Generally speaking, a homenet IS-IS implementation needs to operate in
        a network consisting purely of Level 1 Intermediate Systems.
      </t>

      <t>The following updates to the IS-IS specification:
        <list style="symbols">
          <t><xref target="RFC5120"/>, M-ISIS: Multitopology Routing</t>
          <t><xref target="RFC5303"/>, IS-IS 3-way Adjacency TLV</t>
          <t><xref target="RFC5305"/>, IS-IS Extensions for Traffic Engineering
            <list style="symbols">
              <t>wide metrics and IP prefix encoding</t>
              <t>Sub-TLVs 3, 9, 10, 11, 18 not required</t>
            </list>
          </t>
          <t><xref target="RFC5308"/>, Routing IPv6 with IS-IS</t>
          <t><xref target="I-D.liu-isis-auto-conf"/>, IS-IS Autoconfiguration</t>
          <t><xref target="I-D.baker-ipv6-isis-dst-src-routing"/>, IS-IS IPv6 Source/Destination Routing</t>
          <t><xref target="I-D.lamparter-isis-p2mp"/>, IS-IS Point to Multipoint operation</t>
        </list>
      </t>
      <t>And, finally, IPv6 source/destination routing behavior as specified in
        <xref target="I-D.ietf-rtgwg-dst-src-routing"/>.</t>
    </section>

    <section anchor="parameters" title="Parameter choices">
      <t>Most configuration parameters are specified in
        <xref target="I-D.liu-isis-auto-conf"/> as part of IS-IS autoconfiguration.
      </t>
      <t>Homenet uses the following additional parameter choices:
        <list style="symbols">
          <t>IPv6 is routed in M-ISIS topology with MTID #2.</t>
          <t>IPv4, if supported, is routed in the base topology (MTID #0).</t>
        </list>
      </t>
    </section>

    <section anchor="ipv4" title="Optional additions for IPv4 operation">
      <t>Supporting IPv4 for backwards compatibility requires implementation
        of <xref target="RFC1195"/>.</t>
    </section>

    <section anchor="Security" title="Security and Privacy Considerations">
      <t>This document has no independent security or privacy concerns.  Those
        in the referenced documents apply.</t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>Juliusz Chroboczek pointed out the need for this document.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <reference anchor="IS-IS">
        <front>
          <!--   [IS-IS]    ISO/IEC 10589:2002, Second Edition, "", 2002. -->
          <title>Intermediate System to Intermediate System Intra-Domain
            Routing Exchange Protocol for use in Conjunction with the Protocol
            for Providing the Connectionless-mode Network Service (ISO
            8473)</title>
          <author>
            <organization>ISO/IEC</organization>
          </author>
          <date year="2002"/>
        </front>
        <seriesInfo name="ISO/IEC" value="10589:2002, Second Edition"/>
      </reference>

      <?rfc include="reference.RFC.1195"?>
      <?rfc include="reference.RFC.2119"?>
      <?rfc include="reference.RFC.5120"?>
      <?rfc include="reference.RFC.5303"?>
      <?rfc include="reference.RFC.5305"?>
      <?rfc include="reference.RFC.5308"?>
      <?rfc include="reference.I-D.liu-isis-auto-conf"?>
      <?rfc include="reference.I-D.baker-ipv6-isis-dst-src-routing"?>
      <?rfc include="reference.I-D.ietf-rtgwg-dst-src-routing"?>
      <?rfc include="reference.I-D.lamparter-isis-p2mp"?>
      <?rfc include="reference.I-D.franke-isis-over-ipv6"?>
    </references>

    <references title="Informative References">
      <?rfc include="reference.I-D.sarikaya-6man-sadr-overview"?>
    </references>

    <section anchor="log" title="Change Log">
      <t>(to be removed)</t>
      <t><list style="hanging">
          <t hangText="-00:">July 2015</t>

          <t hangText="-01:">October 2015</t>

          <t hangText="-02:">April 2016; removed isis-over-ipv6</t>
        </list></t>
    </section>
  </back>
</rfc>
<!-- vim: sw=2 ts=2 et
-->