Re: [sfc] IPR related to draft-ietf-sfc-problem-statement

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Mon, 05 May 2014 03:18 UTC

Return-Path: <cpignata@cisco.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 911C41A022A for <sfc@ietfa.amsl.com>; Sun, 4 May 2014 20:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.151
X-Spam-Level:
X-Spam-Status: No, score=-15.151 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 OSl5pwG5fwNK for <sfc@ietfa.amsl.com>; Sun, 4 May 2014 20:18:23 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id EDDB31A022B for <sfc@ietf.org>; Sun, 4 May 2014 20:18:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19532; q=dns/txt; s=iport; t=1399259900; x=1400469500; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=/e+XxG3Lw9qsNJGQSz6ZnISJz3EkuEXz2lFxIn6UsDg=; b=Jr3o0jMIWKQ70sVWL3zLXi8Mpf62cAksfGS3l0It63uZoPQAfP5vKNlZ kK4+JZ2XZq/o3E4WlD+2AbsfNVqjEdvO7cRGy+TkUocpQzSdm30SClfV8 w3V6eRBQgCgklmM4B7QCPiqQ0dm010Gx9NX/kzeWvGrqRWpeqp7udFzv4 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap8IAJABZ1OtJV2b/2dsb2JhbABYgkJET1iqIgEBAQEBAQUBklEBhziBFhZ0giUBAQEEAQEBawsQAgEIEQEDAQEoByEGCxQDBggCBA4FCRKIEgMRDcNVDYZEF4VWhmWBNRACAUsEBgGDKoEVBJdCgXKNF4VdgzRtgUI
X-IronPort-AV: E=Sophos;i="4.97,984,1389744000"; d="scan'208,217";a="319319892"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP; 05 May 2014 03:18:19 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s453IJ70027928 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 5 May 2014 03:18:19 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.230]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Sun, 4 May 2014 22:18:18 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] IPR related to draft-ietf-sfc-problem-statement
Thread-Index: AQHPaBCoBiIR3LM1WEu47gblHIsyrw==
Date: Mon, 05 May 2014 03:18:18 +0000
Message-ID: <0C1E7E86-07D7-45B0-B49D-391A2E6D8833@cisco.com>
References: <94C682931C08B048B7A8645303FDC9F36F58B44EEF@PUEXCB1B.nanterre.francetelecom.fr> <15840_1398406976_5359FF40_15840_14055_1_5af784ba-d2f3-4684-ba30-1e4bcb8f9c3b@OPEXCLILH01.corporate.adroot.infra.ftgroup> <3B0A1BED22CAD649A1B3E97BE5DDD68B5A6F5984@szxema506-mbs.china.huawei.com> <C9B5F12337F6F841B35C404CF0554ACB5FEBA91F@SZXEMA509-MBS.china.huawei.com> <BCFAF839-F091-4FBB-9B60-AB144E55D0F6@affirmednetworks.com> <4A95BA014132FF49AE685FAB4B9F17F645CFFA6E@dfweml701-chm.china.huawei.com> <CAA=duU1TpLjw_j+YeK3tPECBHhowFPbZh6b=zEa=v9ZAaX+MFA@mail.gmail.com>
In-Reply-To: <CAA=duU1TpLjw_j+YeK3tPECBHhowFPbZh6b=zEa=v9ZAaX+MFA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.210.5]
Content-Type: multipart/alternative; boundary="_000_0C1E7E8607D745B0B49D391A2E6D8833ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/XhnGaN8ytm3OWs8JC3XhbroqXrU
Cc: "Andrew G. Malis" <agmalis@gmail.com>, Med Boucadair <mohamed.boucadair@orange.com>, Ron Parker <Ron_Parker@affirmednetworks.com>, Linda Dunbar <linda.dunbar@huawei.com>
Subject: Re: [sfc] IPR related to draft-ietf-sfc-problem-statement
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 May 2014 03:18:25 -0000

SFCers, Thomas,

I think the line of reasoning proposed at the beginning of this thread is not only fallacious but also quite dangerous.

The first email on this thread from Med is basically saying/implying that an existing IPR disclosure for draft-ietf-sfc-problem-statement applies to a particular section of that document only (Section 3), and also that consequently that specific Section ought to be removed (regardless of licensing terms of that IPR disclosure). Both are, IMHO, non-sequitur.

I am not a lawyer and I do not play one on this list -- however, it *cannot* be inferred from the IPR disclosure that the IPR only applies to Section 3. Similarly, it cannot be concluded as a consequence that a Section of a document should be surgically removed. Both statements are misleading.

There are many reasons for which an IPR disclosure can apply to a Problem Statement document, to a Use Case document, to a Requirements document, and of course to an Architecture and Protocol documents. I think it is dangerous to correlate the IPR to a specific section, and even worst to a particular action concerning such section. You can see other examples searching at https://datatracker.ietf.org/ipr/search/

The IPR disclosure points to Patent No: 7200679, that subject matter *may* apply, and all of us should consider this and make an assessment on the WGLC. However, the oversimplification below is incorrect and harmful.

More importantly, there is really not full consensus (to my knowledge, ADs please clarify otherwise) regardless the transitive nature of IPR disclosures and their terms. The disclosure applies to draft-quinn-sfc-problem-statement-02, and there is no explicit disclosure for any version of draft-ietf-sfc-problem-statement. That ought to be clarified. See for example the discussion at http://www.ietf.org/mail-archive/web/ipr-wg/current/msg06187.html

My 2¢,

Carlos.

On Apr 30, 2014, at 3:18 PM, Andrew G. Malis <agmalis@gmail.com<mailto:agmalis@gmail.com>> wrote:

I also agree with everyone else on this thread.

Cheers,
Andy


On Wed, Apr 30, 2014 at 1:06 PM, Linda Dunbar <linda.dunbar@huawei.com<mailto:linda.dunbar@huawei.com>> wrote:
+1.

Linda

From: sfc [mailto:sfc-bounces@ietf.org<mailto:sfc-bounces@ietf.org>] On Behalf Of Ron Parker
Sent: Saturday, April 26, 2014 11:19 AM
To: Liushucheng (Will)
Cc: Jiangyuanlong; BOUCADAIR Mohamed IMT/OLN; sfc@ietf.org<mailto:sfc@ietf.org>; christian.jacquenet@orange.com<mailto:christian.jacquenet@orange.com>

Subject: Re: [sfc] IPR related to draft-ietf-sfc-problem-statement


+1

  Ron


On Apr 25, 2014, at 9:21 PM, "Liushucheng (Will)" <liushucheng@huawei.com<mailto:liushucheng@huawei.com>> wrote:
+1.

According to what we have agreed on the charter about the PS,
 “This document will provide a summary of the
problem space to be addressed by the SFC working group including
example high-level use cases. Additionally, the working group will
normalize nomenclature and definitions for service function chaining.”
The part related to explicit architecture should be merged into the architecture document.

Regards,
Will (Shucheng LIU)

From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Jiangyuanlong
Sent: Friday, April 25, 2014 7:35 PM
To: christian.jacquenet@orange.com<mailto:christian.jacquenet@orange.com>; BOUCADAIR Mohamed IMT/OLN; sfc@ietf.org<mailto:sfc@ietf.org>
Subject: Re: [sfc] IPR related to draft-ietf-sfc-problem-statement

+1, Section 3 addresses the architectural elements, which should be considered in a separate architecture document.

From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of christian.jacquenet@orange.com<mailto:christian.jacquenet@orange.com>
Sent: Friday, April 25, 2014 2:23 PM
To: BOUCADAIR Mohamed IMT/OLN; sfc@ietf.org<mailto:sfc@ietf.org>
Subject: Re: [sfc] IPR related to draft-ietf-sfc-problem-statement

WG,

I’d like to second Med’s comment: an IPR disclosure is a bit incongruous for a document that is supposed to document a problem statement and only a problem statement. From this perspective, the current Section 3 is no less misplaced.

Cheers,

Christian.

De : sfc [mailto:sfc-bounces@ietf.org] De la part de mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
Envoyé : jeudi 24 avril 2014 08:27
À : sfc@ietf.org<mailto:sfc@ietf.org>
Objet : [sfc] IPR related to draft-ietf-sfc-problem-statement

Dear all,

When checking the tracker, I found there is an IPR disclosure for the problem statement document:
https://datatracker.ietf.org/ipr/search/?option=document_search&id=draft-ietf-sfc-problem-statement

I’m surprised to see such disclosure for a document that is supposed to describe only problems (except section 3).

I’m re-iterating my comment to remove section 3 from the PS draft as it seems this is the only part that is close to the solution part than the problem discussion.

Cheers,
Med


_______________________________________________
sfc mailing list
sfc@ietf.org<mailto:sfc@ietf.org>
https://www.ietf.org/mailman/listinfo/sfc