Re: [bess] Comments about draft-gmsm-bess-evpn-bfd-01

Donald Eastlake <> Mon, 05 November 2018 13:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7D7EB128CFD; Mon, 5 Nov 2018 05:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id akIMY_-CuxG5; Mon, 5 Nov 2018 05:48:13 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1232112426A; Mon, 5 Nov 2018 05:48:13 -0800 (PST)
Received: by with SMTP id v11so6455903itj.0; Mon, 05 Nov 2018 05:48:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=q0xfcYgMiKnTgEE2p7kQj160oHWT60itTH1lwwBKQcM=; b=Z0/QhN2IvkBOqU4bfT+B0Mmsee1JeHWM8poXUYN4KLTFW3Ep+s6viVSd33Hk9UFm3V I+nisXgLjDi0ewc0ChP99lqxkAsqU3aM0aifsxFD05SSlFzAprWLjeRGSKkA6lvy5a0D ZR902o5izaEGpC9FpYZVftMbSkiyGWEbvCmi/694EEGuQzhlVyua1BZR7oqMnmGSQhVm SXgnwoQYAM0rSvlOcUqq+w5jjwDNObHolQ1vo9JLod4jtx56uGbwV6PDLB5ou3E+n+rE UEXqyWmEKfHfYqTbAanys2E/xokxxjb81rEwD7TcAk/sGewWUh969zzXa8IU+PHRyqfG 70Ig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=q0xfcYgMiKnTgEE2p7kQj160oHWT60itTH1lwwBKQcM=; b=hSTtAehQm1/qL4hHEu00fhhtJAP5UDBgiZiIMFrcdldidOv98bQBh3oHXVuF6GQGyR gCqpKwYfTOZIFxFDEdSlbHb71PnZXDHwGobnWbbMkcOvt8LJD7cD7+4NFkkQYzjPkPbc 1DwfWHPseUskhK5ONccTw6xzaX8IGRY+6ZPIU8X/7l4oGMfizZb3N7tMhdE0BCKBJcPf Z7FS55NBgYX7sYStSd4FdEOab4KnZ3L431q46/uLpSo7bDv0ThFaNkqGOGCtjnQGwjj6 CnEF59xOeMfJ/GctBxu0Dg1aKC7s7IshqHiFYftPvfsnrU0n10hwjK2o+Qt1/1gKHlh0 wkrA==
X-Gm-Message-State: AGRZ1gKXxfGvCgXyTkGaBG1Nvege6bUTHIvf27+hGCPxCQH/HqmfHwfv yilgOGVIHopKLDKAEc2ng1XxJPWk76/OCAmnrUo=
X-Google-Smtp-Source: AJdET5cc2bxH4NoVVOt+90jThJIXKmxqomyl0kS5EZqPNKSiNzB3NbGtO1YVbZpJS7OY7Ep7IT3EQEkSqjZJKrftSqo=
X-Received: by 2002:a24:ac02:: with SMTP id s2-v6mr6422671ite.105.1541425692124; Mon, 05 Nov 2018 05:48:12 -0800 (PST)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Donald Eastlake <>
Date: Mon, 5 Nov 2018 08:48:00 -0500
Message-ID: <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [bess] Comments about draft-gmsm-bess-evpn-bfd-01
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 05 Nov 2018 13:48:15 -0000

Hi Jorge,

On Mon, Nov 5, 2018 at 4:44 AM Rabadan, Jorge (Nokia - US/Mountain
View) <> wrote:
> Dear authors,
> I couldn’t make it to the BESS meeting, so my apologies if some of these things have been discussed.
> Some comments/questions:

Thanks for sending comments.

> - In the last IETF, I suggested the use of BGP and the BGP-BFD attribute to exchange discriminators, as in section 3.1.6 of draft-ietf-bess-mvpn-fast-failover. The idea seemed to be accepted, but it is not in the new version. This would allow the signaling of the discriminators along with MAC/IP routes, IMET routes, AD per-EVI routes, IP-Prefix routes, etc. without the burden of having to support the EVPN LSP-ping draft.

There is a draft version -02 in the works intended to include
distribution of BFD discriminators in BGP but this revision was not
completed to the agreement of the authors in time to posted before
this meeting.

> - The draft describes an encapsulation and an alternative encapsulation. Is the intend to keep both? Wouldn't be better to leave only one to ease implementations and interoperability?

Currently, the candidate version -02 draft dispenses with with the
alternative encapsulation.

 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 1424 Pro Shop Court, Davenport, FL 33896 USA

> Thank you.
> Jorge