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

Jeff Tantsura <> Thu, 14 December 2017 21:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 009EE12944F; Thu, 14 Dec 2017 13:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Status: No, score=-1.997 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 18EuyIsPPWPE; Thu, 14 Dec 2017 13:48:33 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4003:c0f::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 76733127005; Thu, 14 Dec 2017 13:48:33 -0800 (PST)
Received: by with SMTP id d27so6205582ote.11; Thu, 14 Dec 2017 13:48:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=08L8acHrnDxJkFhaA4yRTUiCiFLyZ4Ujm0tB/uHjcy4=; b=dRvWZoFgVfy8LBTqP0s9SNMN8JTcs9MYn1DCHzCTdc4B1wyeGDE8FRLmb98FJWZ5QH daNO0Xqqi6cluUvXOhCgPFBRBBdthHpjDukaNXjE9lKbv2kORATQtcRR0m3sZzhRnGxC jBozd0Cty6QvGRFJd2yvQNt7RzS+8djW3icL4NXkj0GNtHV/rgLjDdGFOonhP7UbF0Nu P16a3idR+yNah+ZvzxbLlzf0bF1emBvtXlYqKsMmWd6f/3T34wr7/V2oIqT7mcHd7ocf qTXiN/4/4JcLMP24EwN+z/N3/naSzJk3OB1+qVplH/tBlyQO0e4t2+fhqfGFBQONoUpR BhkQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=08L8acHrnDxJkFhaA4yRTUiCiFLyZ4Ujm0tB/uHjcy4=; b=RowZ0GYfcELEheG7vdaAROgBwaEORMOn14kJPdnRHOn4Qqk0jaU2XkPsu9YwFtaSvE RFAokHxK8mFS/34Mqyac5Lfej5yTplR2D+pfUW/ukkSe9CLZbunVWvYr0r3w8EQHgD11 ReyhE9uBPGlsP3ddDFA25N6XZWxfOfbiRndCTRINhMQ48gNeGbO6tKcawmV8B+OxO6M3 hJq0kaYAUCyRp4sra+9F78ghbjlcOagsz3q0gx7zykB0PRJHDRL1AQ/BPlSrw5Oxx+UZ 7swFJ11PYIeNryLMldzjOhR0HTLPbSAR78IuqNWj/pigzPxUsNmwbfFblb7TltjxAuWR u+gw==
X-Gm-Message-State: AKGB3mJvhW5t9oYvbhthIMpaMlAgOS3s2GQHmBgzG0Ny/FEFbKPIVSL2 ngSnDVDOLyqpXlwE4KDlSsU=
X-Google-Smtp-Source: ACJfBotuKdLGYIOx+TB9J4VK93vK2++txuFY6c/uPGBv9roqlvJqNSwhtMMTaydnrr7QDFGlhWe4eA==
X-Received: by with SMTP id i3mr6562770otc.163.1513288112772; Thu, 14 Dec 2017 13:48:32 -0800 (PST)
Received: from [] ([]) by with ESMTPSA id u2sm2429345otf.66.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Dec 2017 13:48:32 -0800 (PST)
User-Agent: Microsoft-MacOutlook/f.29.0.171205
Date: Thu, 14 Dec 2017 13:48:29 -0800
Subject: Re: IPR call for draft-nitish-vrrp-bfd-p2p
From: Jeff Tantsura <>
To: Chris Bowers <>, RTGWG <>
CC: "" <>
Message-ID: <>
Thread-Topic: IPR call for draft-nitish-vrrp-bfd-p2p
References: <> <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3596104111_475347419"
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 21:48:36 -0000

As co-author, I am not aware of any IPR that applies to the 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. 





_______________________________________________ rtgwg mailing list