Genart telechat review of draft-ietf-bfd-vxlan-09

Erik Kline via Datatracker <noreply@ietf.org> Tue, 17 December 2019 05:19 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: rtg-bfd@ietf.org
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD231200CD; Mon, 16 Dec 2019 21:19:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: last-call@ietf.org, rtg-bfd@ietf.org, draft-ietf-bfd-vxlan.all@ietf.org
Subject: Genart telechat review of draft-ietf-bfd-vxlan-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.113.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <157655999615.24604.538120700710888094@ietfa.amsl.com>
Date: Mon, 16 Dec 2019 21:19:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/oTgWVLUcl8EExw4amvn7jOXAWy8>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 17 Dec 2019 05:19:56 -0000

Reviewer: Erik Kline
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-bfd-vxlan-??
Reviewer: Erik Kline
Review Date: 2019-12-16
IETF LC End Date: None
IESG Telechat date: 2019-12-19

Summary:

-09 addresses my concerns from -07.  Thank you for this.

The one "nit" is that it seems to have introduced a recommendation to use
::ffff:7f00:0/104 as an IPv6 loopback prefix.  (a) This document should follow
the format recommendations of RFC 5952 section 4.3 and lowercase the "F"s.  But
(b) more importantly, I'm not sure how implementations may treats this space.

The use of an RFC4291 section-2.5.5.2 mapped v4 address doesn't necessarily
make the packet a part of an IPv6 connection.  Nevertheless, I'm not sure I
have a strong feeling about this as it may still exercise enough of the IPv6
stack in a VTEP.

I definitely do think that in the case of BFD on the management VNI targeting
an IPv6 link-local address of the VTEP would be better.  However, I expect that
if ::ffff:127.0.0.0 does prove to have some issues in the future a -bis can be
written quickly with a recommendation.

Also, Suresh may have ideas for a solution.

Major issues:

Minor issues:

Nits/editorial comments: