Re: BFD for vxlan Destination MAC field (was Re: draft-ietf-bfd-vxlan IESG status)
Greg Mirsky <gregimirsky@gmail.com> Mon, 10 August 2020 19:38 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 3CC7D3A0C5B; Mon, 10 Aug 2020 12:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.097
X-Spam-Level:
X-Spam-Status: No, score=-1.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 LxaHl73sH0MD; Mon, 10 Aug 2020 12:38:56 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 24CD53A0C61; Mon, 10 Aug 2020 12:38:56 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id g6so10875469ljn.11; Mon, 10 Aug 2020 12:38:55 -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=Kh02L1dTW+JRYOvoBzvV5WjZoE4o9SuLgVJiuRbf8DY=; b=PZt4n7ywUspLrIPVjXa+4geHWK0P+iX6p3ILTPakFN5IGLAkNF4mEKORvOCuAMtG7j D+Ifu74jNWBCh6epTns0pMEzkFO9oamamVJFT4HJ1cR5i+RY3GjyPQpssfJeRBVYjj3Q fqk2YgRDin6uaEL3AEsSYPYutxnWQ2V2N5vEBNMlct3JbaKyiTNYgr6kcD0xzdyEgYv9 BJ1+xmbjP6pFAw9EMl9ccY4RuVq8KMjX9wh8r+SlY0ZxIFdwGv5vQQAWl7fBHEffO2P7 zOTGeohcR6jeTzGeg1jxjDpyUHIYmx/teg7/ii8Wsru95S83QSnLcQSsmbyC5QKVrcDq ZMSQ==
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=Kh02L1dTW+JRYOvoBzvV5WjZoE4o9SuLgVJiuRbf8DY=; b=XFhbdA/8NK7YC5rijDSGwYIL5QjmPAUzJgQ2jC33UiXnJXtjK62Mr39mfqljMqJj3Y 85CrzaQyVihw6KaT9GFcuUBusgyEA46lkChRuttqE6XLQXTzra33lStF7X4tapPFcTKL Ir5XJ2NShhSyZ9qWnkl2MxHevX3GoNY388azGPSroNBZ0sHL3/cbRB832Ftkh5lfRyHB vIsqj8NeHLztacb9tKjtfzXXGqQmnMbPatMGcmE1TrZ7CDcvZhiTzIcCNjl8mMsrnqUY SB0FrDOOiJAefIIem5qsvBszOuee4HLbK13+iXlQ2Xaf22G16TlpXktacrX4U8QenBWU RKrA==
X-Gm-Message-State: AOAM531AlXjIvJSpCHEI5qi9ej8HnhRjY4B3DftoRIsolqd36ag9pffx mnuJcdFRRvLnH4ZkDEwWKaMaY1RS0rk5toBRf9T1jeWX
X-Google-Smtp-Source: ABdhPJw4HcOnT1iPewmMu+vic5GoUu69A8sm+IcOydTT0ijXFyuoly15entNGY9uMn/SuDxTP1DWrIRr32BOarWKjP4=
X-Received: by 2002:a2e:752:: with SMTP id i18mr1350570ljd.428.1597088334140; Mon, 10 Aug 2020 12:38:54 -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> <CA+RyBmViC-rxZC=iwAzLAq0YOOo7PT_6fby9mwc0WEM+m4B6TA@mail.gmail.com> <CAF4+nEHAYwveDk0=PQ4Va-0P+Pebgn=PtD+MVXJV7FibSkgUaQ@mail.gmail.com> <FE9B4836-9006-4F2C-8919-7427E08E804E@pfrc.org>
In-Reply-To: <FE9B4836-9006-4F2C-8919-7427E08E804E@pfrc.org>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 10 Aug 2020 12:38:42 -0700
Message-ID: <CA+RyBmXrNWXHMCSVaKNxKh=jDDy6OpbwS9P=0Wy4+35iVrE+5w@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>, draft-ietf-bfd-vxlan@ietf.org, bfd-chairs@ietf.org, rtg-bfd WG <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d4dae105ac8b1aee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/b08STE8UYiYbHB9OvFY5a1fYZ6I>
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, 10 Aug 2020 19:38:59 -0000
Hi Jeff, to update the IANA considerations section by replacing TBD1 with the actual MAC address? I see two small allocation ranges for in the Unicast MAC addresses: 00-52-02 to 00-52-12 Unassigned (small allocations) .... 00-52-14 to 00-52-FF Unassigned (small allocations) Also, can we change the wording in the Reference column from "BFD over VXLAN" to "Control channel in NVO3"? That would be helpful to the work on OAM in Geneve. Regards, Greg On Mon, Aug 10, 2020 at 12:14 PM Jeffrey Haas <jhaas@pfrc.org> wrote: > Thank you, Donald. > > Greg, would you bump the draft with this assignment? > > -- Jeff > > > > On Aug 10, 2020, at 1:08 PM, Donald Eastlake <d3e3e3@gmail.com> wrote: > > > > Hi, > > > > My apologies for not responding earlier in this thread. > > > > IANA originally contacted me as a Designated Expert for MAC addresses > > under the IANA OUI last year in connection with version -07. At that > > time, I approved an assignment for this draft. I'm fine with any > > reasonable usage description the WG comes up with for this MAC address > > whether more or less generic. (Usage of a MAC address reserved for > > documentation would not be appropriate) > > > > Thanks, > > Donald > > =============================== > > Donald E. Eastlake 3rd +1-508-333-2270 (cell) > > 2386 Panoramic Circle, Apopka, FL 32703 USA > > d3e3e3@gmail.com > > > > On Thu, Jul 30, 2020 at 7:55 PM Greg Mirsky <gregimirsky@gmail.com> > wrote: > >> > >> Hi Jeff, > >> do you think that the record in the Usage filed for the requested MAC > address instead of "BFD over VXLAN" be more generic, e.g., "Active OAM over > NVO3"? > >> What do you think? > >> > >> 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 > >
- 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