Re: [Rmt] Posting of IPR Disclosure related to QUALCOMM Incorporated's Statement about IPR related to RFC 5170

"Luby, Michael" <luby@qualcomm.com> Tue, 06 October 2009 14:16 UTC

Return-Path: <luby@qualcomm.com>
X-Original-To: rmt@core3.amsl.com
Delivered-To: rmt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DD9D3A693E for <rmt@core3.amsl.com>; Tue, 6 Oct 2009 07:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.142
X-Spam-Level:
X-Spam-Status: No, score=-105.142 tagged_above=-999 required=5 tests=[AWL=1.456, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uQAkr-OBSm3I for <rmt@core3.amsl.com>; Tue, 6 Oct 2009 07:16:05 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by core3.amsl.com (Postfix) with ESMTP id B8A873A68E8 for <rmt@ietf.org>; Tue, 6 Oct 2009 07:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=luby@qualcomm.com; q=dns/txt; s=qcdkim; t=1254838663; x=1286374663; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Luby,=20Michael"=20<luby@qualcomm.com>|To:=20Vi ncent=20Roca=20<vincent.roca@inrialpes.fr>|CC:=20"rmt@iet f.org"=20<rmt@ietf.org>,=20"Luby,=20Michael"=20<luby@qual comm.com>|Date:=20Tue,=206=20Oct=202009=2007:17:40=20-070 0|Subject:=20Re:=20[Rmt]=20Posting=20of=20IPR=20Disclosur e=20related=20to=20QUALCOMM=0D=0A=20Incorporated's=20Stat ement=20about=20IPR=20related=20to=20RFC=205170 |Thread-Topic:=20[Rmt]=20Posting=20of=20IPR=20Disclosure =20related=20to=20QUALCOMM=0D=0A=20Incorporated's=20State ment=20about=20IPR=20related=20to=20RFC=205170 |Thread-Index:=20AcpGbmzW6L+rQpkIRqmS8ZTrYyZjqwAIVY1h |Message-ID:=20<C6F09F94.77CF%luby@qualcomm.com> |In-Reply-To:=20<4ACB197A.9090208@inrialpes.fr> |Accept-Language:=20en-US|Content-Language:=20en |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_C6F09F9477CFlubyqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5762"=3B=20a=3D"24620955"; bh=lZZ0Qo3y10psKn1gZZVP+JyiO+HqjieCGkbRFbjCvUA=; b=Dcn33lZ/WGDqZ0gRXAHBwOMtHYZXH20rxjwpM5ZSGMCNFG1FuIBJXdQ3 OJFZZ5YNG/nBxdJBKtg+Af0v+J2Ak6Kxm1+68W80HYJ+wrc0HRPSkbu9y jE5gBPlOAwanVVrZl+03sq825ZMaBqDt5fAuQPixK3nyoFCgtnXOQHptF 4=;
X-IronPort-AV: E=McAfee;i="5300,2777,5762"; a="24620955"
Received: from pdmz-ns-mip.qualcomm.com (HELO ithilien.qualcomm.com) ([199.106.114.10]) by wolverine01.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 06 Oct 2009 07:17:43 -0700
Received: from msgtransport03.qualcomm.com (msgtransport03.qualcomm.com [129.46.61.154]) by ithilien.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n96EHgNd023091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 6 Oct 2009 07:17:42 -0700
Received: from nasanexhub01.na.qualcomm.com (nasanexhub01.na.qualcomm.com [10.46.93.121]) by msgtransport03.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id n96EHgR5025684 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 6 Oct 2009 07:17:42 -0700
Received: from nasclexhc01.na.qualcomm.com (10.227.147.14) by nasanexhub01.na.qualcomm.com (10.46.93.121) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 6 Oct 2009 07:17:42 -0700
Received: from NASCLEXMB02.na.qualcomm.com ([10.227.144.113]) by nasclexhc01.na.qualcomm.com ([10.227.147.14]) with mapi; Tue, 6 Oct 2009 07:17:41 -0700
From: "Luby, Michael" <luby@qualcomm.com>
To: Vincent Roca <vincent.roca@inrialpes.fr>
Date: Tue, 06 Oct 2009 07:17:40 -0700
Thread-Topic: [Rmt] Posting of IPR Disclosure related to QUALCOMM Incorporated's Statement about IPR related to RFC 5170
Thread-Index: AcpGbmzW6L+rQpkIRqmS8ZTrYyZjqwAIVY1h
Message-ID: <C6F09F94.77CF%luby@qualcomm.com>
In-Reply-To: <4ACB197A.9090208@inrialpes.fr>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_C6F09F9477CFlubyqualcommcom_"
MIME-Version: 1.0
Cc: "Luby, Michael" <luby@qualcomm.com>, "rmt@ietf.org" <rmt@ietf.org>
Subject: Re: [Rmt] Posting of IPR Disclosure related to QUALCOMM Incorporated's Statement about IPR related to RFC 5170
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmt>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Oct 2009 14:16:12 -0000

Hi Vincent,
Yes, you got it with respect to the technical reason for the new patent information in the updated IPR declaration on RFC 5170.

With respect to 20080034273, it is not yet granted, it was published in February of 2008.

I'll get back to you as soon as practical in a different thread concerning http://www.ietf.org/mail-archive/web/fecframe/current/msg00516.html.
Best, Mike

On 10/6/09 3:18 AM, "Vincent Roca" <vincent.roca@inrialpes.fr> wrote:

Mike,

If I understand correctly, your point is related to the possibility
offered by RFC 5170 of having several encoding symbols per packet in
order to increase the number of symbols, which is useful to improve
LDPC erasure correction capabilities when dealing with small objects.
This is what I understand when comparing claims 25-29 of U.S. patent
20080034273 to our RFC.

And from your 09/23/2009 email, this is the "additional element added
to the ldpc draft" that justified the 10 additional patents of IPR
disclosure #1184 (WRT IPR disclosure #637).

So I recognize there is a problem here. Now that it has been clarified,
we can search for a solution that would hopefully satisfy both of us.

As I said, we always did our best to avoid infringing any patent we
were aware of... But of course, there's nothing we can do in case of
unpublished pending patents!

Especially when an IPR disclosure referring to an unpublished pending
patent is not quickly updated once the patent has been granted or
rejected. In this case, patent 20080034273 has been granted in February
2008, but the IPR disclosure only updated in September 2009. In the
meantime I haven't received any complain from you there could be an
issue with the "several symbols per packet" technique. It does not help!

This reminds me of the similar situation (unpublished pending patent)
we are currently experiencing with our FECFRAME document... So far I
didn't receive any clarification after my email sent mid-September:
http://www.ietf.org/mail-archive/web/fecframe/current/msg00516.html

Cheers,


  Vincent





Luby, Michael wrote:
> Hi Vincent,
>
> Claims 25-29 of U.S. patent publication number 20080034273 is related to the IPR issue.  Note that the patent specification for U.S. Patent 7,418,651 (and the patent specification for U.S. Provisional Patent Application No. 60/569,127 to which it claims priority and is incorporated by reference) also contains IPR related to claims 25-29 of U.S. patent publication number 20080034273.   It was realizing that the IPR in the patent specification for U.S. Patent 7,418,651 (and the patent specification for U.S. Provisional Patent Application No. 60/569,127) is relevant, based on looking more carefully at the drafts as they evolved and not the specific material in any one particular draft, that triggered the new DF IPR declaration in December 2007.
>
> Best, Mike
>