One document matched: draft-ginsberg-isis-sbfd-discriminator-00.xml
<?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" docName="draft-ginsberg-isis-sbfd-discriminator-00.txt"
ipr="pre5378Trust200902">
<front>
<title abbrev="isis-sbfd-discriminator">Advertising 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>USA</country>
</postal>
<email>ginsberg@cisco.com</email>
</address>
</author>
<author fullname="Nobo Akiya" initials="N" surname="Akiya">
<organization>Cisco Systems</organization>
<address>
<postal>
<street/>
<city/>
<code/>
<region/>
<country/>
</postal>
<email>nobo@cisco.com</email>
</address>
</author>
<author fullname="Mach(Guoyi) Chen" initials="M" surname="Chen">
<organization>Huawei</organization>
<address>
<postal>
<street/>
<city/>
<code/>
<country/>
</postal>
<email>mach.chen@huawei.com</email>
</address>
</author>
<date day="08" month="May" year="2014"/>
<area>Routing Area</area>
<workgroup>Networking Working Group</workgroup>
<keyword>Sample</keyword>
<abstract>
<t>This document defines a means of advertising one or more S-BFD
Discriminators using the IS-IS Router Capability TLV.</t>
</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 RFC 2119 [RFC2119].</t>
</note>
</front>
<middle>
<section title="Introduction">
<t>[S-BFD] defines a simplified mechanism to use Bidirectional
Forwarding Detection (BFD)[RFC5880]. This mechanism depends on network
nodes knowing the BFD discriminators which each node in the network has
reserved for this purpose. Use of the Intermediate System to
Intermediate System (IS-IS)[IS-IS] protocol is one possible means of
advertising these discriminators.</t>
</section>
<section title=" Encoding Format">
<t>The IS-IS Router CAPABILITY TLV as defined in [RFC4971] will be used
to advertise S-BFD discriminators. A new sub-TLV is defined as described
below. S-BFD Discriminators sub-TLVs are formatted as specified in
[RFC5305].</t>
<t><figure>
<artwork><![CDATA[ No. of octets
+-----------------------------+
| Type (to be assigned by | 1
| IANA - suggested value 19) |
+-----------------------------+
| Length (multiple of 4) | 1
+-----------------------------+
| Discriminator Value(s) | 4/Discriminator
: :
+-----------------------------+
]]></artwork>
</figure></t>
<t>Inclusion of the S-BFD Discriminators sub-TLV in a Router Capability
TLV is optional. Multiple S-BFD Discriminators sub-TLVs MAY be
advertised by an IS. When multiple S-BFD discriminators are advertised
how a given discriminator is mapped to a specific use case 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 [RFC4971].</t>
</section>
<section anchor="IANA" title="IANA Considerations">
<t>This document requires the definition of a new sub-TLV in the
Sub-TLVs for TLV 242 registry. The value written below is a suggested
value subject to assignment by IANA.</t>
<figure>
<artwork><![CDATA[
Value Description
---- ---------------------
19 S-BFD Discriminators
]]></artwork>
</figure>
</section>
<section anchor="Security" title="Security Considerations">
<t>Security concerns for IS-IS are addressed in [IS-IS], [RFC5304], and
[RFC5310]. Introduction of the S-BFD Discriminators sub-TLV introduces
no new security risks for IS-IS.</t>
<t>Advertisement of the S-BFD discriminators does make 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
the Security Considerations section of [S-BFD].</t>
</section>
<section anchor="Acknowledgements" title="Acknowledgements">
<t>The authors wish to thank Sam Aldrin, Manav Bhatia, and Carlos
Pignataro for input essential to defining the needed functionality.</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), ISO/IEC 10589:2002, Second Edition.</title>
<author fullname="ISO "International Organization for Standardization""/>
<date month="Nov" year="2002"/>
</front>
</reference>
<reference anchor="S-BFD">
<front>
<title>Seamless Bidirectional Forwarding Detection (S-BFD),
draft-akiya-bfd-seamless-base-03(work in progress)</title>
<author fullname="Akiya N., et al,"/>
<date month="April" year="2014"/>
</front>
</reference>
</references>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-23 23:22:22 |