Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces
draft-mmm-bfd-on-lags-03

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-02-01 (latest revision 2012-01-06)
Replaced by rfc7130, draft-ietf-bfd-on-lags
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                     M. Bhatia, Ed.
Internet-Draft                                            Alcatel-Lucent
Intended status: Standards Track                            M. Chen, Ed.
Expires: August 4, 2012                              Huawei Technologies
                                                         S. Boutros, Ed.
                                                    M. Binderberger, Ed.
                                                           Cisco Systems
                                                            J. Haas, Ed.
                                                        Juniper Networks
                                                        February 1, 2012

Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG)
                               Interfaces
                        draft-mmm-bfd-on-lags-03

Abstract

   This document proposes a mechanism to run BFD on Link Aggregation
   Group (LAG) interfaces.  It does so by running an independent BFD
   async session on every LAG member link.

   The mechanism allows to verify the link connectivity, either in
   combination with or in absence of LACP, with a shorter detection time
   than what LACP offers.  The connectivity check can also cover
   elements of layer 3.

   A dedicated well-known UDP port is introduced that all BFD packets
   over member links use to disambiguate those from ordinary BFD
   packets.

Requirements Language

   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].

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

Bhatia, et al.           Expires August 4, 2012                 [Page 1]
Internet-Draft           BFD for LAG Interfaces            February 2012

   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 August 4, 2012.

Copyright Notice

   Copyright (c) 2012 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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Bhatia, et al.           Expires August 4, 2012                 [Page 2]
Internet-Draft           BFD for LAG Interfaces            February 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  BFD on LAG member links  . . . . . . . . . . . . . . . . . . .  4
     2.1.  Micro BFD async session address family . . . . . . . . . .  5
     2.2.  Micro BFD async session negotiation  . . . . . . . . . . .  5
   3.  LAG Management Module  . . . . . . . . . . . . . . . . . . . .  6
     3.1.  BFD in the presence of LACP  . . . . . . . . . . . . . . .  6
     3.2.  BFD in the absence of LACP . . . . . . . . . . . . . . . .  7
     3.3.  Handling Exceptions  . . . . . . . . . . . . . . . . . . .  7
   4.  BFD on LAG members and layer-3 applications  . . . . . . . . .  7
   5.  Detecting a member link failure  . . . . . . . . . . . . . . .  7
   6.  Security Consideration . . . . . . . . . . . . . . . . . . . .  8
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  8
   9.  Contributing authors . . . . . . . . . . . . . . . . . . . . .  8
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     10.1. Normative References . . . . . . . . . . . . . . . . . . .  9
     10.2. Informative References . . . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10

Bhatia, et al.           Expires August 4, 2012                 [Page 3]
Internet-Draft           BFD for LAG Interfaces            February 2012

1.  Introduction

   The Bidirectional Forwarding Detection (BFD) protocol [RFC5880]
Show full document text