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

Jeffrey Haas <jhaas@pfrc.org> Mon, 10 August 2020 19:42 UTC

Return-Path: <jhaas@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 594CE3A0C67; Mon, 10 Aug 2020 12:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 WBgEht_Ha5s6; Mon, 10 Aug 2020 12:42:38 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id C11003A0C64; Mon, 10 Aug 2020 12:42:37 -0700 (PDT)
Received: from dresden.attlocal.net (99-59-193-67.lightspeed.livnmi.sbcglobal.net [99.59.193.67]) by slice.pfrc.org (Postfix) with ESMTPSA id 9A0161E342; Mon, 10 Aug 2020 15:54:17 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_2E07E1AF-104A-4429-ADC0-DC95BE608569"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: BFD for vxlan Destination MAC field (was Re: draft-ietf-bfd-vxlan IESG status)
From: Jeffrey Haas <jhaas@pfrc.org>
In-Reply-To: <CA+RyBmXrNWXHMCSVaKNxKh=jDDy6OpbwS9P=0Wy4+35iVrE+5w@mail.gmail.com>
Date: Mon, 10 Aug 2020 15:42:36 -0400
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>
Message-Id: <B7494732-685B-4C57-B117-173D249496D9@pfrc.org>
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> <CA+RyBmXrNWXHMCSVaKNxKh=jDDy6OpbwS9P=0Wy4+35iVrE+5w@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/yzkFcmAsGGMeBakpLDJWYDgfTq0>
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:42:41 -0000

Greg,

Sorry, I was looking at two messages back to back.  From a unicast from Donald:

> I'm still working on catching up on the MAC address aspects of this
> discussion so this message may have been overcome by events.
> 
> But individual MAC addresses are abundant. I received a request from
> IANA in connection with the -07 version of this draft on 22 May 2019
> (yes 2019). I reviewed the draft the same day and sent back an
> approval to IANA to assign a MAC address in which I suggested the
> value 00-00-5E-00-52-02 which is still available according to the IANA
> registry. Presumably IANA will make that assignment as soon as the
> IESG approves the draft.



-- Jeff


> On Aug 10, 2020, at 3:38 PM, Greg Mirsky <gregimirsky@gmail.com> wrote:
> 
> 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 <mailto: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 <mailto: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 <mailto:d3e3e3@gmail.com>
> > 
> > On Thu, Jul 30, 2020 at 7:55 PM Greg Mirsky <gregimirsky@gmail.com <mailto: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 <mailto: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 <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
>