Re: IPR call for draft-nitish-vrrp-bfd-p2p

Greg Mirsky <gregimirsky@gmail.com> Fri, 15 December 2017 01:27 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 DF56D12704B; Thu, 14 Dec 2017 17:27:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, SPF_PASS=-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 D9Gwmf5fqeF2; Thu, 14 Dec 2017 17:27:53 -0800 (PST)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (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 D992F126D85; Thu, 14 Dec 2017 17:27:52 -0800 (PST)
Received: by mail-lf0-x22f.google.com with SMTP id i2so8744435lfe.9; Thu, 14 Dec 2017 17:27:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1ULnB8G1/Yw/Ila8FvDIMXS1AMS3xa31M7Wg3f58FLo=; b=jYm2N2lI2QMJoEwa45lWqjaVkU+m+XMtr+o4Eh4f/ugEy6E9qI1WPEmlki+uObM/jw Daj0CsnhUBW9ho7+aDYhihBZ71MNxSi4ttqzhXFZ8FA9vfHb96s/VyQPXksHF951sgLY XzTJ+fPEvCruEMnFPN9iwjtgHWdLsidlyt3LHi1GN2rcC9im+eL6Ky6T2Q6xFLa0fUXl 9T7eWH3hbs/b/FacAfHyp4O6ZpAaNlXPMw/7tDiUVEE51GWJKrHjEjI3miFVHkkPdars 94YDzOxRI/mTSOlLkv7kQazkTlyOotom/NTcaWE9dggN5FRRoax7ddJ1Ro2lAikl7N0x 3L7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1ULnB8G1/Yw/Ila8FvDIMXS1AMS3xa31M7Wg3f58FLo=; b=Wlh8do2w8uCRhce7N35en6dHs/d7YU9aFN9j9V7rSDqozxuKm/JKAIAluD4T4pa7Dd wwDwbgJqUUWuvTpSBme6T45FNA3A3MimWOXqEtDKxVvWSTaFEKNDlSeiB+G6mnXSOtAW ARgqpGvcn7AesCuFjsADWXUgW8Bb4mSbBtlWdcXok+8+85lcC/S56gClRdTcv7RElWvR t5I6jnWcVZ4fsfsYaO8RVTh8ynWrrUjk4FiHZgWj0CFC5794Z7DVhw02huO9pMFGpTks d7SLhAGyfgdSwNntZxjsuoMNM7tlfOU2WTTJBb/Sre0m+N650dBgpcKGb/EPIK+asY7n OrOQ==
X-Gm-Message-State: AKGB3mL1fC84IOi0kL/2ikc9xoj2bglc0PgXKZvyJlQ9qOghUWb/AmXn 0cAI8Rm8TN0UQZd0nB+y0S+f2Z6GZLLIzvKk86fHeg==
X-Google-Smtp-Source: ACJfBovPsaaGLQxYzak5Uh0eluaonrshOc0eNPgN6rkePCD8DAYG2nw1WxLTGb2zAIM7CtI8tEdlCujM31YapVyOqts=
X-Received: by 10.25.207.194 with SMTP id f185mr4976530lfg.30.1513301270928; Thu, 14 Dec 2017 17:27:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.46.32.136 with HTTP; Thu, 14 Dec 2017 17:27:50 -0800 (PST)
In-Reply-To: <CAHzoHbvCZ6xMyPfpd6+qKJA1yeji7fdSYET3sYx8Xqj4evBvOg@mail.gmail.com>
References: <CAHzoHbvCZ6xMyPfpd6+qKJA1yeji7fdSYET3sYx8Xqj4evBvOg@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 14 Dec 2017 19:27:50 -0600
Message-ID: <CA+RyBmXdzGhqOXSxMyhP93ZJs0n8xHCLg6w4ePvhW75e5ZNQSw@mail.gmail.com>
Subject: Re: IPR call for draft-nitish-vrrp-bfd-p2p
To: Chris Bowers <chrisbowers.ietf@gmail.com>
Cc: RTGWG <rtgwg@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="001a1141ffb2b12354056056e857"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/siUDn33eVZ71I92Ypfc4iohHj3A>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
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, 15 Dec 2017 01:27:56 -0000

Dear Chris, et. al,
as co-author I'm not aware of any IPR that is applicable to the current
version of draft-nitish-vrrp-bfd-p2p.

Regards,
Greg

On Thu, Dec 14, 2017 at 10:44 AM, Chris Bowers <chrisbowers.ietf@gmail.com>;
wrote:

> RTGWG,
>
> draft-nitish-vrrp-bfd-p2p is currently an individual draft.  Before
> conducting
> a poll regarding working group adoption by RTGWG, I would like to get
> responses from
> the authors and contributors regarding any IPR related to this draft.
>
> First, there is some history associated with this draft that is useful to
> document.
>
> In June of 2015, draft-nitish-vrrp-bfd-00 was published based on the use of
> point-to-point BFD by VRRP.
>
> In July of 2015, draft-mirsky-bfd-p2mp-vrrp-use-case-00 was published
> based on the use of point-to-multipoint BFD by VRRP.
>
> In October of 2015, after suggestions from the WG, the two drafts above
> were
> merged into draft-nitish-vrrp-bfd-02.
>
> In January of 2016, the following IPR was disclosed related to
> draft-nitish-vrrp-bfd.
> https://datatracker.ietf.org/ipr/2739/
> draft-nitish-vrrp-bfd-02 was the current version of draft-nitish-vrrp-bfd
> when this IPR
> was disclosed.
>
> In October of 2016, a WG adoption poll was conducted regarding
> draft-nitish-vrrp-bfd.
> There was not consensus to adopt the draft due to IPR concerns.  See this
> email for details.
> https://www.ietf.org/mail-archive/web/rtgwg/current/msg05729.html
>
> In August of 2017, draft-nitish-vrrp-bfd-p2p-00 was published.
>
> In October of 2017, a new revision of draft-mirsky-bfd-p2mp-vrrp-use-case
> (rev-01) was published.
>
> In December of 2017 (yesterday to be precise), an minor update to
> draft-nitish-vrrp-bfd-p2p was published.
>
> It is my understanding from discussions with the authors of these drafts,
> both inside and outside of the RTGWG sessions at IETF100, that
> draft-nitish-vrrp-bfd-p2p was written with the goal of separating the
> content
> of the merged draft back into two separate drafts in such a way that
> the IPR disclosed in https://datatracker.ietf.org/ipr/2739/ does not
> apply to
> draft-nitish-vrrp-bfd-p2p.
>
> Having documented that history, I would now like to conduct the usual
> RTGWG process regarding IPR, specifically for IPR related to
> draft-nitish-vrrp-bfd-p2p.
>
> https://datatracker.ietf.org/doc/draft-nitish-vrrp-bfd-p2p/
>
> If you are listed as an author or contributor to
> draft-nitish-vrrp-bfd-p2p,
> please respond to this email stating whether or not you are aware of any
> IPR that applies to draft-nitish-vrrp-bfd-p2p. The response needs to be
> sent
> to the RTGWG mailing list. The document will not advance to the next stage
> until a response has been received from each author and each individual
> that has contributed to the document.
>
> Thanks,
> Chris
>
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>
>