One document matched: draft-mirsky-bfd-p2mp-vrrp-use-case-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"[
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC5880 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5880.xml">
<!ENTITY RFC5881 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5881.xml">
<!ENTITY RFC5883 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5883.xml">
<!ENTITY RFC5798 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5798.xml">
<!ENTITY I-D.nitish-vrrp-bfd SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-nitish-vrrp-bfd-01.xml">
<!ENTITY I-D.ietf-bfd-multipoint SYSTEM "http://xml.resource.org/public/rfc/bibxml3/reference.I-D.draft-ietf-bfd-multipoint-06.xml">

]>
<?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="info" ipr="trust200902" docName="draft-mirsky-bfd-p2mp-vrrp-use-case-00">

<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>

<front>
	<title abbrev='BFD P2MP Use in VRRP'>Bidirectional Forwarding Detection (BFD) for Multi-point Networks and Virtual Router Redundancy Protocol (VRRP) Use Case</title>

	<author initials='G.' surname="Mirsky" fullname='Greg Mirsky'>
		<organization>Ericsson</organization>
		<address>
			<email>gregory.mirsky@ericsson.com</email>
		</address> 
	</author>
 	<author initials='J.' surname="Tantsura" fullname='Jeff  Tantsura'>
		<organization>Ericsson</organization>
		<address>
			<email>jeff.tantsura@ericsson.com</email>
		</address> 
	</author>

    <date day="6" month="July" year="2015" />

    <area>Routing</area>

    <workgroup>BFD Working Group</workgroup>

    <keyword>Internet-Draft</keyword>

   <keyword>VRRP</keyword>
   
   <keyword>BFD </keyword>
	
	<abstract>
	<t>
	This document discusses use of Bidirectional Forwarding Detection (BFD) for multi-point networks 
	to provide Virtual Router Redundancy Protocol (VRRP) with sub-second Master convergence.
	 </t>
	</abstract>
</front>

<middle>
  <section anchor="intro" title="Introduction">
 <t>
 The <xref target="RFC5798"/> is the current specification of the Virtual Router Redundancy Protocol (VRRP)
 for IPv4 and IPv6 networks. VRRPv3 allows for faster switchover to a Backup router. Using such capability
 with software-based implementation of VRRP is may prove challenging. 
But it still may be possible to deploy
 VRRP and provide sub-second detection of Master router failure by Backup routers.
 </t>
 <t>
 Bidirectional Forwarding Detection (BFD) <xref target="RFC5880"/> had been originally defined detect
 failure of point-to-point (p2p) paths: single-hop <xref target="RFC5881"/>, multihop <xref target="RFC5883"/>.
 Single-hop BFD may be used to enable Backup routers to detect failure of the Master router within 100 msec or faster.
 <xref target="I-D.nitish-vrrp-bfd"/> demonstrates how, with some extenstions to <xref target="RFC5798"/>,
 that can be achieved.
 </t>
 <t>
 <xref target="I-D.ietf-bfd-multipoint"/> extends <xref target="RFC5880"/> for multipoint and multicast
 networks, which is precisely characterizes deployment scenarios for VRRP over LAN segment.
 </t>
         
     <section title="Conventions used in this document">
         <section title="Terminology">

            <t>BFD:          Bidirectional Forwarding Detection
</t>
            <t>VRRP:        Virtual Router Redundancy Protocol
</t>
         </section>    
         
        <section title="Requirements Language">
             <t>
	  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
                "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 
	  "OPTIONAL" in this document are to be interpreted as described in 
	  <xref target="RFC2119"></xref>.
             </t>
          </section>
      </section>
     </section>
      
     <section anchor="problem-statement" title="Problem Statement">
     
<t>
A router may be part of several Virtual Router Redundancy groups, as Master in some and as Backup in others.
Supporting sub-second mode for VRRPv3 <xref target="RFC5798"/> for all these roles without specialized support
in data plane may prove to be very challenging. BFD already has many implementations based on HW that are capable
to support multiple sub-second session concurrently.
</t>
</section>

<section anchor="apply-p2mp-bfd" title="Applicability of p2mp BFD">
<t>
 <xref target="I-D.ietf-bfd-multipoint"/> may provide the efficient and scaleable solution for fast-converging
 environment that uses default route rather than dynamic routing. Each redundancy group presents itself as p2mp BFD
 session with its Master being the root and Backup routers being tails of the p2mp BFD session. The Master
 router starts transmitting BFD control packets with VRID as source IP address. Backup router demultiplexes
 p2mp BFD test sessions based on VRID that it been configured with. Once Backup router accepts p2mp session
 from the new Master router backup router the Backup router MAY use My Discriminator from received
 p2mp BFD control packet to demultiplex p2mp BFD sessions. When a Backup
 router detects failure of the Master router it re-evaluates its role in the VRID. As result, the Backup router may become the Master
router of the given VRID or continue as a Backup router. If the former is the case, then the new Master
router MUST select My Discriminator and start transmitting p2mp BFD control
 packets using Master IP address as source IP address fro p2mp BFD control packets. If the latter is the case, then the
 Backup router MUST wait for p2mp BFD control packet with source IP address set to VRID.
</t>
</section>
      

     <section anchor="iana-consider" title="IANA Considerations">
     <t>
This document makes no requests for IANA allocations. This section may be deleted by RFC Editor.
 </t>
    </section>
     
     <section anchor="security" title="Security Considerations">
     <t>
 Secuirity considerations discussed in <xref target="RFC5798"/>, <xref target="RFC5880"/>,
 and <xref target="I-D.ietf-bfd-multipoint"/>, apply to this document. 
     </t>
     </section>
      
     
      <section title="Acknowledgements">
         <t>
         </t>  
      </section>

  </middle>
  
    <back>
    <references title="Normative References">
     
     &RFC2119;
     
     &RFC5880;
     
     &RFC5881;
     
     &RFC5883;
     
     &RFC5798;
     
 <!--
    <?rfc include='reference.I-D.draft-nitish-vrrp-bfd'?>

   <?rfc include='reference.I-D.draft-ietf-bfd-multipoint'?>
 -->
    &I-D.nitish-vrrp-bfd;
    
    &I-D.ietf-bfd-multipoint;
         
    </references>


 </back>
 </rfc>