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

"Nitish Gupta (nitisgup)" <> Thu, 14 December 2017 19:52 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DDE6912871F; Thu, 14 Dec 2017 11:52:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id y-blU5eCMYXq; Thu, 14 Dec 2017 11:52:18 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 09C87127286; Thu, 14 Dec 2017 11:52:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=18862; q=dns/txt; s=iport; t=1513281137; x=1514490737; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=p3c5wAVX2ZtX6ymH9fYhVZvNLui7FwaX/F309q+o84w=; b=Rrvw6R5FCWEKR7XtXmNVAEsAvjiEwUdf9AWPGHxPGNmmYCWDs8B+dXt7 qikGfV4fcYX4YJvrIcBNNTm8KKAwZ7Mk7OZsDjF/9saBkDtvb4oTgzXIc myLfc1Ahk9eMr156K2UN6/rhT7YQreBdCFzMBpNh64g5G+yxAKYgKjOAF w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.45,401,1508803200"; d="scan'208,217";a="326294486"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Dec 2017 19:52:16 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id vBEJqGGm023870 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 14 Dec 2017 19:52:16 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 14 Dec 2017 14:52:16 -0500
Received: from ([]) by ([]) with mapi id 15.00.1320.000; Thu, 14 Dec 2017 14:52:16 -0500
From: "Nitish Gupta (nitisgup)" <>
To: Chris Bowers <>, RTGWG <>
CC: "" <>
Subject: Re: IPR call for draft-nitish-vrrp-bfd-p2p
Thread-Topic: IPR call for draft-nitish-vrrp-bfd-p2p
Thread-Index: AQHTdPriGPv1YU09d0GBdGO1y7d5tqNDDeEA
Date: Thu, 14 Dec 2017 19:52:15 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/f.1a.0.160910
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9518082AA52E44069201F7F142E95B76ciscocom_"
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Routing Area Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Dec 2017 19:52:20 -0000


As co-author, I am not aware of any IPRs, on this draft.

From: rtgwg <> on behalf of Chris Bowers <>
Date: Thursday, December 14, 2017 at 8:44 AM
To: RTGWG <>
Cc: "" <>
Subject: IPR call for draft-nitish-vrrp-bfd-p2p

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.
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.

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 does not apply to

Having documented that history, I would now like to conduct the usual
RTGWG process regarding IPR, specifically for IPR related to

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.