Re: New Version Notification for draft-ietf-bfd-vxlan-08.txt

Anoop Ghanwani <anoop@alumni.duke.edu> Fri, 01 November 2019 23:24 UTC

Return-Path: <ghanwani@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 B7524120861; Fri, 1 Nov 2019 16:24:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level:
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 WosGo2C-14EQ; Fri, 1 Nov 2019 16:24:19 -0700 (PDT)
Received: from mail-ua1-f49.google.com (mail-ua1-f49.google.com [209.85.222.49]) (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 86696120074; Fri, 1 Nov 2019 16:24:19 -0700 (PDT)
Received: by mail-ua1-f49.google.com with SMTP id l38so3400116uad.4; Fri, 01 Nov 2019 16:24:19 -0700 (PDT)
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=ItOmQscO9eMLJrUjca2bfCeriU9efWxllLsWas+OKNg=; b=kOpEk0fKismBA7bMa23VTN2OkCA5cjmo9zUR/sD5eKYTiAev+WeF2EtOgeQzLa5qFV PuRqreYz91wQoajZ1zuYK+9bZiiKAGjzYH0RxQfqQOVCssDTldMPWQRBfDufkWGiiYGL kc2nnuACzUMb/s3+olCfOtzjEW/9GJn5+6FTfO91YqMaBJ1jXHGBy9orSm5GB+qS548t u5Idf9zm9MZR8cjruBTrUjZN3oTkkU9QghvaGifMLvesTeY2+UsHYpvdDsdLMs+wgLVZ GGhO3u2+78Q1swRwJt7Ik+AXuI2mvNqO15OjUNRw2fAzmxveXKFgssw/sBGb4s4RoA+e 2Txw==
X-Gm-Message-State: APjAAAXeL+Ud59oFZ9IzxM/U4RpswzMLx69Bhc1QaYCfafvZm2VV4+RZ FPslO3Yg3pzo8Ca1Dpdbg/NXfhVqKfzXTt2+T8o=
X-Google-Smtp-Source: APXvYqwHKOjlJUAZnUvMG3d8Ujw4HuJBvnplKRYu9R9qD27+xkf9nH2Vv47WCEucJeWlWQN0OKbZ1oZEkTn6cNmwRd4=
X-Received: by 2002:a9f:23ea:: with SMTP id 97mr6597912uao.141.1572650658471; Fri, 01 Nov 2019 16:24:18 -0700 (PDT)
MIME-Version: 1.0
References: <157263030423.31830.4277364795812171214.idtracker@ietfa.amsl.com> <CA+RyBmUn2zSME51_rDW+y-GdWTmOXQiV7BKkRbNwcy12q8ZjxA@mail.gmail.com>
In-Reply-To: <CA+RyBmUn2zSME51_rDW+y-GdWTmOXQiV7BKkRbNwcy12q8ZjxA@mail.gmail.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
Date: Fri, 1 Nov 2019 16:24:07 -0700
Message-ID: <CA+-tSzxvknwYwvh-s-UK_C7YoF04eiFhyBvVxoNmT=52=EUnWw@mail.gmail.com>
Subject: Re: New Version Notification for draft-ietf-bfd-vxlan-08.txt
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: rtg-bfd WG <rtg-bfd@ietf.org>, NVO3 <nvo3@ietf.org>, Dinesh Dutt <didutt@gmail.com>, Joel Halpern <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary="000000000000daa546059651431a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/-Yg1p2bvs4IQuSNhTW0aNF92nH4>
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: Fri, 01 Nov 2019 23:24:22 -0000

Hi Greg,

A few comments.

The draft has nits, specifically around the way the IPv6 address is written.

In section 4:

BFD packet MUST be encapsulated ->

BFD packets MUST be encapsulated


>>>

Destination MAC: This MUST NOT be of one of tenant's MAC
         addresses.  The destination MAC address MAY be the address
         associated with the destination VTEP.  The MAC address MAY be
         configured, or it MAY be learned via a control plane protocol.
         The details of how the MAC address is obtained are outside the
         scope of this document.

>>>
It looks like we have removed the option of using a well-known IANA
assigned MAC.  If so, why is the above a MAY and not a MUST?  What else can
it be?  One interpretation is that it can be anything unicast, or
multicast, as long as it's not a tenant MAC.  Is that the intent?  If so,
it would be better to state it that way.  Also (and this is purely
editorial), I think it would be better if the first sentence above were
moved to the end of the paragraph.

"The inner Ethernet frame carrying the BFD
   Control packet- has the following format:"

Extraneous '-' after packet.

Thanks,
Anoop

On Fri, Nov 1, 2019 at 10:53 AM Greg Mirsky <gregimirsky@gmail.com>; wrote:

> Dear All,
> the new version includes updates resulting from the discussions of Joel's
> comments in the RtrDir review of BFD over VXLAN draft, comments from Anoop,
> and Dinesh. On behalf of editors, thank you for your constructive comments
> and for sharing your expertise, all much appreciated.
> I hope we've addressed all your comments, and the draft can proceed
> further.
>
> Regards,
> Greg
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>;
> Date: Fri, Nov 1, 2019 at 10:45 AM
> Subject: New Version Notification for draft-ietf-bfd-vxlan-08.txt
> To: Gregory Mirsky <gregimirsky@gmail.com>;, Mallik Mudigonda <
> mmudigon@cisco.com>;, Sudarsan Paragiri <sudarsan.225@gmail.com>;, Vengada
> Prasad Govindan <venggovi@cisco.com>;, Santosh Pallagatti <
> santosh.pallagatti@gmail.com>;
>
>
>
> A new version of I-D, draft-ietf-bfd-vxlan-08.txt
> has been successfully submitted by Greg Mirsky and posted to the
> IETF repository.
>
> Name:           draft-ietf-bfd-vxlan
> Revision:       08
> Title:          BFD for VXLAN
> Document date:  2019-11-01
> Group:          bfd
> Pages:          11
> URL:
> https://www.ietf.org/internet-drafts/draft-ietf-bfd-vxlan-08.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-bfd-vxlan/
> Htmlized:       https://tools.ietf.org/html/draft-ietf-bfd-vxlan-08
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-bfd-vxlan
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-bfd-vxlan-08
>
> Abstract:
>    This document describes the use of the Bidirectional Forwarding
>    Detection (BFD) protocol in point-to-point Virtual eXtensible Local
>    Area Network (VXLAN) tunnels forming up an overlay network.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>