IETF Logo Mail Archive

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

Cathy Zhang <Cathy.H.Zhang@huawei.com> Wed, 27 August 2014 18:06 UTC

Return-Path: <Cathy.H.Zhang@huawei.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 4E6EA1A00FA for <sfc@ietfa.amsl.com>; Wed, 27 Aug 2014 11:06:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.868
X-Spam-Level:
X-Spam-Status: No, score=-4.868 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 AkFlzJ7E6xJy for <sfc@ietfa.amsl.com>; Wed, 27 Aug 2014 11:06:25 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605341A1F20 for <sfc@ietf.org>; Wed, 27 Aug 2014 11:06:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIU49589; Wed, 27 Aug 2014 18:06:22 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.212.94.49) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 27 Aug 2014 19:06:21 +0100
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.137]) by SJCEML703-CHM.china.huawei.com ([169.254.5.229]) with mapi id 14.03.0158.001; Wed, 27 Aug 2014 11:06:16 -0700
From: Cathy Zhang <Cathy.H.Zhang@huawei.com>
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: Call for WG adoption of draft-merged-sfc-architecture-02
Thread-Index: AQHPwSKarKFwlbPq2EakRGFWvH7bz5vkwL/A
Date: Wed, 27 Aug 2014 18:06:16 +0000
Message-ID: <A2C96F6779E6A041BC7023CC207FC99418F7BB46@SJCEML702-CHM.china.huawei.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:
x-originating-ip: [10.212.145.75]
Content-Type: multipart/alternative; boundary="_000_A2C96F6779E6A041BC7023CC207FC99418F7BB46SJCEML702CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/Mfh3y6y0XkqQIkXvtzOtD7QNDiw
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 18:06:28 -0000

Support.

Cathy

From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Jim Guichard (jguichar)
Sent: Tuesday, August 26, 2014 4: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