Last Call Review of draft-ietf-bfd-vxlan-07

Request Review of draft-ietf-bfd-vxlan
Requested rev. no specific revision (document currently at 10)
Type Last Call Review
Team Transport Area Review Team (tsvart)
Deadline 2019-05-31
Requested 2019-05-17
Authors Juniper Networks, Sudarsan Paragiri, Vengada Govindan, Mallik Mudigonda, Gregory Mirsky
Draft last updated 2019-05-31
Completed reviews Rtgdir Last Call review of -07 by Joel Halpern (diff)
Opsdir Last Call review of -07 by Jürgen Schönwälder (diff)
Genart Last Call review of -07 by Erik Kline (diff)
Tsvart Last Call review of -07 by Olivier Bonaventure (diff)
Secdir Last Call review of -07 by Shawn Emery (diff)
Opsdir Telechat review of -09 by Jürgen Schönwälder (diff)
Secdir Telechat review of -09 by Shawn Emery (diff)
Genart Telechat review of -09 by Erik Kline (diff)
Assignment Reviewer Olivier Bonaventure
State Completed
Review review-ietf-bfd-vxlan-07-tsvart-lc-bonaventure-2019-05-31
Posted at
Reviewed rev. 07 (document currently at 10)
Review result Ready with Issues
Review completed: 2019-05-31


This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC if you reply to or forward this review.

I have only limited knowledge of VXLAN and do not know all subtleties of BFD. This review is thus more from a generalist than a specialist in this topic.

Major issues

Section 4 requires that " Implementations SHOULD ensure that the BFD
   packets follow the same lookup path as VXLAN data packets within the
   sender system."

Why is this requirement only relevant for the lookup path on the sender system ? What does this sentence really implies ? 

Is it a requirement that the BFD packets follow the same path as the data packet for a given VXLAN ? I guess so. In this case, the document should discuss how Equal Cost Multipath could affect this.

Minor issues

Section 1

You write "The asynchronous mode of BFD, as defined in [RFC5880],
 can be used to monitor a p2p VXLAN tunnel."

Why do you use the word can ? It is a possibility or a requirement ?

NVE has not been defined before and is not in the terminology.

This entire section is not easy to read for an outsider.

Section 3

VNI has not been defined

Figure 1 could take less space

Section 4

I do not see the benefits of having one paragraph in Section 4 followed by only Section 4.1

Section 4.1

The document does not specify when a dedicated MAC address or the MAC address of the destination VTEP must be used. This could affect the interoperability of implementations. Should all implementations support both the dedicated MAC address and the destination MAC address ?

It is unclear from this section whether IPv4 inside IPv6 and the opposite should be supported or not.

Section 5.

If the received packet does not match the dedicated MAC address nor the MAC address of the VTEP, should the packet be silently discarded or treated differently ?

Section 5.1

Is this a modification to section 6.3 of RFC5880 ? This is not clear

Section 9

The sentence " Throttling MAY be relaxed for BFD packets
   based on port number." is unclear.