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 <[email protected]> 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: <[email protected]>
> Date: Fri, Nov 1, 2019 at 10:45 AM
> Subject: New Version Notification for draft-ietf-bfd-vxlan-08.txt
> To: Gregory Mirsky <[email protected]>, Mallik Mudigonda <
> [email protected]>, Sudarsan Paragiri <[email protected]>, Vengada
> Prasad Govindan <[email protected]>, Santosh Pallagatti <
> [email protected]>
>
>
>
> 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
>
>
