Re: BFD for vxlan Destination MAC field (was Re: draft-ietf-bfd-vxlan IESG status)

Greg Mirsky <gregimirsky@gmail.com> Mon, 20 July 2020 22:28 UTC

Return-Path: <gregimirsky@gmail.com>
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 E2A223A1048; Mon, 20 Jul 2020 15:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 jKxbtampVl8Q; Mon, 20 Jul 2020 15:28:49 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0F4A3A1046; Mon, 20 Jul 2020 15:28:48 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id f5so21934296ljj.10; Mon, 20 Jul 2020 15:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ChJKODLbwy7cyK21Po13gSX+MGKuXHHcbayDtiy4EXE=; b=sOuB7YQ2QSb5W278au535tiM8wXEBBX9xVtYfREIw008+5bB8bNpYCFnstSr3PlBrs kT/FN3Ew1e+IdNU5Oh3hh//U9o1VjUYWQuzIQp7OeLzrFPtfUd/MnFoQY++kQgCV36s2 Uy0gi85l/FW4tVxV3thX5scoUURaczGjjSWcYJCY8X6R0PkvuUtY9c/+rpZ1k4N+CpE1 h3BgHM0VJZngSiOTTZzB6XvA5q4QkC/3dKkw320/1huI9f+qNkUpwihquiCRhR+uQd+8 ExbTUFjzaB8bvH3jJvqjNACbOw79oGSG2JNvjDQPXDzAe6emL5/6n3bUAfUGv/j0Mzis V65Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ChJKODLbwy7cyK21Po13gSX+MGKuXHHcbayDtiy4EXE=; b=SfVPnBMk7cehdj873vf8ofY09JtpHjLnMkek9YWqRe3IhuPsZbMBqAdtyJ6gOIIuXU yyEZUZn4okq4wkuJL3HGjIwf8yPIuGPY/pa5GYKHUYdTh/d9rQ9u6AOD3L/ka2/nWLJa 1vaNbv8fa42t2OZAmnkQJy/r/r139mtoUtU8S7Vrfgj0gDAgziSV/aCn31xf3GfS9jDH 8+akgtUNNkFY+fnQBcJ4wJTKm5f6wLJUCp23lOtAuerrw6k/mbt4xxhnXf25Sq+qEWuP P0D8JMF+uN03EP/XUdo1tiwkrdL6xvtW1XykZzDe35cWQnlNlDpsvzkAvuRTCnP+fkte DINA==
X-Gm-Message-State: AOAM531UPT0jBicJo593/gRwItelCThQXlF18U1RA/CbdPuo2ag8ZM3r svKH9JrjIc31TCs0tkJjQdbrrXNpjS7Jy/ev6yQ=
X-Google-Smtp-Source: ABdhPJzGNCgzMkQnUurn7ZYNmbsRh9AOQsOaSpTXnuxkZpp/c6mWWmU8nzjYe/WYgprpv4gJAnWfwgtMrkJS+BCWtrw=
X-Received: by 2002:a2e:b00a:: with SMTP id y10mr667335ljk.266.1595284127075; Mon, 20 Jul 2020 15:28:47 -0700 (PDT)
MIME-Version: 1.0
References: <20200127221705.GB17622@pfrc.org> <20200616211057.GA21373@pfrc.org> <CA+RyBmXk_-gnuyUYwbSwkfiBSvUnX77G2m5M4bkDsYQiHYjqbw@mail.gmail.com> <E2C152D4-AA4C-4CC8-BAD1-13FF007552E6@pfrc.org> <20200720213734.GC25102@pfrc.org>
In-Reply-To: <20200720213734.GC25102@pfrc.org>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 20 Jul 2020 15:28:36 -0700
Message-ID: <CA+RyBmUssQ=ZkXraAi6gdxg3DokCTDBQV82nAOy3eVCnTbGmaA@mail.gmail.com>
Subject: Re: BFD for vxlan Destination MAC field (was Re: draft-ietf-bfd-vxlan IESG status)
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: Donald Eastlake <d3e3e3@gmail.com>, The IESG <iesg@ietf.org>, bfd-chairs@ietf.org, draft-ietf-bfd-vxlan@ietf.org, rtg-bfd WG <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b5d01805aae70735"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/J6YFMKwZD7IjilC9VwMkAhvVdcM>
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 22:28:51 -0000

Hi Jeff,
thank you for the proposed text. I'll include it in the working version
with capitalizing VXLAN in the IANA section).

Regards,
Greg

On Mon, Jul 20, 2020 at 2:26 PM Jeffrey Haas <jhaas@pfrc.org> wrote:

> 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
>