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

Greg Mirsky <gregimirsky@gmail.com> Mon, 18 February 2019 15:32 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 E3F71130F18 for <rtg-bfd@ietfa.amsl.com>; Mon, 18 Feb 2019 07:32:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, 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 cwRwL4Hk7c1s for <rtg-bfd@ietfa.amsl.com>; Mon, 18 Feb 2019 07:32:43 -0800 (PST)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 C3E81130F03 for <rtg-bfd@ietf.org>; Mon, 18 Feb 2019 07:32:42 -0800 (PST)
Received: by mail-lj1-x22d.google.com with SMTP id g80so14730706ljg.6 for <rtg-bfd@ietf.org>; Mon, 18 Feb 2019 07:32:42 -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=x98uWyJBrJtaEk5g/7guGODlGHKs2UifJb/tz3igrLk=; b=Hej/PvAZVAw1RyilVT6dCzEHH2zIpEB6/i9JZrx8iKZFTgKiDGbPXU0IwCvdCQC2dd YWzpAqUILWrT0zW0ytPZPwJbOaJuai2HOLc6Jn0n91Z3dGCcj7dEu9HKbcV0t4Kcq58h Ylal3E+uRtrACgCtL2D8UAuNV14pir9qJxLbUaCcP2YCis5oDu6W8t0lKqXObPcCSQS6 uB8mWvYMRemzJKh1sn21ThgfrpsWOijpMH+DtxTMqDnEXqL7Gn911htjZiZ6edHB5aC1 9m3xuptEZJPyPfS/Bo3lB1BuGVG8EKAi6sbFZvGLwF6UlUw9iQYEe6VpE60AAGPYuqhK nQQA==
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=x98uWyJBrJtaEk5g/7guGODlGHKs2UifJb/tz3igrLk=; b=qiyX3doqua+tFz5n1/vCDkr5oGJBYX0octX2Jf5ZDj5Z/Ps/d6QNNfMmere7dXwgry i+F6i9sf75i5y1sGnbx4sPrsjSqimswTuCavn5rYOzjLvxNWwjOILnu/IXUSSdxRIZAz CSvytfphoUFitF137P5C0/8g9CeESEGLqZhFFX+mfpkfS5z4hXgVyKFJ9Myrr0eI0YM4 SWoXHJJxPELf+DjKurV7cn2uL4Ljlay4OdpFUM/59roOPwZe9otAsw8DGTwtn/+1w7wq QAdChsGauIxZvX02JjkD8KYFqlYASs6xSjbgDIXyl+9U7GOaYroHwBafA/7SEtBtRCTQ vw5Q==
X-Gm-Message-State: AHQUAuaX2HFdKnz1Vz4UZQLcXLSnVL26lNgenL1t64xuhO4NDduAV6Gq L1b1w1vfRYuH2wPyjwzXK4dGI0iPnxUspsA1wEc=
X-Google-Smtp-Source: AHgI3Ibu6XoJsqiswh4Gm9iNQ5AoRcJOwJN7ENwwosRsJhk8gGhXQNXz0icWkEkPTC9y6aXqUjzmpSeY06S0OuzqFrs=
X-Received: by 2002:a2e:81a:: with SMTP id 26-v6mr14488737lji.14.1550503960762; Mon, 18 Feb 2019 07:32:40 -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+RyBmW+pxqk6OmT4H1233XY-T7O06azGodUNu24Pu22aqhtMg@mail.gmail.com> <20190216163154.GC28950@pfrc.org> <CA+RyBmUp0jhNjPFO_xgdm_1dNnxYSiNhBfCsoVJKNj6rOFRjvw@mail.gmail.com> <20190216184510.GF28950@pfrc.org> <CA+RyBmUHm5YnbuFp6oiXUVnVS+0kfSW8xdJqjwC+HiP_WfqKBA@mail.gmail.com> <20190218152544.GG28950@pfrc.org>
In-Reply-To: <20190218152544.GG28950@pfrc.org>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 18 Feb 2019 07:32:30 -0800
Message-ID: <CA+RyBmUGwZj0AuQWT+atzeN9uR4i5ffpzeKsMM_fRYB5BVmFVw@mail.gmail.com>
Subject: Re: WG Adoption request for draft-mirsky-bfd-mpls-demand
To: Jeffrey Haas <jhaas@pfrc.org>
Cc: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, Martin Vigoureux <martin.vigoureux@nokia.com>, rtg-bfd WG <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cddc4305822cd57e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/ONaaZgk6zJv6R8rI4FnU4rUo8TE>
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: Mon, 18 Feb 2019 15:32:45 -0000

Hi Jeff,
could you please clarify which of your roles, BFD WG chair or individual
contributor, you are in this discussion.

Regards,
Greg

On Mon, Feb 18, 2019 at 7:26 AM Jeffrey Haas <jhaas@pfrc.org> wrote:

> Greg,
>
> Answering this message with the reply partially reorganized.
>
>
> On Sun, Feb 17, 2019 at 04:40:31PM -0800, Greg Mirsky wrote:
> > On Sat, Feb 16, 2019 at 10:46 AM Jeffrey Haas <jhaas@pfrc.org> wrote:
> > > > GIM>> The behavior of the system in Demand mode is introduced as
> > > optional.
> > > > And that is precisely the update to RFC 5880.
> > >
> > > I don't understand.
> > >
> > > Basically, 5880, 5884 leave demand as an option.  It's built into the
> > > specs.
> > > It's unclear what you're suggesting being changed.
> > >
> > GIM2>> RFC 5884 leaves the Demand mode outside its scope. RFC 5884 does
> not
> > discuss how the Demand mode may be used in BFD over MPLS LSPs.
>
> Even thought the RFC says demand mode is out of scope, 5880 is clear about
> how demand mode works.  I'm not seeing anything in your draft that alters
> that procedure.
>
> Basically, no draft is needed for a one-liner: you can use demand mode.
>
> > GIM2>> Is the fact that the patent application is not yet published the
> > sole foundation for your objection to adopting this draft as Chair of BFD
> > WG or as an individual contributor? Is there any IETF document that
> > requires that the patent must be published before the draft can be
> adopted
> > or published as RFC?
>
> The sole reason for mentioning this is demand mode is clear.  BFD over mpls
> is clear.  You're asserting some sort of IPR on things that are already
> clear.  So, either your draft itself is unclear on some new thing you're
> asserting IPR on, or you're not actually covering something new.  That's
> it.
>
> -- Jeff
>