[nwcrg] Recent IPR disclosure against RFC 8681

kavim.shroff@codeontechnologies.com Mon, 06 April 2020 16:23 UTC

Return-Path: <kavim.shroff@codeontechnologies.com>
X-Original-To: nwcrg@ietfa.amsl.com
Delivered-To: nwcrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C1043A0C30 for <nwcrg@ietfa.amsl.com>; Mon, 6 Apr 2020 09:23:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.047
X-Spam-Level:
X-Spam-Status: No, score=-2.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FORGED_OUTLOOK_TAGS=0.052, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=codeontechnologies.com
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 zu-nCx28lo72 for <nwcrg@ietfa.amsl.com>; Mon, 6 Apr 2020 09:23:26 -0700 (PDT)
Received: from black.elm.relay.mailchannels.net (black.elm.relay.mailchannels.net [23.83.212.19]) (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 8B8343A0C2A for <nwcrg@irtf.org>; Mon, 6 Apr 2020 09:23:25 -0700 (PDT)
X-Sender-Id: 63fz4d685t|x-authuser|kavim.shroff@codeontechnologies.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id BB132340EDA for <nwcrg@irtf.org>; Mon, 6 Apr 2020 16:23:24 +0000 (UTC)
Received: from valandil.securewebz.com (100-96-23-11.trex.outbound.svc.cluster.local [100.96.23.11]) (Authenticated sender: 63fz4d685t) by relay.mailchannels.net (Postfix) with ESMTPA id 06AF5340DD0 for <nwcrg@irtf.org>; Mon, 6 Apr 2020 16:23:24 +0000 (UTC)
X-Sender-Id: 63fz4d685t|x-authuser|kavim.shroff@codeontechnologies.com
Received: from valandil.securewebz.com (valandil.securewebz.com [64.188.10.113]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.6); Mon, 06 Apr 2020 16:23:24 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: 63fz4d685t|x-authuser|kavim.shroff@codeontechnologies.com
X-MailChannels-Auth-Id: 63fz4d685t
X-Soft-Slimy: 71f2869616d87053_1586190204556_265393317
X-MC-Loop-Signature: 1586190204556:1321711327
X-MC-Ingress-Time: 1586190204555
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=codeontechnologies.com; s=default; h=Content-Type:MIME-Version:Message-ID: Date:Subject:In-Reply-To:References:To:From:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=lcS0zJejvKuuWIX4AKEDJ9SJllGROAFcHTFJafSWMyI=; b=bMbIOBVK9dzxqghyjVEOUlydh 76FX5GsqRSCko+8wI2adTmtjeSYUhgojq/9sM9O5pOBw7/kyA+207TbvviEG4RDyKPBLSmFc30MbZ si51YIBN3msnyYeUAv2mtO8bgQFcRIF1AnqGo1kGmoyW3+Snz2pR2ql23muos6pMtrdfwi9zUg6jQ czgSczBrknU/tU7xqe/EGC/LTVnd9xdQO+EJtOA1vfYD2jT+8qMtApvKiRRNmVsXHRR4rGiQss3nA C4e5pfugj0KzlSG72F7Mb2SbXEx+d4fkhynNWv0pPwyhy+FrFPEe/lGhwDScVTpKysKlIs0Q4A42A cZIU73mNw==;
Received: from [188.214.13.58] (port=7216 helo=KavimPC) by valandil.securewebz.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <kavim.shroff@codeontechnologies.com>) id 1jLUWw-00Fwcb-Tq for nwcrg@irtf.org; Mon, 06 Apr 2020 11:23:23 -0500
From: kavim.shroff@codeontechnologies.com
To: nwcrg@irtf.org
References: <CAPjWiCTrtZm=ipDFV1FF1br6dtfOt-bPyH9O5mSP9j-VShkgzA@mail.gmail.com>
In-Reply-To: <CAPjWiCTrtZm=ipDFV1FF1br6dtfOt-bPyH9O5mSP9j-VShkgzA@mail.gmail.com>
Date: Mon, 06 Apr 2020 17:23:20 +0100
Message-ID: <00ef01d60c2f$b0ebadc0$12c30940$@codeontechnologies.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_00F4_01D60C38.12B17550"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJld8d5XHkOYCylwSZuNmyUBlZss6dNbcyw
Content-Language: en-gb
X-AuthUser: kavim.shroff@codeontechnologies.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/nwcrg/zMgogS19-Aco-Gmv_HN0Fbg1sjA>
Subject: [nwcrg] Recent IPR disclosure against RFC 8681
X-BeenThere: nwcrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF Network Coding Research Group discussion list <nwcrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nwcrg/>
List-Post: <mailto:nwcrg@irtf.org>
List-Help: <mailto:nwcrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nwcrg>, <mailto:nwcrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Apr 2020 16:23:31 -0000

Dear All,

Following the email (here enclosed) of Marie-José Montpetit, co-chair of the NWCRG, we would like to point out the following:

1.	Code On Network Coding (“Code On”) is a small start-up having to promote a technology / ecosystem and manage a portfolio of over 100 patents (many of them licensed from over 10 Universities) with limited resources. 
2.	Despite not having in-house IP capabilities, Code On takes IPR activity very seriously and adheres to IETF policies to the best of its ability.  

3.	Code On understands that RFC 8179 provides that participants must disclose the existence of any IPR that they believe might cover the technology under discussion.  And it is in this spirit that Code On has consistently made IPR disclosures to the IETF since 2013, as per the links hereafter [https://datatracker.ietf.org/ipr/search/?draft= <https://datatracker.ietf.org/ipr/search/?draft=&rfc=&doctitle=&group=&holder=code+on&submit=holder&iprtitle=&patent=> &rfc=&doctitle=&group=&holder=code+on&submit=holder&iprtitle=&patent= ];[ https://www.linkedin.com/feed/update/urn:li:activity:6651777131674238976 ] 

4.	We strongly reject the statement of the Co-Chair that our disclosure was done against the rules:   

*	In general, all of our disclosures have followed the rules of RFC 8681;
*	In particular, this disclosure, relevant for a contribution made by somebody else, is a “timely disclosure” because it was made by us promptly once we reached a belief of the relevancy of this specific patent. 

5.	We reject the notion that we should have discussed the relevance of our disclosure either at a general meeting or in private emails, since the duty to disclose is personal to each participant.

 

6.	We will not comment on the Co-Chair’s statement that she did not disclose this IPR because she did not feel that there was a direct relationship between the patent and RLC from its initial ID to the RFC, but are surprised that a Co-Chair would comment on the relevance of a disclosure of one of the contributors in light of the fact that RFC 8179 specifically states that the IETF will make no determination about the validity of any particular IPR claim. 

Best

Kavim Shroff

M: +44 (0) 7932 073 224 | Skype: kavimds

 <http://www.codeontechnologies.com/> 

Information transmitted in or attached to this e-mail is intended only for the person or entity to which it is addressed, and may contain confidential and/or privileged material. If this email has been sent to you by mistake and you are not the intended recipient, please telephone or email the sender immediately and delete it from your system; do not read, copy or disclose its contents to anyone. No responsibility is accepted by Code On for any loss or damage arising in any way from the receipt or use of this e-mail or its attachments. Please note that all e-mail messages are subject to interception for lawful business purposes.

 <https://www.linkedin.com/company/code-on-technologies>  <https://twitter.com/codeontech?lang=en-gb> 

 

 

--- Begin Message ---
Dear NWCRG list members:

There was a recent IPR disclosure related to RFC 8681 - Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAME -
https://datatracker.ietf.org/ipr/4069/ 
This refers to a patent that has me as co-inventor.  This disclosure puts me in a delicate position as the patent co-inventor hence someone who should have disclosed the IPR and at the same time as the NWCRG chair who has been following the RLC development since 2015 and should be impartial.


(w/o chair hat on) 
1. This patent was submitted following some work I did as an MIT researcher in Muriel Médard’s laboratory and as such all my IPR is now owned by MIT for them to license at will. It is the licensee that made the disclosure, not MIT, not me or any of the patent co-inventors most of which have been or are still involved in the NWCRG. I was not made aware of the disclosure and have no relationship with the discloser but it puts me like I said in a delicate position.

According to RFC 8179 I should have disclosed this IPR at the time of the first ID in 2015 or throughout its evolution in the TSVWG from 2017-2019 and its presentations in the NWCRG meetings during that time if I felt that it was related to the work of RFC 8681. I understand the rules of 8179 for the need for timely disclosure. I did not disclose any IPR, as I did not feel that there was a direct relationship between the patent and RLC from its initial ID to the RFC. I also understand that the entity disclosing the IPR does not agree with me.

As far as I am concerned, the work that lead to the patent, where I was co-PI, was a master student thesis on using network coding (the MIT/Caltech RLNC) as an alternative to some of the layer 2 reliability mechanisms in WIMAX-2 networks with wider applicability to other wireless networks. The patent in thus on a novel implementation of coding not a code development. 

Since RFC 8681 is about developing a code with sliding windows and one that compared to the RLNC used in the patent does not allow for re-encoding. I believe our patent to be not directly related hence the reason I never pointed to the IPR. Of course the field of applicability of RFC 8681 includes wireless networks but also many others; applications are not crux of the RFC 8681. As a co-inventor I would have welcomed the discussion at our meetings or in private emails before the disclosures.


(with co-chair hat one) 
2. Other co-inventors from MIT and now Harvard and the disclosing entity, via one of their representatives, were present at almost every NWCRG meetings throughout the development of the RLC since 2015 and are part of our mailing list. Our patent or any other that are now disclosed against RFC 8681 was pointed out as being related. Some of the concerned participants even supported the RLC work. There is a rule in IETF that is followed by the IRTF about "timely disclosures" of related IPR. I am surprised that the disclosing entity took so long against the rule. And at every meeting we emphasized the IPR rules. 


Vincent and I welcome comments on this as we are strategizing for the future of the group.


mjm

Marie-José Montpetit, Ph.D.
marie@mjmontpetit.com <mailto:marie@mjmontpetit.com> 


--- End Message ---