BFD for vxlan Destination MAC field (was Re: draft-ietf-bfd-vxlan IESG status)
Jeffrey Haas <jhaas@pfrc.org> Mon, 20 July 2020 21:26 UTC
Return-Path: <jhaas@slice.pfrc.org>
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 C95E13A0FA2; Mon, 20 Jul 2020 14:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D3refhEMkmBh; Mon, 20 Jul 2020 14:26:51 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 235F93A0FA3; Mon, 20 Jul 2020 14:26:50 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 26F251E2FB; Mon, 20 Jul 2020 17:37:35 -0400 (EDT)
Date: Mon, 20 Jul 2020 17:37:35 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Greg Mirsky <gregimirsky@gmail.com>, Donald Eastlake <d3e3e3@gmail.com>
Cc: The IESG <iesg@ietf.org>, bfd-chairs@ietf.org, draft-ietf-bfd-vxlan@ietf.org, rtg-bfd WG <rtg-bfd@ietf.org>
Subject: BFD for vxlan Destination MAC field (was Re: draft-ietf-bfd-vxlan IESG status)
Message-ID: <20200720213734.GC25102@pfrc.org>
References: <20200127221705.GB17622@pfrc.org> <20200616211057.GA21373@pfrc.org> <CA+RyBmXk_-gnuyUYwbSwkfiBSvUnX77G2m5M4bkDsYQiHYjqbw@mail.gmail.com> <E2C152D4-AA4C-4CC8-BAD1-13FF007552E6@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E2C152D4-AA4C-4CC8-BAD1-13FF007552E6@pfrc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/7mvYRFFJJeKjCiDn3Hl0Y8YM01o>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 20 Jul 2020 21:26:53 -0000
On Wed, Jun 17, 2020 at 03:52:14PM -0400, Jeffrey Haas wrote: > >> Proposed solution: A MAC value should be chosen that is well known and the > >> text would become: > >> > >> "Destination MAC: A Management VNI, which does not have any tenants, will > >> have no dedicated MAC address for decapsulated traffic. The value > >> X:X:X:X:X > >> SHOULD be used in this field." > >> > >> SHOULD might need to be MUST. Since a partial motivation for permitting > >> the > >> flexibility in the specification to NOT use the management VNI is desired= > > , > >> MUST might be inappropriate. > >> > > GIM>> Accepted the suggested text. I agree that the flexibility to not use > > the Management VNI is permitted in the specification and thus SHOULD in the > > text is consistent with that scenario. How would we pick the MAC address? > > I am out of my area of expertise and I was hoping someone in the IESG can offer a fix. :-) I am copying Donald Eastlake since he's the designated expert for the IANA MAC address block. > > Donald, review of the thread may be useful, but tersely the need is to have a well known MAC address that can be placed in this vxlan PDU that is literally a placeholder of "not to be used for forwarding". The packet arrives at the endpoint and, if not immediately accepted, would be dropped. > > If there is no well known MAC that could be used for such a behavior, perhaps an address from the IANA block may be used? > > While I suspect the IANA mac documentation range could be used, IANA may not appreciate that. Donald is not responding to emails. Considering I've been similarly bad about responding, that's forgivable. However, in the interest of advancing the document, I'd like to make a proposal. https://www.iana.org/assignments/ethernet-numbers/ethernet-numbers.xhtml Proposed text: : Destination MAC: A Management VNI, which does not have any tenants, will : have no dedicated MAC address for decapsulated traffic. The value : [TBD1] SHOULD be used in this field. : : IANA Considerations: : : IANA is requested to assign a single MAC address to the value TBD1 from the : "IANA Unicast 48-bit MAC Address" registry from the "Unassigned (small : allocations)" block. The Usage field will be "BFD for vxlan" with a : Reference field of this document. -- Jeff
- Alvaro Retana's Discuss on draft-ietf-bfd-vxlan-0… Alvaro Retana via Datatracker
- Re: Alvaro Retana's Discuss on draft-ietf-bfd-vxl… Greg Mirsky
- Re: Alvaro Retana's Discuss on draft-ietf-bfd-vxl… Alvaro Retana
- Re: draft-ietf-bfd-vxlan IESG status Greg Mirsky
- Re: draft-ietf-bfd-vxlan IESG status Greg Mirsky
- draft-ietf-bfd-vxlan IESG status Jeffrey Haas
- Re: draft-ietf-bfd-vxlan IESG status Greg Mirsky
- Re: draft-ietf-bfd-vxlan IESG status Alvaro Retana
- Re: draft-ietf-bfd-vxlan IESG status Greg Mirsky
- Re: draft-ietf-bfd-vxlan IESG status Jeffrey Haas
- Re: draft-ietf-bfd-vxlan IESG status Greg Mirsky
- Re: draft-ietf-bfd-vxlan IESG status Benjamin Kaduk
- Re: draft-ietf-bfd-vxlan IESG status Alvaro Retana
- Re: draft-ietf-bfd-vxlan IESG status Greg Mirsky
- Re: draft-ietf-bfd-vxlan IESG status Jeffrey Haas
- Re: draft-ietf-bfd-vxlan IESG status Alvaro Retana
- Re: draft-ietf-bfd-vxlan IESG status Greg Mirsky
- Re: draft-ietf-bfd-vxlan IESG status Greg Mirsky
- BFD for vxlan Destination MAC field (was Re: draf… Jeffrey Haas
- Re: draft-ietf-bfd-vxlan IESG status Jeffrey Haas
- Re: BFD for vxlan Destination MAC field (was Re: … Greg Mirsky
- Re: BFD for vxlan Destination MAC field (was Re: … Greg Mirsky
- Re: BFD for vxlan Destination MAC field (was Re: … Greg Mirsky
- Re: BFD for vxlan Destination MAC field (was Re: … Donald Eastlake
- Re: BFD for vxlan Destination MAC field (was Re: … Jeffrey Haas
- Re: BFD for vxlan Destination MAC field (was Re: … Greg Mirsky
- Re: BFD for vxlan Destination MAC field (was Re: … Jeffrey Haas
- Re: BFD for vxlan Destination MAC field (was Re: … Donald Eastlake
- Re: BFD for vxlan Destination MAC field (was Re: … Greg Mirsky