BFD Echo mode coverage in BFD for VXLAN

Greg Mirsky <> Mon, 05 August 2019 22:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8466512009C; Mon, 5 Aug 2019 15:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QyF2Nj8nmFUv; Mon, 5 Aug 2019 15:16:16 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 17F1F120073; Mon, 5 Aug 2019 15:16:16 -0700 (PDT)
Received: by with SMTP id b29so52039104lfq.1; Mon, 05 Aug 2019 15:16:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=X2NC7BhKP2CYpHmS4YmzpgqGM7cFG3M/os+8DZxjAnw=; b=iG6HtTbzGkglmyYCE1BHdaCwrnquWGxhFW72PWKTDRehUHBNMFjlqOcZqav6daza9M 7fzOLbEFHLJZPCZSMY7XJ7zYhTJhW7UT6EmfMiL/Byh1T8JBJXFkzz2/MCYm4oUXlwJ8 vGDWzUwwYz0AIUsfe/MCKyzeKs9sLpx0yBW2pga8OgYcBUXGalQYdjgB/JPr15JHo4a2 FchBYRXDNYrOBwjD7hT3fuAAa7eotENjlInBMCJNouwlRXhsPDns3FOBjm/BeKdRpJQg 1J/4RsBQUkC3cAZs+IuZkAoBi/UJ0DxQQuv6poOjpDYQFXnRxFFSXp2s0dn6zbO61FhG dQUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=X2NC7BhKP2CYpHmS4YmzpgqGM7cFG3M/os+8DZxjAnw=; b=dSKANKeZL0PhoohhVuuuLHMKp2gfQDTZvLhZ8PtcgO76H6hK38FM3f2ur+zAcTfAaK iBDnJqUMiCGOQgVyS7VmB7DAtz1oYa4Kb9mp417G1dOKUU/PGjg0BrrwXPDunC8AyEd4 0xhV+1KZMD+l1LZUqyfRrP/eo4LoduAPXQXj0yXhegUzqgdwHUGWQ+SKjovQmwXk9f8J DkpZVF0zoriVrIeO8UOyKo/PirbyYicg42W5sx51s/t8/KGQwKbVEBV18XSNO2dOgWeF ky3pKzRDj7f1BzuqWE937e671m+QpMT2qcN9NxGmgorW/CScrJvEgRkA/FblziJ2IOXs HOxw==
X-Gm-Message-State: APjAAAVmNuot/h2ivvDm5aEbObn3iisfr8HYwPN9DtOm5oYXUN6ErQ/R Mn4YYPNY5iZm5XNGyMMffRDwKdcpixIxrooB6K2k0DTS
X-Google-Smtp-Source: APXvYqxAXz2NOdFtmF/IxxWgoXINFuwJZJLIO0lWVb4WQWg1XvIYyPiKAERtp1/TLLviXMxGaNtLKYvVumauaHa6Ee0=
X-Received: by 2002:a19:cbc4:: with SMTP id b187mr6533852lfg.27.1565043373990; Mon, 05 Aug 2019 15:16:13 -0700 (PDT)
MIME-Version: 1.0
From: Greg Mirsky <>
Date: Mon, 05 Aug 2019 15:16:03 -0700
Message-ID: <>
Subject: BFD Echo mode coverage in BFD for VXLAN
To: rtg-bfd WG <>,, Martin Vigoureux <>, "Carlos Pignataro (cpignata)" <>
Content-Type: multipart/alternative; boundary="0000000000005d6797058f660e71"
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 05 Aug 2019 22:16:18 -0000

Dear All,
in course of reviews of the draft, several times a question was asked about
the rationale for excluding BFD Echo from the scope of this document:

7.  Echo BFD

   Support for echo BFD is outside the scope of this document.

Much appreciate your consideration of the following options:

   - describe the applicability of BFD Echo in VXLAN environment in the
   - remove Section 7 and clarify in the Introduction


This specification describes procedures only for BFD Asynchronous mode.

   - make no changes at all.