IETF Logo Mail Archive

Re: [sfc] Call for WG adoption of draft-merged-sfc-architecture-02

"Zarny, Myo" <Myo.Zarny@gs.com> Wed, 27 August 2014 21:23 UTC

Return-Path: <Myo.Zarny@gs.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 357EA1A02A6 for <sfc@ietfa.amsl.com>; Wed, 27 Aug 2014 14:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.568
X-Spam-Level:
X-Spam-Status: No, score=-7.568 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] 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 zlfPmtLMEBph for <sfc@ietfa.amsl.com>; Wed, 27 Aug 2014 14:22:54 -0700 (PDT)
Received: from mxe01.gs.com (mxe01.gs.com [204.4.178.104]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C26591A0141 for <sfc@ietf.org>; Wed, 27 Aug 2014 14:22:53 -0700 (PDT)
Received: from pps.filterd (gsppacdp01sd.idz.gs.com [127.0.0.1]) by gsppacdp01sd.idz.gs.com (8.14.5/8.14.5) with SMTP id s7RLL6Cs015059 for <sfc@ietf.org>; Wed, 27 Aug 2014 17:22:52 -0400
Received: from mxpcd02-public.ny.fw.gs.com ([148.86.97.79]) by gsppacdp01sd.idz.gs.com with ESMTP id 1p1kk0tr8t-1 for <sfc@ietf.org>; Wed, 27 Aug 2014 17:22:52 -0400
From: "Zarny, Myo" <Myo.Zarny@gs.com>
X-sendergroup: RELAYLIST
Received: from gshccdp15ex.firmwide.corp.gs.com ([10.135.172.93]) by cd02-mxp-vip-prod.ny.fw.gs.com with ESMTP; 27 Aug 2014 17:22:52 -0400
Received: from GSCMAMP19EX.firmwide.corp.gs.com ([139.172.38.36]) by gshccdp15ex.firmwide.corp.gs.com ([10.135.172.93]) with mapi; Wed, 27 Aug 2014 17:22:52 -0400
To: "'Jim Guichard (jguichar)'" <jguichar@cisco.com>, "'sfc@ietf.org'" <sfc@ietf.org>
Date: Wed, 27 Aug 2014 17:22:51 -0400
Thread-Topic: Call for WG adoption of draft-merged-sfc-architecture-02
Thread-Index: AQHPwSKarKFwlbPq2EakRGFWvH7bz5vk96SQ
Message-ID: <A3233753A4B65F43BCA1B64DA99A9C23070DD0CDF9@GSCMAMP19EX.firmwide.corp.gs.com>
References: <D021EA69.33AE5%jguichar@cisco.com>
In-Reply-To: <D021EA69.33AE5%jguichar@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-retentionstamp: Firmwide
Content-Type: multipart/alternative; boundary="_000_A3233753A4B65F43BCA1B64DA99A9C23070DD0CDF9GSCMAMP19EXfi_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.12.52, 1.0.27, 0.0.0000 definitions=2014-08-27_06:2014-08-27,2014-08-27,1970-01-01 signatures=0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/T0gJByTif_kzLFDTUgM96eQuCz8
Subject: Re: [sfc] Call for WG adoption of draft-merged-sfc-architecture-02
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, 27 Aug 2014 21:23:01 -0000

Support

From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Jim Guichard (jguichar)
Sent: 26 August 2014 7:41 AM
To: sfc@ietf.org
Subject: [sfc] Call for WG adoption of draft-merged-sfc-architecture-02

Greetings WG:

This message begins a two week call for WG adoption of draft-merged-sfc-architecture-02 [http://datatracker.ietf.org/doc/draft-merged-sfc-architecture/] ending September 9th 2014.

Please respond to the SFC mailing list with any statements of approval or disapproval.

As always, please note:
1.       This is not WG Last Call. The document is not final, and the WG is expected to modify the document's content until there is WG consensus that the content is solid. Therefore, please don't oppose adoption just because you want to see changes to its content.
2.       If you have objections to adoption of the document, please state your reasons why, and explain what it would take to address your concerns.
3.       If you have issues with the content, by all means raise those issues and we can begin a dialog about how best to address them.

v2.23.0 | Report a Bug | By Email