Re: Progressing BFD authentication documents

Jeffrey Haas <jhaas@pfrc.org> Tue, 02 July 2019 18:35 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 BB24E1206F2 for <rtg-bfd@ietfa.amsl.com>; Tue, 2 Jul 2019 11:35:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 gVOTCUhht2tG for <rtg-bfd@ietfa.amsl.com>; Tue, 2 Jul 2019 11:35:51 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id E31BA12010F for <rtg-bfd@ietf.org>; Tue, 2 Jul 2019 11:35:50 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 3F55F1E2F2; Tue, 2 Jul 2019 14:37:15 -0400 (EDT)
Date: Tue, 2 Jul 2019 14:37:15 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: rtg-bfd@ietf.org
Subject: Re: Progressing BFD authentication documents
Message-ID: <20190702183714.GB3974@pfrc.org>
References: <20190216170740.GA31558@pfrc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190216170740.GA31558@pfrc.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/fACiRf65FyLOZbJc1ySPqjhNkhs>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 02 Jul 2019 18:35:53 -0000

Working Group,

A followup on this item.

Currently, the status is identical to that which was last posted.  Mahesh
did make contact with Ciena IPR holders regarding the state of the license.
It is their belief that their disclosure is consistent with similar IPR
filed against BFD.  Citing two similar ones:

https://datatracker.ietf.org/ipr/516/
https://datatracker.ietf.org/ipr/1419/

It also appears to be their belief that the current wording doesn't require
that a license fee is due.  However, this is private commentary.

At this point, my recommendation to the working group is we decide if we'll
proceed with the publication process.  Let's use this time prior to IETF 105
to discuss any pending issues on these documents.

-- Jeff

On Sat, Feb 16, 2019 at 12:07:40PM -0500, Jeffrey Haas wrote:
> Working Group,
> 
> On March 28, 2018, we started Working Group Last Call on the following document
> bundle:
> 
>   draft-ietf-bfd-secure-sequence-numbers
>   draft-ietf-bfd-optimizing-authentication
>   draft-ietf-bfd-stability
> 
> The same day, Mahesh Jethanandani acknowledged there was pending IPR
> declarations against these drafts.  An IPR declaration was finally posted on
> November 1, 2018.  In particular, it notes a patent.  The licenseing is
> RAND.  
> 
> https://datatracker.ietf.org/ipr/3328/
> 
> In the time since the WGLC was requested, there were a number of technical
> comments made on these drafts.  It's my belief that all substantial
> technical comments had been addressed in the last posted version of these
> documents.  Note that there was one lingering comment about Yang
> considerations for the BFD module with regard to enabling this optimized
> authentication mode which can be dealt with separably.
> 
> The chairs did not carry out a further consensus call to ensure that there
> are no further outstanding technical issues.
> 
> On November 21, Greg Mirsky indicated an objection to progressing the
> document due to late disclosure.
> 
> https://mailarchive.ietf.org/arch/msg/rtg-bfd/u8rvWwvDWRKI3jseGHecAB9WtDo
> 
> Since we are a little over a month prior to the upcoming IETF 104, this
> seems a good time to try to decide how the Working Group shall finish this
> work.  Since we are meeting in Prague, this may progress to microphone
> conversation.
> 
> For the moment, the chairs' perceived status of the documents are:
> - No pending technical issues with the documents with one known issue.
> - Concerns over late disclosure of IPR.
> - No solid consensus from the Working Group that we're ready to proceed.
>   This part may be covered by a future consensus call, but let's hear list
>   discussion first.
> 
> -- Jeff