Re: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check

Jeffrey Haas <> Tue, 11 April 2023 10:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0CDC6C15155B; Tue, 11 Apr 2023 03:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.004
X-Spam-Status: No, score=-6.004 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9XXyGcHTPGlo; Tue, 11 Apr 2023 03:35:10 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id DA674C151543; Tue, 11 Apr 2023 03:35:09 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTPSA id 446271E037; Tue, 11 Apr 2023 06:35:08 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-D331E95B-533F-4FFE-AF20-FD7B2A3C4098"
Content-Transfer-Encoding: 7bit
From: Jeffrey Haas <>
Mime-Version: 1.0 (1.0)
Subject: Re: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check
Date: Tue, 11 Apr 2023 06:34:57 -0400
Message-Id: <>
References: <>
Cc:, rtg-bfd WG <>
In-Reply-To: <>
To: Greg Mirsky <>
X-Mailer: iPhone Mail (20D67)
Archived-At: <>
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 11 Apr 2023 10:35:14 -0000


Sorry if the phrasing was confusing. 

We are looking for any undisclosed ipr. 


On Apr 10, 2023, at 9:05 PM, Greg Mirsky <> wrote:

Hi Jeff,
I got confused by the "any additional IPR applicable to this document" in the announcement. AFAIK, there is no IPR disclosure for the" rel="nofollow">draft-cw-bfd-unaffiliated-echo, nor for the" rel="nofollow">draft-ietf-bfd-unaffiliated-echo. Have I missed something?


On Mon, Apr 10, 2023 at 8:27 AM Jeffrey Haas <> wrote:" rel="noreferrer nofollow" target="_blank">

Working Group,

The Working Group Last Call for draft-ietf-bfd-unaffiliated-echo has completed.  My judgment is that it has weak, but positive support to proceed to publication.  This isn't atypical of BFD work at this point in the BFD Working Group's life. 

The next steps for the document:

1. Please continue to iterate through the issues raised during last call.  I will be summarizing them in the original WGLC thread.  I suspect we can reach conclusion for them shortly.

2. Each of the authors needs to make an attestation as to whether they're aware of any additional IPR applicable to this document.  The rest of the Working Group, as per BCP 78/79[1] should also disclose of any applicable IPR if they're aware of it.

One thing that makes this document particularly interesting is that this work is covered partially under work done in BBF in TR-146.  This will be noted in the shepherd writeup.

-- Jeff

[1]" rel="noreferrer nofollow" target="_blank">