Re: Comment on DestinationMac in draft-mmm-bfd-on-lags

Donald Eastlake <d3e3e3@gmail.com> Sun, 30 September 2012 19:52 UTC

Return-Path: <d3e3e3@gmail.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 4A77E21F8578 for <rtg-bfd@ietfa.amsl.com>; Sun, 30 Sep 2012 12:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.267
X-Spam-Level:
X-Spam-Status: No, score=-102.267 tagged_above=-999 required=5 tests=[AWL=-0.968, BAYES_00=-2.599, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_LOW=-1, 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 dqEWUKctdfWg for <rtg-bfd@ietfa.amsl.com>; Sun, 30 Sep 2012 12:52:27 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id CAA5F21F84DF for <rtg-bfd@ietf.org>; Sun, 30 Sep 2012 12:52:27 -0700 (PDT)
Received: by iec9 with SMTP id 9so12397415iec.31 for <rtg-bfd@ietf.org>; Sun, 30 Sep 2012 12:52:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=nFLKRUy9BnFzo+DaKU+EQYHy5FS2bKWnr/4Mxr/5ftU=; b=OITfIMp/3oZ/LCyoTUUMk5aWBa0v2zBK9meW3MIWkjyg8ao5knl0CwehRfFQxpwCnJ vOcL/LY18IKxNgjpzEda0anNsudlh1GMr3+f0yoJZhpcu911L4TGLHQulMby1E64wNTw nQAFcrMtcy56Q/kKYiHN3Ws3K2BI7BatLovTecpkHMBuOJ8lnOOKwV0P2rTgr6EnHjRG C1C5/CA8xULEh1d7kvgHGLZB5uGW2Fe4vZI6By2iwCKbSmm20npsYB19VlcKVkZqTfSp ylh5MKjz3GpjzxmlnBt3ZrLln/FlvHB751PssdZ/kMlfbRr4FGMOYRy6UiJ4pY1/k8Jg gt5Q==
Received: by 10.50.185.230 with SMTP id ff6mr4491667igc.0.1349034747140; Sun, 30 Sep 2012 12:52:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.86.113 with HTTP; Sun, 30 Sep 2012 12:52:06 -0700 (PDT)
In-Reply-To: <7A2E55DFE338EE418E3B95A0C388997D075E407F79@INBANSXCHMBSA1.in.alcatel-lucent.com>
References: <7A2E55DFE338EE418E3B95A0C388997D075E407F79@INBANSXCHMBSA1.in.alcatel-lucent.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 30 Sep 2012 15:52:06 -0400
Message-ID: <CAF4+nEE6kK5WfSonT14z-rz4iFHS7JFvVry+xS1a9c+Waxvebw@mail.gmail.com>
Subject: Re: Comment on DestinationMac in draft-mmm-bfd-on-lags
To: "JOVELPONNAIEN, ARULMOHAN (ARULMOHAN)" <arulmohan.jovelponnaien@alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"
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: Sun, 30 Sep 2012 19:52:32 -0000

Hi,

On Fri, Sep 28, 2012 at 6:45 AM, JOVELPONNAIEN, ARULMOHAN (ARULMOHAN)
<arulmohan.jovelponnaien@alcatel-lucent.com> wrote:
> Hi All,
>
> Micro-BFD session would use dedicated destination MAC address allocated for
> IANA range (RFC 5342). But this MAC address range is not link-level and would
> allow forwarding of Link-Level BFD packets by intermediate L2 switches.
>
> Assume case below, here it is possible that 3 micro BFD sessions from
> Router1 could be forwarded on single-port to Router2.
> Router1 ------------(3-port) LAG------------L2 Switch-------(1-port
> LAG)-----------Router2
>
> If MAC-address is chosen from range 01:80:c2:xx:xx:xx, then this case would
> not arise. Micro-BFD session would then be terminated by L2 switch
> immediately. By 802.1d standard 01:80:c2:xx:xx:xx would be terminated by L2
> switch.

I believe you will find that the range of addresses that are blocked
by 802.1 bridges if they do not understand them is MUCH narrower. It
is, in fact, only the block of 16 addresses from 01:80:C2:00:00:00 to
01:80:C2:00:00:0F. For example, 01-80-C2-00-00-14 and
01-80-C2-00-00-15 are the addresses used by IS-IS for All Level 1 and
All Level 2 Intermediate Systems, respectively, and which must be
transparently handled by bridges or you couldn't have a bridge in
between two Layer 3 IP routers.

> Is it not better if we choose a MAC address in 01:80:c2 range similar to
> LACP to make sure micro-BFD session remains link-level protocol?

If you want an address of that type, you could apply to the IEEE
Registration Authority although the WG should probably coordinate that
with you AD. Only a tiny fraction of those addresses, which are
intended for standards use, have been allocated. But, as I say, it
will not make any difference to the behavior and it seems easier for
an IETF WG to get a 48-bit multicast address using the procedures in
RFC 5342.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Regards,
> Arul Mohan.
>
>