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

Colin Docherty <colin@doch.org.uk> Fri, 15 December 2017 14:25 UTC

Return-Path: <colin.doch.org.uk@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 8B61E124205; Fri, 15 Dec 2017 06:25:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=no
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 jGbKd25pc-43; Fri, 15 Dec 2017 06:25:00 -0800 (PST)
Received: from mail-ot0-f177.google.com (mail-ot0-f177.google.com [74.125.82.177]) (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 1DBC3128C83; Fri, 15 Dec 2017 06:24:57 -0800 (PST)
Received: by mail-ot0-f177.google.com with SMTP id h9so7913854oti.0; Fri, 15 Dec 2017 06:24:57 -0800 (PST)
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=WgwXwp2qSfgVm+JuzU2rMSSWVRPgVf0o5u5GsFR2B+A=; b=Sj4rXlZzuE/BpP+mWfs2P2Z9B3Ky5IR2qzGfG2u2CiPQTEj+M/wGgq7FScOCGogkt5 g8jbM53YXZ9L23HXoRe5qHLD4qUDtGAsi99DJO9yoqNqT97yJM7oBJsZP40AQ0As4H1K AjQEDE+iDOEyr1YFWZ/i7fZ4rzweH/L2WslyWLY8GPM64qvXxg17GZtH3SougKTgowHA EjHpN/bJs7JndG9VEB82gbPVrQYxcpBPPdT9WOBtvXTCYrYp9gkaBv+vQTp7X4L+ghVL ue407PXWY51+lJPdazRqcNQyGDvTMG7hbZPkAzHitFN11iNEEm+9MMv7+gS3jpDCgtZ9 x9Rw==
X-Gm-Message-State: AKGB3mIjMoIZ8eKqjCeZQ52JPHAAuDma+fwNlqsCxHphFzjyWfcQpo58 j4ygDGXAUoXQRGHqwMZFY7dgumSlCDkOvyaI+icPIw==
X-Google-Smtp-Source: ACJfBou0abu/GMTgx/IiNiqbYLdfSTjJ0R0ngEjrNHvBcj14PJGiPiR9COaEvYfTYAECo/Oiw5P45dCBC5ODhIjerOk=
X-Received: by 10.157.46.86 with SMTP id c22mr7250887otd.213.1513347896367; Fri, 15 Dec 2017 06:24:56 -0800 (PST)
MIME-Version: 1.0
References: <6e5d11fb30274932a442abae418fc49b@XCH-RCD-018.cisco.com>
In-Reply-To: <6e5d11fb30274932a442abae418fc49b@XCH-RCD-018.cisco.com>
From: Colin Docherty <colin@doch.org.uk>
Date: Fri, 15 Dec 2017 14:24:45 +0000
Message-ID: <CACei1EG6FGHV6NtC+jiH-+nV=n7dTAAGvEoFWRx8QBCnQSDHuQ@mail.gmail.com>
Subject: Re: IPR call for draft-nitish-vrrp-bfd-p2p
To: "Aditya Dogra (addogra)" <addogra@cisco.com>
Cc: RTGWG <rtgwg@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "draft-nitish-vrrp-bfd-p2p@ietf.org" <draft-nitish-vrrp-bfd-p2p@ietf.org>
Content-Type: multipart/alternative; boundary="001a11397b84c8df6d056061c373"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/hIZSKXPwl_xiI6sedgz6rE9lnW4>
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 14:25:02 -0000

Hi All,

       As a co-author of this draft, I am not aware of any IPR associated
with this draft.


Many thanks,

Colin Docherty

ietf@doch.org.uk


On Fri, 15 Dec 2017 at 00:11 Aditya Dogra (addogra) <addogra@cisco.com>;
wrote:

> Hi All,
>
>        As a co-author of this draft , I am not aware of any IPR associated
> with this draft.
>
>
>
> Thanks & Regards,
>
> Aditya Dogra (addogra)
>
>
>
>
>
> From: rtgwg <rtgwg-bounces@ietf.org>; on behalf of Chris Bowers <
> chrisbowers.ietf@gmail.com>;
>
> Date: Thursday, December 14, 2017 at 8:44 AM
>
> To: RTGWG <rtgwg@ietf.org>;
>
> Cc: "rtg-bfd@ietf.org"; <rtg-bfd@ietf.org>;
>
> Subject: IPR call for draft-nitish-vrrp-bfd-p2p
>
>
>
> 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
>
>
>