IETF Logo Mail Archive

BFD on LAG interfaces

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> Tue, 13 December 2011 18:21 UTC

Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E401821F8ABD for <rtg-bfd@ietfa.amsl.com>; Tue, 13 Dec 2011 10:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.098
X-Spam-Level:
X-Spam-Status: No, score=-6.098 tagged_above=-999 required=5 tests=[AWL=0.501, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id msOBLTMKmP7H for <rtg-bfd@ietfa.amsl.com>; Tue, 13 Dec 2011 10:21:34 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id ABEB021F8AA8 for <rtg-bfd@ietf.org>; Tue, 13 Dec 2011 10:21:33 -0800 (PST)
Received: from inbansmailrelay1.in.alcatel-lucent.com (h135-250-11-31.lucent.com [135.250.11.31]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id pBDILT3I000509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <rtg-bfd@ietf.org>; Tue, 13 Dec 2011 12:21:32 -0600 (CST)
Received: from INBANSXCHHUB03.in.alcatel-lucent.com (inbansxchhub03.in.alcatel-lucent.com [135.250.12.80]) by inbansmailrelay1.in.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id pBDILSBJ028486 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rtg-bfd@ietf.org>; Tue, 13 Dec 2011 23:51:29 +0530
Received: from INBANSXCHMBSA1.in.alcatel-lucent.com ([135.250.12.38]) by INBANSXCHHUB03.in.alcatel-lucent.com ([135.250.12.80]) with mapi; Tue, 13 Dec 2011 23:51:28 +0530
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Date: Tue, 13 Dec 2011 23:51:27 +0530
Subject: BFD on LAG interfaces
Thread-Topic: BFD on LAG interfaces
Thread-Index: Acy5xAc2rqbrLGipReylGpRIoRTZpQ==
Message-ID: <7C362EEF9C7896468B36C9B79200D8350D026F0D2C@INBANSXCHMBSA1.in.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-bfd>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Dec 2011 18:21:35 -0000

Hi,

We had a very lively debate on the BFD mailing list a few months back on standardizing BFD over the LAG interfaces.

We have written a draft that proposes a new approach that fixes the issues that are seen with how folks do BFD over the LAGs today.

Draft available here:
http://tools.ietf.org/id/draft-mmm-bfd-on-lags-00.txt

Would be great to comments from the WG.

Cheers, 
Marc, Mach and Manav

--

Abstract

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

   A dedicated well-known multicast IP address for both IPv4 and IPv6 is
   introduced as the destination IP address of the BFD packets when
   running BFD on the member links of the LAG.

   There is currently no standard that describes how BFD should run on
   LAG interfaces.  As a result multiple non-interoperable BFD
   implementations for LAG interfaces exist.  This draft provides a
   short overview as a context for the new proposed mechanism.

v2.23.0 | Report a Bug | By Email