Bidirectional Forwarding Detection (BFD) on Multi-chassis Ling Aggregation Group (MC-LAG) Interfaces in IP/MPLS Networks
draft-tanmir-rtgwg-bfd-mc-lag-mpls-01

Document Type Active Internet-Draft (candidate for bfd WG)
Last updated 2017-05-05 (latest revision 2017-03-10)
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state Call For Adoption By WG Issued
Polled for WG adoption but not adopted
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
RTG Working Group                                              G. Mirsky
Internet-Draft                                                 ZTE Corp.
Updates: 7130 (if approved)                                  J. Tantsura
Intended status: Standards Track                              Individual
Expires: September 11, 2017                               March 10, 2017

     Bidirectional Forwarding Detection (BFD) on Multi-chassis Ling
       Aggregation Group (MC-LAG) Interfaces in IP/MPLS Networks
                 draft-tanmir-rtgwg-bfd-mc-lag-mpls-01

Abstract

   This document describes use of Bidirectional Forwarding Detection for
   Multi-chassis Link Aggregation Group to provide faster than Link
   Aggregation Control Protocol convergence.  This specification
   enhances and updates RFC 7130 "Bidirectional Forwarding Detection
   (BFD) on Link Aggregation Group (LAG) Interfaces".

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 11, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Mirsky & Tantsura      Expires September 11, 2017               [Page 1]
Internet-Draft         BFD for MC-LAG over IP/MPLS            March 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions used in this document . . . . . . . . . . . .   2
       1.1.1.  Terminology . . . . . . . . . . . . . . . . . . . . .   2
       1.1.2.  Requirements Language . . . . . . . . . . . . . . . .   3
   2.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
   3.  BFD on MC-LAG with IP/MPLS data plane . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The [RFC7130] defines use of Bidirectional Forwarding Detection (BFD)
   on Link Aggregation Group (LAG) interfaces.  Multi-chassis LAG (MC-
   LAG) is type of LAG [IEEE.802.1AX.2008] with member links terminated
   on separate chassis.  [IEEE.802.1AX.2008] does not specify MC-LAG but
   doesn't preclude it either.  Link Aggregation Control Protocol
   (LACP), also defined in [IEEE.802.1AX.2008], can work with MC-LAG
   but, as in LAG case, can detect link failure only in range of single
   seconds.  This document defines how mechanism defined to work on LAG
   interfaces [RFC7130] can be adapted to MC-LAG case to enable sub-
   second detection of member link failure.

1.1.  Conventions used in this document

1.1.1.  Terminology

   ACH: Associated Channel Header

   BFD: Bidirectional Forwarding Detection

   BoS: Bottom of the Stack

   G-ACh: Generic Associated Channel

   GAL: Generic Associated Label

   LAG: Link Aggregation Group

   LACP: Link Aggregation Control Protocol

Mirsky & Tantsura      Expires September 11, 2017               [Page 2]
Internet-Draft         BFD for MC-LAG over IP/MPLS            March 2017

   MC-LAG: Multi-chassis Link Aggregation Group

   MPLS: Multi-Protocol Label Switching

1.1.2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text