<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">

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

<rfc category="std" number="7883"
     ipr="pre5378Trust200902" submissionType="IETF" consensus="yes">

  <front>
    <title abbrev="Advertising S-BFD Discriminators in IS-IS">Advertising
Seamless Bidirectional Forwarding Detection (S-BFD) Discriminators in IS-IS</title>

    <author fullname="Les Ginsberg" initials="L" surname="Ginsberg">
      <organization>Cisco Systems</organization>
      <address>
        <postal>
          <street>510 McCarthy Blvd.</street>
          <city>Milpitas</city>
          <code>95035</code>
          <region>CA</region>
          <country>United States</country>
        </postal>
        <email>ginsberg@cisco.com</email>
      </address>
    </author>

    <author fullname="Nobo Akiya" initials="N" surname="Akiya">
      <organization>Big Switch Networks</organization>
      <address>
        <email>nobo.akiya.dev@gmail.com</email>
      </address>
    </author>

    <author fullname="Mach(Guoyi) Chen" initials="M" surname="Chen">
      <organization>Huawei</organization>
      <address>
        <email>mach.chen@huawei.com</email>
      </address>
    </author>

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

    <abstract>
      <t>This document defines a means of advertising one or more
      Seamless Bidirectional Forwarding Detection (S-BFD)
      Discriminators using the IS-IS Router CAPABILITY TLV.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t><xref target="RFC7880"/> defines a simplified mechanism for using
      Bidirectional Forwarding Detection (BFD) <xref target="RFC5880"/>.
      This mechanism depends on network nodes knowing the BFD
      Discriminators that each node in the network has reserved for this
      purpose. The use of the Intermediate System to Intermediate System
      (IS-IS) <xref target="IS-IS"/> protocol is one possible means of
      advertising these discriminators.</t>

        <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 RFC 2119
        <xref target="RFC2119"/>.</t>

    </section>

    <section title=" Encoding Format">
      <t>The IS-IS Router CAPABILITY TLV as defined in
      <xref target="RFC4971"/> will be used to advertise Seamless
      BFD (S-BFD) Discriminators. A new sub-TLV is defined as described
      below. S-BFD Discriminators sub-TLVs are formatted as specified in
      <xref target="RFC5305"/>.</t>

      <t><figure>
          <artwork><![CDATA[                                               No. of octets
              +-----------------------------+
              | Type (20)                   |     1
              +-----------------------------+
              | Length (multiple of 4)      |     1
              +-----------------------------+
              | Discriminator Value(s)      |     4/Discriminator
              :                             :
              +-----------------------------+
]]></artwork> </figure></t>

      <t>The inclusion of an S-BFD Discriminators sub-TLV in a Router
      CAPABILITY TLV is optional. Multiple S-BFD Discriminators sub-TLVs MAY be
      advertised by an IS. How a given discriminator is mapped to a specific
      use case when multiple S-BFD Discriminators are advertised is out of
      scope for this document.</t>

      <t>S-BFD Discriminator advertisements MAY be flooded within an area or
      throughout the domain, using the procedures specified in
      <xref target="RFC4971"/>. The appropriate flooding scope depends on
      the intended use of S-BFD. If S-BFD usage will be exclusively within
      a Level-1 area, then area scope is appropriate. If S-BFD usage will
      span different Level-1 areas, then domain scope is appropriate.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>IANA has added a new sub-TLV in the
      "Sub&nbhy;TLVs for TLV 242" registry. The registration is as follows:</t>

      <figure>
        <artwork><![CDATA[ 
   Value  Description           
   -----  --------------------
   20     S-BFD Discriminators
]]></artwork>
      </figure>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>Security concerns for IS-IS are addressed in <xref target="IS-IS"/>,
      <xref target="RFC5304"/>, and <xref target="RFC5310"/>.
      The new S-BFD Discriminators sub-TLV does not introduce any new
      security risks for IS-IS.</t>

      <t>Advertising the S-BFD Discriminators makes it possible for
      attackers to initiate S-BFD sessions using the advertised information.
      The vulnerabilities this poses and how to mitigate them are discussed
      in <xref target="RFC7880"/>.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
   <?rfc include="reference.RFC.2119"?>
   <?rfc include='reference.RFC.4971'?>
   <?rfc include='reference.RFC.5304'?>
   <?rfc include='reference.RFC.5305'?>
   <?rfc include='reference.RFC.5310'?>
   <?rfc include='reference.RFC.5880'?>

   <reference anchor="IS-IS">
    <front>
    <title>Intermediate System to Intermediate System intra-domain routeing
    information exchange protocol for use in conjunction with the protocol
    for providing the connectionless-mode network service (ISO 8473)</title>
    <author>
    <organization>International Organization for Standardization</organization>
    </author>
    <date month="" year="2002" />
    </front>
    <seriesInfo name="ISO" value="Standard 10589" />
   </reference>

<!-- draft-ietf-bfd-seamless-base (RFC 7880) -->
   <reference anchor="RFC7880" target="http://www.rfc-editor.org/info/rfc7880">
     <front>
     <title>Seamless Bidirectional Forwarding Detection (S-BFD)</title>
     <author initials='C' surname='Pignataro' fullname='Carlos Pignataro'>
       <organization />
     </author>
     <author initials='D' surname='Ward' fullname='David Ward'>
       <organization />
     </author>
     <author initials='N' surname='Akiya' fullname='Nobo Akiya'>
       <organization />
     </author>
     <author initials='M' surname='Bhatia' fullname='Manav Bhatia'>
       <organization />
     </author>
     <author initials='S' surname='Pallagatti' fullname='Santosh Pallagatti'>
       <organization />
     </author>
     <date month='July' year='2016' />
     </front>
     <seriesInfo name='RFC' value='7880'/>
     <seriesInfo name="DOI" value="10.17487/RFC7880"/>
   </reference>
  </references>

  <section anchor="Acknowledgements" title="Acknowledgements" numbered="no">
     <t>The authors wish to thank Sam Aldrin, Manav Bhatia, and Carlos
     Pignataro for input essential to defining the needed functionality.</t>
  </section>
 </back>
</rfc>
