Re:Working Group Last Call on BFD Authentication Documents (expiresSeptember 13, 2019)

<xiao.min2@zte.com.cn> Mon, 16 September 2019 02:28 UTC

Return-Path: <xiao.min2@zte.com.cn>
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 67CCC120807 for <rtg-bfd@ietfa.amsl.com>; Sun, 15 Sep 2019 19:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 v9p4ydIFo-7X for <rtg-bfd@ietfa.amsl.com>; Sun, 15 Sep 2019 19:28:40 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F745120100 for <rtg-bfd@ietf.org>; Sun, 15 Sep 2019 19:28:39 -0700 (PDT)
Received: from mxct.zte.com.cn (unknown [192.168.164.217]) by Forcepoint Email with ESMTPS id 0DAC84B4D3266C773CDC; Mon, 16 Sep 2019 10:28:38 +0800 (CST)
Received: from mse-fl2.zte.com.cn (unknown [10.30.14.239]) by Forcepoint Email with ESMTPS id E154AF7B1D050060AC30; Mon, 16 Sep 2019 10:28:37 +0800 (CST)
Received: from njxapp05.zte.com.cn ([10.41.132.204]) by mse-fl2.zte.com.cn with SMTP id x8G2SLKp095653; Mon, 16 Sep 2019 10:28:21 +0800 (GMT-8) (envelope-from xiao.min2@zte.com.cn)
Received: from mapi (njxapp02[null]) by mapi (Zmail) with MAPI id mid201; Mon, 16 Sep 2019 10:28:21 +0800 (CST)
Date: Mon, 16 Sep 2019 10:28:21 +0800 (CST)
X-Zmail-TransId: 2afa5d7ef345e69d200e
X-Mailer: Zmail v1.0
Message-ID: <201909161028210504433@zte.com.cn>
In-Reply-To: <CACi9rdukH1s4OEt_D5GqvBPvPR0THceVAfiJRUgnrnKFcRTqvw@mail.gmail.com>
References: 20190216170740.GA31558@pfrc.org, 20190702183714.GB3974@pfrc.org, CACi9rdukH1s4OEt_D5GqvBPvPR0THceVAfiJRUgnrnKFcRTqvw@mail.gmail.com
Mime-Version: 1.0
From: <xiao.min2@zte.com.cn>
To: <santosh.pallagatti@gmail.com>
Cc: <mishra.ashesh@outlook.com>, <rtg-bfd@ietf.org>
Subject: =?UTF-8?B?UmU6V29ya2luZyBHcm91cCBMYXN0IENhbGwgb24gQkZEIEF1dGhlbnRpY2F0aW9uIERvY3VtZW50cyAoZXhwaXJlc1NlcHRlbWJlciAxMywgMjAxOSk=?=
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl2.zte.com.cn x8G2SLKp095653
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/Lwyxu3IkmfdU5-uWmb36JwtKpfQ>
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: Mon, 16 Sep 2019 02:28:43 -0000

Hi all,







I support all the three drafts to be published. They're useful enhancements to base BFD protocol, short and well-written.






BRs,


Xiao Min










原始邮件



发件人:SantoshPK <santosh.pallagatti@gmail.com>
收件人:Ashesh Mishra <mishra.ashesh@outlook.com>om>;
抄送人:rtg-bfd@ietf.org <rtg-bfd@ietf.org>rg>;
日 期 :2019年09月13日 01:10
主 题 :Re: Working Group Last Call on BFD Authentication Documents (expiresSeptember 13, 2019)





I support all three documents. 



On Wed, Sep 11, 2019 at 9:22 AM Ashesh Mishra <mishra.ashesh@outlook.com> wrote:





As author, I support all three drafts. 


On Sep 10, 2019, at 7:13 PM, Manav Bhatia <manavbhatia@gmail.com> wrote:




I support all 3 documents.



On Tue, Aug 27, 2019 at 8:45 PM Jeffrey Haas <jhaas@pfrc.org> wrote:

Working Group,

As we discussed in Montreal at IETF-105, the last hang up on progressing the
authentication documents (thread copied below) was concerns on the IPR
against them.

The holder of the IPR believes their discloures are consistent with prior
IPR posted against the BFD suite of published RFCs.o

We are thus proceeding with the Working Group Last Call for these documents....
You are encouraged to provide technical feedback for the contents of the
documents, which addresses providing stronger authentication on the BFD
protocol.  

Please indicate whether you believe these documents should be advanced to
the IESG for publication as RFCs.

-- Jeff and Reshad


On Tue, Jul 02, 2019 at 02:37:15PM -0400, Jeffrey Haas wrote:
> 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