Re: draft-mmm-bfd-on-lags: IPv4 _and_ IPv6 ?

Jeffrey Haas <jhaas@pfrc.org> Wed, 12 September 2012 16:38 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 480C121F84E6 for <rtg-bfd@ietfa.amsl.com>; Wed, 12 Sep 2012 09:38:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.215
X-Spam-Level:
X-Spam-Status: No, score=-102.215 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32j0LqGJfUVt for <rtg-bfd@ietfa.amsl.com>; Wed, 12 Sep 2012 09:38:07 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id DCEC821F84AE for <rtg-bfd@ietf.org>; Wed, 12 Sep 2012 09:38:07 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 2C595C3A3; Wed, 12 Sep 2012 12:38:02 -0400 (EDT)
Date: Wed, 12 Sep 2012 12:38:02 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Marc Binderberger <marc@sniff.de>
Subject: Re: draft-mmm-bfd-on-lags: IPv4 _and_ IPv6 ?
Message-ID: <20120912163802.GC25587@pfrc>
References: <AC626F7A-7A9A-4395-B653-32C0F45BFA85@sniff.de> <7C362EEF9C7896468B36C9B79200D8350D063A0B51@INBANSXCHMBSA1.in.alcatel-lucent.com> <CAGEmCZxJtms7puJW6W4J13vr7Y1dajpuGt0cZQXivGFFWEafOw@mail.gmail.com> <7C362EEF9C7896468B36C9B79200D8350D063A0D7A@INBANSXCHMBSA1.in.alcatel-lucent.com> <0D1B9ACE-889A-4090-88CC-BA7E3652117F@sniff.de> <20120912133410.GB25037@pfrc> <98FA4437-6313-442D-B181-974CEA623363@sniff.de> <20120912140448.GA25587@pfrc> <165FD086-EC34-4658-9B76-C93F64B93C08@sniff.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <165FD086-EC34-4658-9B76-C93F64B93C08@sniff.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: draft-mmm-bfd-on-lags@tools.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: Wed, 12 Sep 2012 16:38:08 -0000

On Wed, Sep 12, 2012 at 06:29:45PM +0200, Marc Binderberger wrote:
> Hello Jeff et al.,
> 
> is the following text achieving what we want?
> 
> 
> ----snip----snap----snip----snap----
> 5.  Detecting a member link failure
> 
>    When a micro BFD session goes down then this member link MUST be
>    taken out of the LAG L2 load balance table(s).
> 
>    In case an implementation has separate load balance tables for IPv4
>    and IPv6 then if both an IPv4 and IPv6 micro session exist for a
>    member link an implementation MAY remove the member link from the
>    load balance table only that matches the address family of the
>    failing BFD session.  If for example the IPv4 micro session fails but
>    the IPv6 micro session stays up then the member link MAY be removed
>    from the IPv4 load balance table only but remains forwarding in the
>    IPv6 load balance table.
> ----snip----snap----snip----snap----
> 
> 
> And similar for the part where we describe adding a member link to the table.

Perfect.

-- Jeff