Re: [sfc] IPR check for draft-quinn-sfc-problem-statement
Chris Frederick <cfrederick@sandvine.com> Mon, 27 January 2014 14:27 UTC
Return-Path: <cfrederick@sandvine.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 1E7221A0236 for <sfc@ietfa.amsl.com>; Mon, 27 Jan 2014 06:27:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level:
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535] 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 41pPh_bu3TCM for <sfc@ietfa.amsl.com>; Mon, 27 Jan 2014 06:27:50 -0800 (PST)
Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) by ietfa.amsl.com (Postfix) with ESMTP id D20431A013F for <sfc@ietf.org>; Mon, 27 Jan 2014 06:27:49 -0800 (PST)
Received: from WTL-EXCHP-2.sandvine.com ([fe80::68ac:f071:19ff:3455]) by WTL-EXCHP-3.sandvine.com ([fe80::3c39:d305:d721:f00a%16]) with mapi id 14.01.0339.001; Mon, 27 Jan 2014 09:27:46 -0500
From: Chris Frederick <cfrederick@sandvine.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Thread-Topic: [sfc] IPR check for draft-quinn-sfc-problem-statement
Thread-Index: AQHPFtu2O3ornJShr0OlqV+EtD9b+pqP/DAA//+Ae4CAACuAgIAAeVkAgAAAywCAAB6YAIAAApGAgACjNECABo4hAIABM8hw
Date: Mon, 27 Jan 2014 14:27:46 +0000
Message-ID: <802F0FD88084CC4D82A0663874219D1A1887F398@wtl-exchp-2.sandvine.com>
References: <CF041613.235C%kegray@cisco.com> <CF043A3F.2D1AD%smkumar@cisco.com> <1E714095C88C9D408749A723A59CF6ED1C06E441@SJEXCHMB12.corp.ad.broadcom.com> <8F9A3BC8F79F244DB44EC1569235CB4F79FCC918@ORD1EXD04.RACKSPACE.CORP> <64BC961C-E325-40C4-BFFF-0F4F395FF68F@cisco.com> <CF045A51.31AA%michsmit@cisco.com> <802F0FD88084CC4D82A0663874219D1A1887DF44@wtl-exchp-2.sandvine.com> <68BA82B4-DA2E-441B-A2FA-9138711940EA@cisco.com>
In-Reply-To: <68BA82B4-DA2E-441B-A2FA-9138711940EA@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [198.91.160.188]
Content-Type: multipart/alternative; boundary="_000_802F0FD88084CC4D82A0663874219D1A1887F398wtlexchp2sandvi_"
MIME-Version: 1.0
Cc: Thomas Narten <narten@us.ibm.com>, "sfc@ietf.org" <sfc@ietf.org>, "Jim Guichard (jguichar)" <jguichar@cisco.com>, "Michael Smith (michsmit)" <michsmit@cisco.com>, Brad McConnell <bmcconne@rackspace.com>, "Paul Quinn (paulq)" <paulq@cisco.com>
Subject: Re: [sfc] IPR check for draft-quinn-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, 27 Jan 2014 14:27:56 -0000
Hi Carlos, I was trying to draw a distinction between IPR related to the 'process of actual chaining' (which it's not) and IPR related to the granular selection of 'what gets chained' (which it is). Thx for the pointer to the proper form, I'm new here + still getting my bearings. Best, /c From: Carlos Pignataro (cpignata) [mailto:cpignata@cisco.com] Sent: Sunday, January 26, 2014 10:00 AM To: Chris Frederick Cc: Michael Smith (michsmit); Paul Quinn (paulq); Brad McConnell; Thomas Narten; Jim Guichard (jguichar); sfc@ietf.org Subject: Re: [sfc] IPR check for draft-quinn-sfc-problem-statement Chris, Just to be clear -- when you say "This is not related to SFC specifically", are you acknowledging that you know of no IPR with subject matter related to draft-quinn-sfc-problem-statement-02.txt? Also, if there is any IPR to be disclosed, the actual disclosure should be done at http://www.ietf.org/ipr/file-disclosure.html and not on the WG mailing list. Thanks, -- Carlos. On Jan 22, 2014, at 11:07 AM, Chris Frederick <cfrederick@sandvine.com<mailto:cfrederick@sandvine.com>> wrote: Hello, Sandvine has intellectual property related to the granular steering of traffic flows, specifically where the session has been established. This technique enables steering on the basis of application, content, etc, vs. just the port that would be seen in the initial SYN packet. This is outlined here: http://www.google.com/patents/WO2004086714A1?cl=en This is not related to SFC specifically but I bring it to your attention as this technique can be used to select flows that would then be redirected through a service function chain or path; Sandvine uses this mechanism in our own SFC implementation for example. Best regards, Chris Frederick Director, Technology Partnerships cfrederick@sandvine.com <mailto:cfrederick@sandvine.comSee> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Michael Smith (michsmit) Sent: Tuesday, January 21, 2014 8:10 PM To: Paul Quinn (paulq); Brad McConnell Cc: Thomas Narten; Jim Guichard (jguichar); sfc@ietf.org<mailto:sfc@ietf.org> Subject: Re: [sfc] IPR check for draft-quinn-sfc-problem-statement I'm not aware of any either. Michael From: "Paul Quinn (paulq)" <paulq@cisco.com<mailto:paulq@cisco.com>> Date: Tuesday, January 21, 2014 5:00 PM To: Brad McConnell <bmcconne@rackspace.com<mailto:bmcconne@rackspace.com>> Cc: Thomas Narten <narten@us.ibm.com<mailto:narten@us.ibm.com>>, "Jim Guichard (jguichar)" <jguichar@cisco.com<mailto:jguichar@cisco.com>>, "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto:sfc@ietf.org>> Subject: Re: [sfc] IPR check for draft-quinn-sfc-problem-statement Me neither. Paul On Jan 21, 2014, at 6:11 PM, Brad McConnell <bmcconne@rackspace.com<mailto:bmcconne@rackspace.com>> wrote: I'm not aware of any. Thank you, Brad McConnell ________________________________ From: sfc [sfc-bounces@ietf.org<mailto:sfc-bounces@ietf.org>] on behalf of Rajeev Manur [rmanur@broadcom.com<mailto:rmanur@broadcom.com>] Sent: Tuesday, January 21, 2014 5:08 PM To: Jim Guichard (jguichar) Cc: Thomas Narten; sfc@ietf.org<mailto:sfc@ietf.org> Subject: Re: [sfc] IPR check for draft-quinn-sfc-problem-statement +1 Thanks! --Rajeev From: sfc [mailto:sfc-bounces@ietf.org<mailto:bounces@ietf.org>] On Behalf Of Surendra Kumar (smkumar) Sent: Tuesday, January 21, 2014 2:54 PM To: Jim Guichard (jguichar) Cc: Thomas Narten; sfc@ietf.org<mailto:sfc@ietf.org> Subject: Re: [sfc] IPR check for draft-quinn-sfc-problem-statement +1 Surendra. From: "Ken Gray (kegray)" <kegray@cisco.com<mailto:kegray@cisco.com>> Date: Tuesday, January 21, 2014 12:18 PM To: Thomas Nadeau <tnadeau@lucidvision.com<mailto:tnadeau@lucidvision.com>>, "Jim Guichard (jguichar)" <jguichar@cisco.com<mailto:jguichar@cisco.com>> Cc: Thomas Narten <narten@us.ibm.com<mailto:narten@us.ibm.com>>, "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto:sfc@ietf.org>> Subject: Re: [sfc] IPR check for draft-quinn-sfc-problem-statement Ditto From: Thomas Nadeau <tnadeau@lucidvision.com<mailto:tnadeau@lucidvision.com>> Date: Tuesday, January 21, 2014 2:54 PM To: "Jim Guichard (jguichar)" <jguichar@cisco.com<mailto:jguichar@cisco.com>> Cc: Thomas Narten <narten@us.ibm.com<mailto:narten@us.ibm.com>>, "sfc@ietf.org<mailto:sfc@ietf.org>" <sfc@ietf.org<mailto:sfc@ietf.org>> Subject: Re: [sfc] IPR check for draft-quinn-sfc-problem-statement None from my end. On Jan 21, 2014:2:05 PM, at 2:05 PM, Jim Guichard (jguichar) <jguichar@cisco.com<mailto:jguichar@cisco.com>> wrote: This email serves as a poll for knowledge of any IPR that applies to draft [1], to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email whether or not you are aware of any relevant IPR. The draft will not be adopted until a response has been received from each author and major contributor. If you are on the SFC WG mailing list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thank you, Jim & Thomas SFC chairs [1] http://tools.ietf.org/id/draft-quinn-sfc-problem-statement-02.txt _______________________________________________ sfc mailing list sfc@ietf.org<mailto:sfc@ietf.org> https://www.ietf.org/mailman/listinfo/sfc _______________________________________________ sfc mailing list sfc@ietf.org<mailto:sfc@ietf.org> https://www.ietf.org/mailman/listinfo/sfc _______________________________________________ sfc mailing list sfc@ietf.org<mailto:sfc@ietf.org> https://www.ietf.org/mailman/listinfo/sfc
- [sfc] IPR check for draft-quinn-sfc-problem-state… Jim Guichard (jguichar)
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Thomas Nadeau
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Ken Gray (kegray)
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Surendra Kumar (smkumar)
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Rajeev Manur
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Brad McConnell
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Paul Quinn (paulq)
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Navindra Yadav
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Michael Smith (michsmit)
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Chris Frederick
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Kevin Glavin
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Hongyu Li (Julio)
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Puneet Agarwal
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… christian.jacquenet
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Carlos Pignataro (cpignata)
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Carlos Pignataro (cpignata)
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Chris Frederick
- Re: [sfc] IPR check for draft-quinn-sfc-problem-s… Chris Frederick