
From nobody Wed Sep  9 13:53:27 2020
Return-Path: <internet-drafts@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 032B43A0E54; Wed,  9 Sep 2020 13:53:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: rtg-bfd@ietf.org
Subject: I-D Action: draft-mirsky-bfd-mpls-demand-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 7.16.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: rtg-bfd@ietf.org
Message-ID: <159968480096.11114.4251067926858714924@ietfa.amsl.com>
Date: Wed, 09 Sep 2020 13:53:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/_cKOKILrAhFUOc1brh0hlD_8H0o>
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: Wed, 09 Sep 2020 20:53:21 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bidirectional Forwarding Detection WG of the IETF.

        Title           : BFD in Demand Mode over Point-to-Point MPLS LSP
        Author          : Greg Mirsky
	Filename        : draft-mirsky-bfd-mpls-demand-08.txt
	Pages           : 5
	Date            : 2020-09-09

Abstract:
   This document describes procedures for using Bidirectional Forwarding
   Detection (BFD) in Demand mode to detect data plane failures in
   Multiprotocol Label Switching (MPLS) point-to-point Label Switched
   Paths.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-mirsky-bfd-mpls-demand/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-mirsky-bfd-mpls-demand-08
https://datatracker.ietf.org/doc/html/draft-mirsky-bfd-mpls-demand-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-mirsky-bfd-mpls-demand-08


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Thu Sep 10 05:24:11 2020
Return-Path: <internet-drafts@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 804513A08AB; Thu, 10 Sep 2020 05:24:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: rtg-bfd@ietf.org
Subject: I-D Action: draft-ietf-bfd-unaffiliated-echo-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 7.16.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: rtg-bfd@ietf.org
Message-ID: <159974064345.28848.11522462025408390357@ietfa.amsl.com>
Date: Thu, 10 Sep 2020 05:24:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/knicFWnz75emkEB96GrBWw20xZo>
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: Thu, 10 Sep 2020 12:24:04 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Bidirectional Forwarding Detection WG of the IETF.

        Title           : Unaffiliated BFD Echo Function
        Authors         : Weiqiang Cheng
                          Ruixue Wang
                          Xiao Min
                          Aihua Liu
                          Reshad Rahman
                          Raj Chetan Boddireddy
	Filename        : draft-ietf-bfd-unaffiliated-echo-00.txt
	Pages           : 6
	Date            : 2020-09-09

Abstract:
   Bidirectional Forwarding Detection (BFD) is a fault detection
   protocol that can quickly determine a communication failure between
   two forwarding engines.  This document proposes a use of BFD echo
   where the local system supports BFD but the neighboring system does
   not support BFD.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-bfd-unaffiliated-echo-00
https://datatracker.ietf.org/doc/html/draft-ietf-bfd-unaffiliated-echo-00


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Fri Sep 11 08:38:18 2020
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 251763A0407; Fri, 11 Sep 2020 08:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 2CMD5jKMuyqn; Fri, 11 Sep 2020 08:38:15 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::234]) (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 F0B563A080F; Fri, 11 Sep 2020 08:38:14 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id c2so12772551ljj.12; Fri, 11 Sep 2020 08:38:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=kVyv8JyPq+zYMnN1oQy2vdpfbrqKVgmajMVwWK8oizc=; b=jCQ7+ohP/O6cvWbb6nasVnD2brjdoVuxqKVHZQlm9g6qbnJvRTlQQqBeHfolwP8OGq hI6pWjApejqQL4FOtvxIKUVZDrYdRk/ZG0+YOwdWkZyDFmWCxNhhdEHmVyxEEz9q/IO7 mc9DStTpci13SNFd5iFakEo4/93nBEkQF+X2n1rV3gD0HrDNV+KF0kjIrSybOxIlkImB 9KH3HCzMDzr7zsFNX6BHbDy2qtIP8yIJi5q56dkm+0kRffNGM6j9wEhUgRnRXGZknJjt PsnvFH5WHiPdZn7spBpID3lBZQCKDY29vltuWcfktdzq6UjAhPEKPK6/5KT6in0zBTFH FN6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=kVyv8JyPq+zYMnN1oQy2vdpfbrqKVgmajMVwWK8oizc=; b=HwAIC/Q1YaH4lVi9nlYE45Dr1lKVOglFLwoR4qIssRdDsRKjQsn1t5WV1VtA3Zou5m LvIqFu32JHwRo/FH6hOV2WAmlH+5LOLrb24f1lvDWd4mZ2cetk954i86Fuj7BF6nxm0l RbYZSuPVGT73VAIkEX7+lZgrq2oP0Ga0L/UJuBmJUHnLxDkDCB6rFxStM2vRYHfsoO0f i4bK8cmJI63gQ8f9M+kHhnLBJUoUoX5lb3LtnMkIs1Jfn6PXbWXjTIbiFQVD5vYnT4b/ Henps0zhd9n/izo/t7AJTUlVzOXMG+OpTS52hsPMflIF2LdbFnnZsyl5uuLtyGRdRQ6r +1GA==
X-Gm-Message-State: AOAM530LuMy8BDT8YNK7zFQQ1ZN+PkcXjsC3nv1VHeStvaJ8Ya1BHbOx ZqxNEHEEKYagRxoNIcHklCfN5PofUOZoh+j6b2Gs/+hW
X-Google-Smtp-Source: ABdhPJy5qRSWanA5G5QHSX7y3iL0L/UkqH5Y/N0mLlXtA7WUhB5iKWWkUOa9Y0wDxE5DiAvjnZCSOczwGUW0+hdV1oo=
X-Received: by 2002:a2e:2e09:: with SMTP id u9mr964946lju.23.1599838691955; Fri, 11 Sep 2020 08:38:11 -0700 (PDT)
MIME-Version: 1.0
References: <159968480096.11114.4251067926858714924@ietfa.amsl.com>
In-Reply-To: <159968480096.11114.4251067926858714924@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 11 Sep 2020 08:38:00 -0700
Message-ID: <CA+RyBmWNent_Bffs+5DwJoiOzxY0GhsTMoea_uWBw32dWMX6kQ@mail.gmail.com>
Subject: Fwd: I-D Action: draft-mirsky-bfd-mpls-demand-08.txt
To: rtg-bfd WG <rtg-bfd@ietf.org>, bfd-chairs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ee98cc05af0b7806"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/xCZpCoQx3-vQyQq1W-OyoQs_4QQ>
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: Fri, 11 Sep 2020 15:38:17 -0000

--000000000000ee98cc05af0b7806
Content-Type: text/plain; charset="UTF-8"

Dear All,
the updates in this version intended to address comments received from WG
Chairs and WG's AD.
Your questions, comments, and suggestions are always welcome and greatly
appreciated.

Regards,
Greg

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Wed, Sep 9, 2020 at 1:54 PM
Subject: I-D Action: draft-mirsky-bfd-mpls-demand-08.txt
To: <i-d-announce@ietf.org>
Cc: <rtg-bfd@ietf.org>



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Bidirectional Forwarding Detection WG of
the IETF.

        Title           : BFD in Demand Mode over Point-to-Point MPLS LSP
        Author          : Greg Mirsky
        Filename        : draft-mirsky-bfd-mpls-demand-08.txt
        Pages           : 5
        Date            : 2020-09-09

Abstract:
   This document describes procedures for using Bidirectional Forwarding
   Detection (BFD) in Demand mode to detect data plane failures in
   Multiprotocol Label Switching (MPLS) point-to-point Label Switched
   Paths.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-mirsky-bfd-mpls-demand/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-mirsky-bfd-mpls-demand-08
https://datatracker.ietf.org/doc/html/draft-mirsky-bfd-mpls-demand-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-mirsky-bfd-mpls-demand-08


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.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

--000000000000ee98cc05af0b7806
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Dear All,<div>the updates in this version intended to addr=
ess comments received from WG Chairs and WG&#39;s AD.</div><div>Your questi=
ons, comments, and suggestions are always welcome and greatly appreciated.<=
/div><div><br></div><div>Regards,</div><div>Greg<br><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">---------- Forwarded message =
---------<br>From: <span dir=3D"auto">&lt;<a href=3D"mailto:internet-drafts=
@ietf.org">internet-drafts@ietf.org</a>&gt;</span><br>Date: Wed, Sep 9, 202=
0 at 1:54 PM<br>Subject: I-D Action: draft-mirsky-bfd-mpls-demand-08.txt<br=
>To:  &lt;<a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a=
>&gt;<br>Cc:  &lt;<a href=3D"mailto:rtg-bfd@ietf.org">rtg-bfd@ietf.org</a>&=
gt;<br></div><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
This draft is a work item of the Bidirectional Forwarding Detection WG of t=
he IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 BFD in Demand Mode over Point-to-Point MPLS LSP<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Greg=
 Mirsky<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-mir=
sky-bfd-mpls-demand-08.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 5<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2020-09-09<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes procedures for using Bidirectional For=
warding<br>
=C2=A0 =C2=A0Detection (BFD) in Demand mode to detect data plane failures i=
n<br>
=C2=A0 =C2=A0Multiprotocol Label Switching (MPLS) point-to-point Label Swit=
ched<br>
=C2=A0 =C2=A0Paths.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-mirsky-bfd-mpls-demand/" =
rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft=
-mirsky-bfd-mpls-demand/</a><br>
<br>
There are also htmlized versions available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-mirsky-bfd-mpls-demand-08" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-mirsky-=
bfd-mpls-demand-08</a><br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-mirsky-bfd-mpls-dema=
nd-08" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/do=
c/html/draft-mirsky-bfd-mpls-demand-08</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-mirsky-bfd-mpls-demand=
-08" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/rfcdiff?url2=
=3Ddraft-mirsky-bfd-mpls-demand-08</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-drafts/</a><br>
<br>
<br>
</div></div></div>

--000000000000ee98cc05af0b7806--


From nobody Tue Sep 29 13:31:42 2020
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 913D53A121B; Tue, 29 Sep 2020 13:31:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-bfd-vxlan@ietf.org, bfd-chairs@ietf.org, rtg-bfd@ietf.org, Jeffrey Haas <jhaas@pfrc.org>, jhaas@pfrc.org
Subject: Benjamin Kaduk's No Objection on draft-ietf-bfd-vxlan-14: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 7.17.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <160141149555.5134.7770392875628704272@ietfa.amsl.com>
Date: Tue, 29 Sep 2020 13:31:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/Ord6HKZdN7AmsW-AaTHYu8596yU>
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, 29 Sep 2020 20:31:37 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-bfd-vxlan-14: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-bfd-vxlan/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the discussions around my discuss point, and the ensuing changes
resulting from the discussions!  My apologies that I was tardy in re-reviewing after
the updates were made.

I think the core issues have been resolved, but do have a couple comments on the -14:

Section 3 says:

                  Separate BFD sessions can be established between the
   VTEPs (IP1 and IP2) for monitoring each of the VXLAN tunnels (VNI 100
   and 200).  Using a BFD session to monitor a set of VXLAN VNIs between
   the same pair of VTEPs might help to detect and localize problems
   caused by misconfiguration.  An implementation that supports this
   specification MUST be able to control the number of BFD sessions that
   can be created between the same pair of VTEPs.  [...]

While the first two sentences are probably true, they are arguably out
of scope for this document, since Section 6 says that BFD control
packets on non-management VNI is outside the scope of this
specification.  The third sentence is quite surprising in the context of
this document only defining BFD for the management VNI, since multiple
BFD sessions on the same VNI seem redundant.

Section 5

         Destination MAC: A Management VNI, which does not have any
         tenants, will have no dedicated MAC address for decapsulated
         traffic.  The value [TBD1] SHOULD be used in this field.

While this normative language seems like the appropriate level of
stringency, I do find myself wondering what other value might be used
and why.  (This, of course, need not be answered in the document, though
it could be if the answer is known and useful.)



