<?xml version='1.0' encoding='UTF-8'?>

<reference anchor='I-D.chen-bfd-interface'>
<front>
<title>Bidirectional Forwarding Detection (BFD) for Interface</title>

<author initials='M' surname='Chen' fullname='Mach Chen'>
    <organization />
</author>

<author initials='Z' surname='Wang' fullname='Zuliang Wang'>
    <organization />
</author>

<author initials='L' surname='Guo' fullname='Liang Guo'>
    <organization />
</author>

<author initials='M' surname='Binderberger' fullname='Marc Binderberger'>
    <organization />
</author>

<date month='July' day='4' year='2011' />

<abstract><t>This document describes how application clients can request IP-based Bidirectional Forwarding Detection (BFD) sessions while either being IP agnostic themselves or while dealing with IP unnumbered interfaces.  A dedicated well-known multicast IP address 224.XXX.XXX.XXX is used as the destination IP address of the BFD packets when running BFD for interface.  It allows for BFD sessions on interfaces that may have no IP addresses, either because the interface is unnumbered or because the layer 3 protocol status of the interfaces is not up yet.  One application of BFD for interface is to run BFD over LAG/Bundle component links.  An example will be given in this document.</t></abstract>

</front>

<seriesInfo name='Internet-Draft' value='draft-chen-bfd-interface-00' />
<format type='TXT'
        target='http://www.ietf.org/internet-drafts/draft-chen-bfd-interface-00.txt' />
</reference>

