Update to BFD over VXLAN

Greg Mirsky <gregimirsky@gmail.com> Wed, 20 November 2019 02:42 UTC

Return-Path: <gregimirsky@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 6EC771201EF; Tue, 19 Nov 2019 18:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.596
X-Spam-Level:
X-Spam-Status: No, score=-0.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 vxesKSMYFy_U; Tue, 19 Nov 2019 18:42:00 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 D8F831201E0; Tue, 19 Nov 2019 18:41:59 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id d6so18853575lfc.0; Tue, 19 Nov 2019 18:41:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=6tSMg4LZCvRFYPqpSou/YN1Xv82VXsjxLPlcrjVa1gw=; b=dZBuYMCoB/rGcMPWiMKGH4Ib9jJ8FIBU0SuDovfbthRBgHMt4d3kIDHXLvjqLaN0bJ I1HRbHyG75132OicNaPEpN921gtLhoACa2Gy0ov6JfzoNZ29ntc6ju5cegdqWEdWqJsK F2C1ePKFhYt7cWoWOxxGMgYP1TYlkW+W4YD5QwGkiZ7+ed8tJLO7pQ5Y0ITYsPF5kfYe gaj678SZFxp0ajcxAkAiIzyfuKOvD7G2vYzOBo0RXe/n0kXchDOKN2VONX5PQjQ3D6Gu nt6gI0pwwULwZH9vZP74gKuAoAzijPE06SDIGGNT4wpc8Xt3ChaxFG5Su/vvVG70nUiK AXnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6tSMg4LZCvRFYPqpSou/YN1Xv82VXsjxLPlcrjVa1gw=; b=dxr/e1/D+TEYNeVGpakMUwVQo/kLuzzAHpDGQhF/9vtcqIsRkrMfQ6t3pkyP+ltXuj 5Ao2PGcvpcakGJJDIZ8Jxqqlg0M1IYS1Y3keElsGCY7y2dNSah7sX0gWtMfRgiSEIJWn hTgkMg78mL7R8x0FBIpgCoHvcsU6htBvJD5WeGgHrgrT2v/wrCpxTjB2Lo46wnDh7/0g K+56bUCaXCbtEK4FwsXCudncu6V95uEH4pzydU6UmHxOmSjbBFPdRh+VHp3SmTW+BbzB gZY+FStdY2cJS3t7STpERT+WfPmRTuQhXaI1nvzNIDyvGJxQCvTHg3DAodABGuR8TaH7 FAOA==
X-Gm-Message-State: APjAAAXgb0eIYc9hwbBYMyjvqqoit/dWRTTZ8rBoXKczXELQrbEUA8K+ CbqEime7g0xx/iRivDf96xQzPQzif38HrAemN6NHRLZJDKI=
X-Google-Smtp-Source: APXvYqyORqz9e1GO6nCawXrJb8pu8lfoJ47h/SjiJsFC0dsMBSX/SYTJKQokzEPTp8wCSsOPbFbS4xke6mQSvvCD5sY=
X-Received: by 2002:a05:6512:486:: with SMTP id v6mr536138lfq.72.1574217717651; Tue, 19 Nov 2019 18:41:57 -0800 (PST)
MIME-Version: 1.0
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 20 Nov 2019 10:41:46 +0800
Message-ID: <CA+RyBmWaeTZknMAdXBTeok3DOTUZdtKxnReD76ad9X9S+cROwQ@mail.gmail.com>
Subject: Update to BFD over VXLAN
To: rtg-bfd WG <rtg-bfd@ietf.org>, bfd-chairs@ietf.org, Martin Vigoureux <martin.vigoureux@nokia.com>
Content-Type: multipart/mixed; boundary="000000000000dc44870597be1fa2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/-7Y5F6hQJSAcVRqmD8j1j36TUBE>
X-Mailman-Approved-At: Tue, 19 Nov 2019 19:21:36 -0800
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: Wed, 20 Nov 2019 02:42:03 -0000

Dear All,
as was decided at the meeting, an explanation of using an address from the
Internal host loopback interface address range has been added into the
Security Consideration section:
NEW TEXT:
   This document recommends using an address from the Internal host
   loopback addresses range as the destination IP address in the inner
   IP header. Using such address prevents the forwarding of the
   encapsulated BFD control message by a transient node in case the
   VXLAN tunnel is broken as according to [RFC1812]:

      A router SHOULD NOT forward, except over a loopback interface, any
      packet that has a destination address on network 127.  A router
      MAY have a switch that allows the network manager to disable these
      checks.  If such a switch is provided, it MUST default to
      performing the checks.

Welcome your comments and suggestions. If the update is acceptable, will
upload the new version.

Attached are the diff and the working version of the draft.

Regards,
Greg
.