IETF Logo Mail Archive

Re: [sfc] Mail regarding draft-quinn-sfc-problem-statement

"Jim Guichard (jguichar)" <jguichar@cisco.com> Wed, 05 March 2014 16:44 UTC

Return-Path: <jguichar@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 3D93E1A012A for <sfc@ietfa.amsl.com>; Wed, 5 Mar 2014 08:44:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.047
X-Spam-Level:
X-Spam-Status: No, score=-10.047 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, RP_MATCHES_RCVD=-0.547, 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 OMyhuKelMQKX for <sfc@ietfa.amsl.com>; Wed, 5 Mar 2014 08:43:58 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id 538291A00A3 for <sfc@ietf.org>; Wed, 5 Mar 2014 08:43:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4598; q=dns/txt; s=iport; t=1394037835; x=1395247435; h=from:to:subject:date:message-id:mime-version; bh=8/vXTerXTmM1WlBZsCys7NQFLDsGBcBN9D3GRSMHPVA=; b=fJ610eELtTkzw0uzVrFEUuFTZ7yt0bdDiz4WTa6cQzSwWAZqzBUJxuVy KqQNS7cZmiH0jlTt6HcaRdkTKvUcizMcehxZdRr0ySOzHLgbqrD/qUP8P K0dx2njO2VEWYHqZOw/dTRXzs0Bs3eliwmpT3FgWqQdPGvA7RvRS/G42/ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAB9UF1OtJXG8/2dsb2JhbABagkJEgRLBC4EZFnSCJQECBIELAQgEDQMBAig5FAkKBAESh3nOLxeOAAEBPhqENgSYPZIrgy2BcTk
X-IronPort-AV: E=Sophos; i="4.97,593,1389744000"; d="scan'208,217"; a="25129483"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by alln-iport-1.cisco.com with ESMTP; 05 Mar 2014 16:43:38 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id s25GhcCS006553 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 5 Mar 2014 16:43:38 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.35]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Wed, 5 Mar 2014 10:43:38 -0600
From: "Jim Guichard (jguichar)" <jguichar@cisco.com>
To: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>, sfc <sfc@ietf.org>
Thread-Topic: [sfc] Mail regarding draft-quinn-sfc-problem-statement
Thread-Index: AQHPOJIO0/NvL3RLrEKcgK4AVpxdXw==
Date: Wed, 05 Mar 2014 16:43:37 +0000
Message-ID: <CF3CBD9E.168A8%jguichar@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.98.43.181]
Content-Type: multipart/alternative; boundary="_000_CF3CBD9E168A8jguicharciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/XuVxXaM8wdlaBb9NWum4pT0Pfj0
Subject: Re: [sfc] Mail regarding 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: Wed, 05 Mar 2014 16:44:00 -0000

Hi Wim,

Could you be more specific in what you would like to see called out in the problem statement and any potential text that you feel is missing? Right now I see that in section 3 (bullet point 4) of the problem statement we have the follow text:

"In addition to sharing of information, the use of metadata addresses several of the issues raised in section 2, most notably the de-coupling of policy from the topology, and the need for per-service classification (and re-classification)".

Does this not capture what you are asking for?

From: <Henderickx>, "Wim (Wim)" <wim.henderickx@alcatel-lucent.com<mailto:wim.henderickx@alcatel-lucent.com>>
Date: Monday, March 3, 2014 at 4:28 AM
To: sfc <sfc@ietf.org<mailto:sfc@ietf.org>>
Subject: [sfc] Mail regarding draft-quinn-sfc-problem-statement

With respect to the problem statement I see a lot of discussions to use the meta-data header to convey information with respect to policies, etc to service fucntions.
If it is a problem we want to tackle in SFC we should also capture this in draft-quinn-sfc-problem-statement.

v2.23.0 | Report a Bug | By Email