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

Jürgen Schönwälder via Datatracker <noreply@ietf.org> Tue, 17 December 2019 08:05 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 0A8C812097E; Tue, 17 Dec 2019 00:05:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?J=C3=BCrgen_Sch=C3=B6nw=C3=A4lder_via_Datatracker?= <noreply@ietf.org>
To: <ops-dir@ietf.org>
Cc: last-call@ietf.org, rtg-bfd@ietf.org, draft-ietf-bfd-vxlan.all@ietf.org
Subject: Opsdir 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: =?utf-8?b?SsO8cmdlbiBTY2jDtm53w6RsZGVy?= <j.schoenwaelder@jacobs-university.de>
Message-ID: <157656992287.26356.12991667526690255621@ietfa.amsl.com>
Date: Tue, 17 Dec 2019 00:05:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/KxJ4oSiXZw83NYznEBTMiBcZG60>
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 08:05:23 -0000

Reviewer: Jürgen Schönwälder
Review result: Has Nits

I have only a limited understanding of VXLAN and BFD technology.
Hence, some of my question may look odd to the insiders.

- Never	heard of this IPv6 loopback address space before. Is it	OK to
  allocate and use it this way?

- Why is echo BFD outside the scope of this document? Can I just turn
  on echo mode or will extra specifications be needed?

- Nits:

  OLD

    Ability to monitor path continuity

  NEW

    The ability to monitor path continuity

  OLD

    BFD packet MUST be encapsulated

  NEW

    BFD packets MUST be encapsulated