Re: WGLC for BFD over Link Aggregate Group Interfaces - ends November 8

Marc Binderberger <marc@sniff.de> Fri, 01 November 2013 20:29 UTC

Return-Path: <marc@sniff.de>
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 9F75411E813D for <rtg-bfd@ietfa.amsl.com>; Fri, 1 Nov 2013 13:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 eCSHD9FYkoNg for <rtg-bfd@ietfa.amsl.com>; Fri, 1 Nov 2013 13:29:15 -0700 (PDT)
Received: from door.sniff.de (door.sniff.de [IPv6:2001:6f8:94f:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB2711E8131 for <rtg-bfd@ietf.org>; Fri, 1 Nov 2013 13:29:15 -0700 (PDT)
Received: from [IPv6:::1] (localhost.sniff.de [127.0.0.1]) by door.sniff.de (Postfix) with ESMTP id E28CF2AA0F; Fri, 1 Nov 2013 20:29:12 +0000 (GMT)
Date: Fri, 01 Nov 2013 13:29:13 -0700
From: Marc Binderberger <marc@sniff.de>
To: Ashesh Mishra <mishra.ashesh@outlook.com>
Message-ID: <20131101132913173633.325d6feb@sniff.de>
In-Reply-To: <BAY176-W326F85F0A92071D8333280FAF50@phx.gbl>
References: <20131024191431.GO17538@pfrc> <315041E4211CB84E86EF7C25A2AB583D337EBFB3@xmb-rcd-x15.cisco.com> <425296D4-F96F-49FF-86D2-40737B64E117@gmail.com> <20211F91F544D247976D84C5D778A4C32E4EEE0D@SG70YWXCHMBA05.zap.alcatel-lucent.com> <931B5B03-5578-428D-BA5B-F3311E31305B@gmail.com> <20131101012840441464.ae114f50@sniff.de> <BAY176-W326F85F0A92071D8333280FAF50@phx.gbl>
Subject: Re: WGLC for BFD over Link Aggregate Group Interfaces - ends November 8
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: GyazMail version 1.5.15
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
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: Fri, 01 Nov 2013 20:29:15 -0000

Hello Ashesh,

> the receiving end will have a Rx session for every member of the LAG?

Yes. You have a sending and a receiving session per LAG member link.

> If so, how will the session negotiation work with more than one 
> endpoint on the peer node?

section 2.2 explains it. Here the part for starting the session:

   The demultiplexing of a received BFD packet is solely based on the
   Your Discriminator field, if this field is nonzero.  For the initial
   Down BFD packets of a BFD session this value MAY be zero.  In this
   case demultiplexing MUST be based on some combination of other fields
   which MUST include the interface information of the member link.


In other words your implementation "binds" a particular Rx/Tx session 
to one member interface (I use quotation marks to indicate the details 
are up to your implementation).


Regards, Marc



On Fri, 1 Nov 2013 11:58:54 -0700, Ashesh Mishra wrote:
> Hi all,
> 
> Does the mechanism proposed in this draft suggest that the 
> transmitting end will multicast the BFD CC frames over the LAG and 
> the receiving end will have a Rx session for every member of the LAG?
> 
> If so, how will the session negotiation work with more than one 
> endpoint on the peer node?
> 
> --
> Ashesh