idnits 2.17.1 draft-mirsky-bfd-p2mp-vrrp-use-case-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == It seems as if not all pages are separated by form feeds - found 0 form feeds but 4 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 6, 2015) is 3214 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-19) exists of draft-ietf-bfd-multipoint-06 == Outdated reference: A later version (-04) exists of draft-nitish-vrrp-bfd-01 Summary: 0 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 BFD Working Group G. Mirsky 3 Internet-Draft J. Tantsura 4 Intended status: Informational Ericsson 5 Expires: January 7, 2016 July 6, 2015 7 Bidirectional Forwarding Detection (BFD) for Multi-point Networks and 8 Virtual Router Redundancy Protocol (VRRP) Use Case 9 draft-mirsky-bfd-p2mp-vrrp-use-case-00 11 Abstract 13 This document discusses use of Bidirectional Forwarding Detection 14 (BFD) for multi-point networks to provide Virtual Router Redundancy 15 Protocol (VRRP) with sub-second Master convergence. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on January 7, 2016. 34 Copyright Notice 36 Copyright (c) 2015 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 1.1. Conventions used in this document . . . . . . . . . . . . 2 53 1.1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 2 54 1.1.2. Requirements Language . . . . . . . . . . . . . . . . 2 55 2. Problem Statement . . . . . . . . . . . . . . . . . . . . . . 3 56 3. Applicability of p2mp BFD . . . . . . . . . . . . . . . . . . 3 57 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 58 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 59 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3 60 7. Normative References . . . . . . . . . . . . . . . . . . . . 3 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 63 1. Introduction 65 The [RFC5798] is the current specification of the Virtual Router 66 Redundancy Protocol (VRRP) for IPv4 and IPv6 networks. VRRPv3 allows 67 for faster switchover to a Backup router. Using such capability with 68 software-based implementation of VRRP is may prove challenging. But 69 it still may be possible to deploy VRRP and provide sub-second 70 detection of Master router failure by Backup routers. 72 Bidirectional Forwarding Detection (BFD) [RFC5880] had been 73 originally defined detect failure of point-to-point (p2p) paths: 74 single-hop [RFC5881], multihop [RFC5883]. Single-hop BFD may be used 75 to enable Backup routers to detect failure of the Master router 76 within 100 msec or faster. [I-D.nitish-vrrp-bfd] demonstrates how, 77 with some extenstions to [RFC5798], that can be achieved. 79 [I-D.ietf-bfd-multipoint] extends [RFC5880] for multipoint and 80 multicast networks, which is precisely characterizes deployment 81 scenarios for VRRP over LAN segment. 83 1.1. Conventions used in this document 85 1.1.1. Terminology 87 BFD: Bidirectional Forwarding Detection 89 VRRP: Virtual Router Redundancy Protocol 91 1.1.2. Requirements Language 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 95 "OPTIONAL" in this document are to be interpreted as described in 96 [RFC2119]. 98 2. Problem Statement 100 A router may be part of several Virtual Router Redundancy groups, as 101 Master in some and as Backup in others. Supporting sub-second mode 102 for VRRPv3 [RFC5798] for all these roles without specialized support 103 in data plane may prove to be very challenging. BFD already has many 104 implementations based on HW that are capable to support multiple sub- 105 second session concurrently. 107 3. Applicability of p2mp BFD 109 [I-D.ietf-bfd-multipoint] may provide the efficient and scaleable 110 solution for fast-converging environment that uses default route 111 rather than dynamic routing. Each redundancy group presents itself 112 as p2mp BFD session with its Master being the root and Backup routers 113 being tails of the p2mp BFD session. The Master router starts 114 transmitting BFD control packets with VRID as source IP address. 115 Backup router demultiplexes p2mp BFD test sessions based on VRID that 116 it been configured with. Once Backup router accepts p2mp session 117 from the new Master router backup router the Backup router MAY use My 118 Discriminator from received p2mp BFD control packet to demultiplex 119 p2mp BFD sessions. When a Backup router detects failure of the 120 Master router it re-evaluates its role in the VRID. As result, the 121 Backup router may become the Master router of the given VRID or 122 continue as a Backup router. If the former is the case, then the new 123 Master router MUST select My Discriminator and start transmitting 124 p2mp BFD control packets using Master IP address as source IP address 125 fro p2mp BFD control packets. If the latter is the case, then the 126 Backup router MUST wait for p2mp BFD control packet with source IP 127 address set to VRID. 129 4. IANA Considerations 131 This document makes no requests for IANA allocations. This section 132 may be deleted by RFC Editor. 134 5. Security Considerations 136 Secuirity considerations discussed in [RFC5798], [RFC5880], and 137 [I-D.ietf-bfd-multipoint], apply to this document. 139 6. Acknowledgements 141 7. Normative References 143 [I-D.ietf-bfd-multipoint] 144 Katz, D., Ward, D., and J. Networks, "BFD for Multipoint 145 Networks", draft-ietf-bfd-multipoint-06 (work in 146 progress), May 2015. 148 [I-D.nitish-vrrp-bfd] 149 Gupta, N., Dogra, A., and C. Docherty, "Fast failure 150 detection using peer learning in VRRP with BFD", draft- 151 nitish-vrrp-bfd-01 (work in progress), June 2015. 153 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 154 Requirement Levels", BCP 14, RFC 2119, March 1997. 156 [RFC5798] Nadas, S., "Virtual Router Redundancy Protocol (VRRP) 157 Version 3 for IPv4 and IPv6", RFC 5798, March 2010. 159 [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 160 (BFD)", RFC 5880, June 2010. 162 [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 163 (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June 164 2010. 166 [RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection 167 (BFD) for Multihop Paths", RFC 5883, June 2010. 169 Authors' Addresses 171 Greg Mirsky 172 Ericsson 174 Email: gregory.mirsky@ericsson.com 176 Jeff Tantsura 177 Ericsson 179 Email: jeff.tantsura@ericsson.com