Re: [sfc] WG acceptance of DC use case document
"Songhaibin (A)" <haibin.song@huawei.com> Mon, 05 May 2014 02:33 UTC
Return-Path: <haibin.song@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 218071A020F for <sfc@ietfa.amsl.com>; Sun, 4 May 2014 19:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.851
X-Spam-Level:
X-Spam-Status: No, score=-4.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, 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 XCBAOY2pd8qw for <sfc@ietfa.amsl.com>; Sun, 4 May 2014 19:33:39 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id EC0801A020E for <sfc@ietf.org>; Sun, 4 May 2014 19:33:38 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDU93363; Mon, 05 May 2014 02:33:35 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 5 May 2014 03:32:23 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 5 May 2014 03:33:34 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.85]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Mon, 5 May 2014 10:33:30 +0800
From: "Songhaibin (A)" <haibin.song@huawei.com>
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: WG acceptance of DC use case document
Thread-Index: AQHPZ4zZmOCxvX5ZJUmDR/KJEmbqkZsxO/8w
Date: Mon, 05 May 2014 02:33:29 +0000
Message-ID: <E33E01DFD5BEA24B9F3F18671078951F650C1329@nkgeml501-mbs.china.huawei.com>
References: <CF8B9E13.2033D%jguichar@cisco.com>
In-Reply-To: <CF8B9E13.2033D%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.138.41.49]
Content-Type: multipart/alternative; boundary="_000_E33E01DFD5BEA24B9F3F18671078951F650C1329nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/ghOXMV-LFxc0Wo_SzR5KHxb5Cqg
Subject: Re: [sfc] WG acceptance of DC use case document
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, 05 May 2014 02:33:41 -0000
Dear SFC Chairs, I have one logistic question, while the object of this call for adoption action is draft-kumar-sfc-dc-use-cases-01, why does the working group document draft-ietf-sfc-dc-use-cases-00 have the same text with draft-kumar-sfc-dc-use-cases-02? Did the WG call for the adoption of draft-kumar-sfc-dc-use-cases-02? Or I missed that email from the list? Best Regards! -Haibin From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Jim Guichard (jguichar) Sent: Sunday, May 04, 2014 7:35 PM To: sfc@ietf.org Subject: [sfc] WG acceptance of DC use case document Greetings: Thank you for your responses on the call for adoption of draft-kumar-sfc-dc-use-cases. Overall there seems to be general consensus that the document provides relevant content and is a good baseline for documenting both SP and Enterprise/cloud use cases and should serve as the basis for a WG document. While several folks have expressed concern that particular content is currently missing from the document, please note that the omission of content is normal process and the WG is expected to modify the document until there is WG consensus that the content is solid and complete. Therefore, if you believe there is content missing please have that discussion either directly with the authors or (preferably) on the mailing list so that all concerns become addressed and reflected (as appropriate) within the document. Authors, please post a new version as draft-ietf-sfc-dc-use-cases-00. Jim & Thomas.
- [sfc] WG acceptance of DC use case document Jim Guichard (jguichar)
- Re: [sfc] WG acceptance of DC use case document Songhaibin (A)
- Re: [sfc] WG acceptance of DC use case document Loa Andersson
- Re: [sfc] WG acceptance of DC use case document Songhaibin (A)
- Re: [sfc] WG acceptance of DC use case document Loa Andersson
- Re: [sfc] WG acceptance of DC use case document Jim Guichard (jguichar)