Re: BFD over VXLAN: Trapping BFD Control packet at VTEP

"Joel M. Halpern" <> Wed, 31 July 2019 18:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B51981201CE; Wed, 31 Jul 2019 11:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WBNWiWzlpiQB; Wed, 31 Jul 2019 11:05:51 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4815B12017C; Wed, 31 Jul 2019 11:05:51 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 45zLvM141hzKm71; Wed, 31 Jul 2019 11:05:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=2.tigertech; t=1564596351; bh=gSqIgmRRFGMpJmVMUro/HCzfA/axVGvGU5pRWSeIGnw=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=RjJmpDYh4p7sUzs7oiynKmaAqCCC2XP1hORG5qxPDWOH5DeeeDTt8/WxQfUtvSyj8 G8TgaXSqZ/ODwD3VhkcdKui9ZzhYdS2zbezS78VLGj4fZF8zB2f9youEz0bCVcYxeX dzVCYUVCitR8y2VLqhVpERO4WO8orlCOyX1jAyL0=
X-Virus-Scanned: Debian amavisd-new at
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 45zLvL0djTz1P8xp; Wed, 31 Jul 2019 11:05:50 -0700 (PDT)
Subject: Re: BFD over VXLAN: Trapping BFD Control packet at VTEP
To: Greg Mirsky <>, rtg-bfd WG <>, "T. Sridhar" <>, Dinesh Dutt <>,, Martin Vigoureux <>
References: <>
From: "Joel M. Halpern" <>
Message-ID: <>
Date: Wed, 31 Jul 2019 14:05:49 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
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: Wed, 31 Jul 2019 18:05:53 -0000

I made the mistake of assuming we were in agreement.
What Greg has proposed below makes very good sense to me.

Thank you Greg.

On 7/31/2019 8:48 AM, Greg Mirsky wrote:
> Dear All,
> thank you for your comments, suggestions on this issue, probably the 
> most challenging for this specification. In the course of our 
> discussions, we've agreed to abandon the request to allocate the 
> dedicated MAC address to be used as the destination MAC address in the 
> inner Ethernet frame. Also, earlier using VNI 0 was changed from 
> mandatory to one of the options an implementation may offer to an 
> operator. The most recent discussion was whether VTEP's MAC address 
> might be used as the destination MAC address in the inner Ethernet 
> frame. As I recall it, the comments from VXLAN experts equally split 
> with one for it and one against. Hence I would like to propose a new 
> text to resolve the issue. The idea is to let an operator select 
> Management VNI and use that VNI in VXLAN encapsulation of BFD Control 
> packets:
>     An operator MUST select a VNI number to be used as Management VNI.
>     VXLAN packet for Management VNI MUST NOT be sent to a tenant. VNI
>     number 1 is RECOMMENDED as the default for Management VNI.
> With that new text, what can be the value of the destination MAC in the 
> inner Ethernet? I tend to believe that it can be anything and ignored by 
> the reciever VTEP. Also, if the trapping is based on VNI number, the 
> destination IP address of the inner IP packet can from the range 127/8 
> for IPv4, and for IPv6 from the range 0:0:0:0:0:FFFF:7F00:0/104. And 
> lastly, the TTL to be set to 1 (no change here).
> Much appreciate your comments, questions, and suggestions.
> Best regards,
> Greg