IETF Logo Mail Archive

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

"Hongyu Li (Julio)" <hongyu.li@huawei.com> Sat, 30 August 2014 07:29 UTC

Return-Path: <hongyu.li@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 E2F061A885D for <sfc@ietfa.amsl.com>; Sat, 30 Aug 2014 00:29:35 -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 Ii_f3shytlt1 for <sfc@ietfa.amsl.com>; Sat, 30 Aug 2014 00:29:34 -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 96C321A885C for <sfc@ietf.org>; Sat, 30 Aug 2014 00:29:33 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIW70813; Sat, 30 Aug 2014 07:29:32 +0000 (GMT)
Received: from SZXEMA404-HUB.china.huawei.com (10.82.72.36) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 30 Aug 2014 08:29:31 +0100
Received: from SZXEMA509-MBX.china.huawei.com ([169.254.1.59]) by SZXEMA404-HUB.china.huawei.com ([10.82.72.36]) with mapi id 14.03.0158.001; Sat, 30 Aug 2014 15:29:24 +0800
From: "Hongyu Li (Julio)" <hongyu.li@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: AQHPwSKarKFwlbPq2EakRGFWvH7bz5voxe5g
Date: Sat, 30 Aug 2014 07:29:24 +0000
Message-ID: <6EB34CB5D82C4645B826C56144826EA97EA5AF68@SZXEMA509-MBX.china.huawei.com>
References: <D021EA69.33AE5%jguichar@cisco.com>
In-Reply-To: <D021EA69.33AE5%jguichar@cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.114.234]
Content-Type: multipart/alternative; boundary="_000_6EB34CB5D82C4645B826C56144826EA97EA5AF68SZXEMA509MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/XD0RvQ897Gdjca18Yr7aSQeLFbA
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: Sat, 30 Aug 2014 07:29:36 -0000

Support

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