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

Greg Mirsky <gregimirsky@gmail.com> Mon, 20 July 2020 23:18 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 86C1A3A092F; Mon, 20 Jul 2020 16:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.696
X-Spam-Level:
X-Spam-Status: No, score=-0.696 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_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, 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 hUvCwSVlWqKn; Mon, 20 Jul 2020 16:18:37 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 7C8DB3A092D; Mon, 20 Jul 2020 16:18:36 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id b30so8339652lfj.12; Mon, 20 Jul 2020 16:18:36 -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=NqUD3oWYYvKgOBem6f0YKfQQNXJi3sq3iX8mwlyIEjo=; b=GGg1AB9uscq5Dc+PHlWTHUGipfep69I7+mTx270QcZWAEnjCMbIkfJaarrm+qW/8lf gcUkCGvZBbzCJwBQvkbidEKMs48/q6wXrRFCEzp4ZnVT1ufKlq+pMoYeMYTWLbvVIhKx PzMuabkCMhOxrcgn9DAjb/J7J4F9TeNFEzwxNRvjUv/jEZcMPAqen4qRkRN45OAff4s4 NEDp2F6Hwpq3OtMQpN2wqdy1OE7TE67sCqtVdjW8AEEDZ/Dl17ezw4yQs55ufAMla5a0 L8wMKWSKqh9SzPzISehlS4PXXR44ASCLuG3pbZvqSHUbCIUE7E8AlZgYe95d+3vgwQjn hjlQ==
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=NqUD3oWYYvKgOBem6f0YKfQQNXJi3sq3iX8mwlyIEjo=; b=mYkh890V/1rZeSBx7wYNn9ola3UFE7zREScBAOlIHRvdCIFj0NGf4PLT0n/gtmKyP4 l0qkZ/CmL8+B9ZClYV1sOLIyKWI9GYhIcI1FgwrFurUhtFM0shUHTs4isTgIRSgJdMTh cNWat3xx5qLiYeltvoml0rFKr90NKnMzbKjY8qbuOZRqrXhW88SNP60ZGFv9MlcnGc9b ZHAaQdpXbepYOP0BWKm8owAMX9wBovxYxLy/tgy1cGqTyU82rfZGrre7Pw/i84YSZ+X9 tIRALzdkNyexHMB+2oB4TwxGIz1b5sZpmStJn4fO6Dzti0vIB9eHYqX3uozMR1hMFhFs grVA==
X-Gm-Message-State: AOAM530Eh09q+KN0lH7XfvFUSA0xR7NH3HMgORlXMOwNUDoo29heSdmZ XqLONntQyONHBplmelQzAwfkMraPqBWK7oRqZCQ=
X-Google-Smtp-Source: ABdhPJye5BuMtr6ZeOp76WhdiMbU5n04Hc8y78CkIg+0V6ebRmxjAfD9NJoVa8MmOkHsmu0ulTlJaQUa+YcUJ2NlHvY=
X-Received: by 2002:ac2:51c6:: with SMTP id u6mr11401020lfm.123.1595287114556; Mon, 20 Jul 2020 16:18:34 -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 16:18:23 -0700
Message-ID: <CA+RyBmWwn--zB4xEBtmpeG+XSqSd35+nT0OKSxsbnOEBEnP0ng@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/mixed; boundary="000000000000c7471505aae7b988"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/pNh4zKTR03PtQPqr927mj3h3oqA>
X-Mailman-Approved-At: Mon, 20 Jul 2020 16:32:37 -0700
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 23:18:41 -0000

Hi Jeff, et al.,
attached please find the new working version of BFD over VXLAN and its diff
to -13.
Please let me know if you have any questions.

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
>