Re: [mpls] Two new drafts on (micro-)BFD over MC-LAG interfaces

Gregory Mirsky <> Fri, 08 April 2016 12:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3B55612D682; Fri, 8 Apr 2016 05:39:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RLHWT1WQKRNR; Fri, 8 Apr 2016 05:39:37 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2448E12D823; Fri, 8 Apr 2016 05:39:17 -0700 (PDT)
X-AuditID: c618062d-f79216d00000767f-0a-5707a027cc62
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 35.D6.30335.720A7075; Fri, 8 Apr 2016 14:12:24 +0200 (CEST)
Received: from ([]) by ([]) with mapi id 14.03.0248.002; Fri, 8 Apr 2016 08:39:15 -0400
From: Gregory Mirsky <>
To: Manav Bhatia <>, Mach Chen <>
Thread-Topic: Two new drafts on (micro-)BFD over MC-LAG interfaces
Thread-Index: AdGOvsdErg6+dntrQsqNMvPnP9/byACNIV+ZABt/KgAADGd7oA==
Date: Fri, 08 Apr 2016 12:39:14 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF11221A40584eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrDIsWRmVeSWpSXmKPExsUyuXSPt67GAvZwgzkfeSw+PbzEbHFg00FG iwtrhS0uT2pjt1h3+RSbxa2lK1ktlty+x27x+c82RgcOj52z7rJ7tBx5y+qxZMlPJo8vlz+z BbBEcdmkpOZklqUW6dslcGU8uLyOtWDGHMaK7X+72BsYW2YwdjFyckgImEgs+7iOFcIWk7hw bz1bFyMXh5DAUUaJS4sWMEM4yxglvj+8BFbFJmAk8WJjDzuILSLgJbFnyTawDmaBi0wS36Z+ YQJJCAs4Snyff40ZoshJ4sOVxUDNHGD24wOFIGEWARWJEw+OMYGEeQV8JW7eDIXY9YBRYvK+ GWC7OAUCJbqWzAa7lBHouu+n1oCNZxYQl7j1ZD4TxNUCEkv2nGeGsEUlXj7+B/WNksSc1xAn MAvkS7zt2whm8woISpyc+YRlAqPoLCSjZiEpm4WkbBbQecwCmhLrd+lDlChKTOl+yA5ha0i0 zpnLjiy+gJF9FSNHaXFBTm66kcEmRmCcHpNg093BeH+65yFGAQ5GJR7eBQLs4UKsiWXFlbmH GCU4mJVEeLcuAQrxpiRWVqUW5ccXleakFh9ilOZgURLnbQz+FyYkkJ5YkpqdmlqQWgSTZeLg lGpgNH22fE7KWRfFbRY2ZltK98kzLqk+na5WtDpUkW+99Y2KY/kKZl3sfT/qAl9OdLrWwK4Q VCc700Rk9yoTq42PTv6UVXm0TvsFy8TiH/yHZH5yT2LZnu7BIuosu1HKS+TSTTUtFsM5S0sd /MuSxKIfSPROdl6m9uE2Q4979LEq+z2HHFZwCKYpsRRnJBpqMRcVJwIADkxhhM8CAAA=
Archived-At: <>
Cc: "" <>, "" <>, "" <>, "" <>, "" <>
Subject: Re: [mpls] Two new drafts on (micro-)BFD over MC-LAG interfaces
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Multi-Protocol Label Switching WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 08 Apr 2016 12:39:40 -0000

Hi Manav,
thank you for sharing insight view of discussions around RFC 7130, extremely helpful.
We believe, and Jeff is co-author of RFC 7130 too, that MC-LAG presents different case and the compromise that you’ve pointed too is justified. We will add more details on the potential differences between unicast and multicast fast paths in the next update.
We are open to the discussion and always welcome comments and alternative proposals.


From: Manav Bhatia []
Sent: Thursday, April 07, 2016 7:39 PM
To: Mach Chen
Cc: Gregory Mirsky;;;;;; Alia Atlas (
Subject: Re: Two new drafts on (micro-)BFD over MC-LAG interfaces

I believe it had to do with multicast datapath (especially link local) being different from the unicast datapath in most routers. Using link local multicast IP addresses may not necessarily guarantee Unicast IP reachability.

When writing 7130 we spent quite a bit of time ensuring that we dont carve out a special data path for the micro-BFD packets. Using link local would have made it a lot simpler.

And this is where i think the current proposal is flawed -- they use link local multicast to ensure IP unicast reachability which is incorrect.

Cheers, Manav

On Thu, Apr 7, 2016 at 11:16 PM, Mach Chen <<>> wrote:

Hi Greg and all,

I just have quick review on the drafts. If my understanding is correct, the idea is to use multicast destination address other than unicast address when  sending BFD packets over LAG links. And actually this idea has been proposed in (the predecessor of RFC 7130). And at that time, the co-authors of RFC 7130 did discuss the idea of using multicast destination address, but for some reason I forget now(I may need to reiterate the discussions on the archive), the idea was abandoned, although I still think multicast destination address is a smart idea.

Best regards,


From: Rtg-bfd [<>] on behalf of Gregory Mirsky [<>]
Sent: Tuesday, April 05, 2016 6:16
Cc:<>;<>;<>; Alia Atlas (<>)
Subject: Two new drafts on (micro-)BFD over MC-LAG interfaces
Dear All,
two new drafts, related to RFC 7130, were published before the meeting:

•         BFD on MC-LAG interfaces in IP network<>

•         BFD on MC-LAG interfaces in IP/MPLS network<>

Greatly appreciate your reviews, comments, questions and suggestions.