Re: WG Adoption request for draft-mirsky-bfd-mpls-demand

Greg Mirsky <gregimirsky@gmail.com> Thu, 13 December 2018 13:53 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 DF674127133 for <rtg-bfd@ietfa.amsl.com>; Thu, 13 Dec 2018 05:53:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 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_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 E-V-g92DozPG for <rtg-bfd@ietfa.amsl.com>; Thu, 13 Dec 2018 05:53:33 -0800 (PST)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 14A441252B7 for <rtg-bfd@ietf.org>; Thu, 13 Dec 2018 05:53:33 -0800 (PST)
Received: by mail-lf1-x134.google.com with SMTP id v5so1614629lfe.7 for <rtg-bfd@ietf.org>; Thu, 13 Dec 2018 05:53:32 -0800 (PST)
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 :cc; bh=FgCweWx2v6znNlMyfpP9U29HsMb36QJPb7EfbVcAIb8=; b=V61YOjcyFCGDiHdfg3aGEFoc0/3Rl2xQ8SadjhL8rx/FkhBAcZ7buEdgHBCrLZ/eDQ HhPyWnq/CRXw3Olix8agRZdUR9ALQNUhVleZLUAThp4D9TI6RBtO/7ytbvayJJ9j6buA jc4BsJwutiGfkvAdeJaVTeLDHivABdIBwbfsw0ajE6oaS78THq/MNMx1Cck+TcgrVsqH z0tjZArJOx/jzUZZPgcCzOcVks20eD7Cf/rKmBKqLz34sz91gRdY5ZESF2iOcoo0HLfO PLAheliK6STR8LAdqWRhL0aL8UoQYWk8jluOnSsrjWO8MjE7je9ngy3/qfXV5sfdiRbL syCw==
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:cc; bh=FgCweWx2v6znNlMyfpP9U29HsMb36QJPb7EfbVcAIb8=; b=rAop2KyFHm7twmutAwvZOrzkubthgTFwI/1+7tSzVlu7n/qNzTQ/Tjbk4EPbojCKH1 Y6WTnk8AsA/Wsv43NraJwrRbvlhHAMolg8m+fgksOse4di2dzSTDBtiOvSwMAc8nMySG QqQhTncXm8aoOvmJeyyq74S+RZSwIvcoQvXskeBgMMf2uClFcHycuzw9yBrItmanijnC sDkxCcI2RahlHc4jk1m5gof2AVSsHY3X9ymHploTk9iGpMV8L+6e5EDEN493qSblAqrn 4oGAbEl96TdOQVyWbdrwT2r6C4WPHJpNQjFxuqGTeVXwTgkOdzj2eYFb4/OFGQxMmeZI z+9Q==
X-Gm-Message-State: AA+aEWYLMJE0OJSQTfwO8mJzYyx/azjk3IVkUZYHhvvhWmcAlZKIOiz3 77tL0t+y0PpFuAwJZCzWQgRsnZ4jwx8w3Nhs6bU=
X-Google-Smtp-Source: AFSGD/XYSc2poIHfm8OZTbEG1DWoGK90zOFrButl+JIgo1lLXnQNiKQcCN6dt2AGGJ21rV7Rf8GCRCXmoPkjYKPCPnQ=
X-Received: by 2002:a19:26ce:: with SMTP id m197mr13758618lfm.23.1544709210978; Thu, 13 Dec 2018 05:53:30 -0800 (PST)
MIME-Version: 1.0
References: <20181017222431.GK17157@pfrc.org> <20181121222755.GC23096@pfrc.org> <CA+RyBmWeRoySs4a8he5ZGMz-_FDjzTeHMCd_4WksDSCqB5aEYw@mail.gmail.com> <20181210220953.GA6053@pfrc.org> <CA+RyBmWUu3h=giX2mqyZcSVgdts3mgwb4hEbcFBNZTd8CCYc1w@mail.gmail.com>
In-Reply-To: <CA+RyBmWUu3h=giX2mqyZcSVgdts3mgwb4hEbcFBNZTd8CCYc1w@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 13 Dec 2018 13:53:19 +0000
Message-ID: <CA+RyBmW1o=sSCaXnDViip4Z=xP-c76QOi4H13Xt6hrr3f_NMzA@mail.gmail.com>
Subject: Re: WG Adoption request for draft-mirsky-bfd-mpls-demand
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: rtg-bfd WG <rtg-bfd@ietf.org>, Martin Vigoureux <martin.vigoureux@nokia.com>
Content-Type: multipart/alternative; boundary="000000000000cd3f98057ce7a3f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/XWwqH-QG1xqOWfG9crQx9aDrCYI>
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: Thu, 13 Dec 2018 13:53:36 -0000

Hi Jeff, et al.,
I now would like to comment on the point of "not satisfactory convergence"
of discussion. I assume that this is related to the discussion started by
the message
<https://www.ietf.org/mail-archive/web/rtg-bfd/current/msg04146.html>addressed
to Xiao Min, not to the author of the draft. Oddly enough. But I've
responded nevertheless. Two questions were raised and both were explained:
- BFD Demand mode may be used to monitor the continuity of a path in one
direction and we have two specifications, draft-ietf-bfd-multipoint and
draft-ietf-bfd-multipoint-active-tail, that describe how that can be done
without and with notification to the ingress BFD node;
- indeed, it is the liveliness of the path between the BFD systems that are
 monitored.
These were the questions and, in my opinion, both got answered. And now I
got to wonder what other questions need to be addressed? Plans to
implement? In my experience, evaluating a draft in WG AP I, explicitly or
not, answer to these questions:

   - whether the document is coherent;
   - is it likely to be actually useful in operational networks;
   - is the document technically sound?

And I cannot find any unaddressed question that falls into any of these
categories.
Much appreciate comments from BFD WG Chairs.

Regards,
Greg

On Tue, Dec 11, 2018 at 8:52 AM Greg Mirsky <gregimirsky@gmail.com> wrote:

> Hi Jeff, et al.,
> thank you for the update. I wanted to clarify the second item, the
> question related to the IPR Disclosure. The first disclosure used the
> "covenant not to assert" language. The second was to only update the filing
> status, not the licensing terms. I believe I've clarified that at the time
> of asking for WG AP. I was informed that there's the update to IPR
> Disclosure on this work submitted that restores the "covenant not to
> assert" language. I hope that can be taken into consideration by you and
> Reshad.
>
> Regards,
> Greg
>
> On Mon, Dec 10, 2018 at 10:10 PM Jeffrey Haas <jhaas@pfrc.org> wrote:
>
>> Greg,
>>
>> Apologies for the long delay in reply.
>>
>> On Wed, Nov 21, 2018 at 02:40:50PM -0800, Greg Mirsky wrote:
>> > I respectfully ask to summarize the comments that were shared with you
>> and
>> > to publish them to the WG without naming the authors.
>>
>> Tersely:
>> - The document is not addressing fundamental issues.
>> - It is encumbered by IPR.
>> - Observed list traffic regarding question on the feature was not
>>   satisfactorily converging.
>>
>> > And I have to admit that I don't understand your suggestion to use the
>> > Errata. The procedures to apply the Demand mode described in the draft
>> are
>> > not in contradiction with RFC 5880, so the suggestion to use Errata
>> > surprised me.
>>
>> I will respond on my own analysis in detail hopefully this week.  I am
>> awaiting the resolution of a particular bit of correspondence before
>> determining the tenor of my response.
>>
>> -- Jeff
>>
>