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

"Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com> Mon, 03 March 2014 09:28 UTC

Return-Path: <wim.henderickx@alcatel-lucent.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 A95211A0D36 for <sfc@ietfa.amsl.com>; Mon, 3 Mar 2014 01:28:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-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 l-C431xHypup for <sfc@ietfa.amsl.com>; Mon, 3 Mar 2014 01:28:20 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 7473B1A0BFC for <sfc@ietf.org>; Mon, 3 Mar 2014 01:28:20 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s239SGVp017805 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <sfc@ietf.org>; Mon, 3 Mar 2014 03:28:17 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s239SFA2002125 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <sfc@ietf.org>; Mon, 3 Mar 2014 10:28:15 +0100
Received: from FR711WXCHMBA07.zeu.alcatel-lucent.com ([169.254.3.10]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Mon, 3 Mar 2014 10:28:15 +0100
From: "Henderickx, Wim (Wim)" <wim.henderickx@alcatel-lucent.com>
To: sfc <sfc@ietf.org>
Thread-Topic: Mail regarding draft-quinn-sfc-problem-statement
Thread-Index: AQHPNsLnGEcyhjJB7EuhMkrx+LqLvQ==
Date: Mon, 03 Mar 2014 09:28:15 +0000
Message-ID: <CF3A09B8.B3102%wim.henderickx@alcatel-lucent.com>
Accept-Language: nl-BE, 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: [135.239.27.38]
Content-Type: multipart/alternative; boundary="_000_CF3A09B8B3102wimhenderickxalcatellucentcom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/Cb29LV0KxvUTRuqCTDIWLhoXI-8
Subject: [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: Mon, 03 Mar 2014 09:28:21 -0000

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.