Re: [sfc] Progression of use case documents in the SFC WG

Jiangyuanlong <jiangyuanlong@huawei.com> Sat, 29 March 2014 02:56 UTC

Return-Path: <jiangyuanlong@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 899ED1A0286 for <sfc@ietfa.amsl.com>; Fri, 28 Mar 2014 19:56:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 SPILnukq9RxA for <sfc@ietfa.amsl.com>; Fri, 28 Mar 2014 19:56:21 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A13451A002F for <sfc@ietf.org>; Fri, 28 Mar 2014 19:56:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCN51327; Sat, 29 Mar 2014 02:56:17 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 29 Mar 2014 02:55:35 +0000
Received: from SZXEMA403-HUB.china.huawei.com (10.82.72.35) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 29 Mar 2014 02:56:16 +0000
Received: from SZXEMA506-MBS.china.huawei.com ([169.254.4.41]) by SZXEMA403-HUB.china.huawei.com ([10.82.72.35]) with mapi id 14.03.0158.001; Sat, 29 Mar 2014 10:56:05 +0800
From: Jiangyuanlong <jiangyuanlong@huawei.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] Progression of use case documents in the SFC WG
Thread-Index: AQHPSRxfEA3AATWG/kWi/n3iJI0NjZr0gfcAgALedpA=
Date: Sat, 29 Mar 2014 02:56:03 +0000
Message-ID: <3B0A1BED22CAD649A1B3E97BE5DDD68B5A6F0CC8@szxema506-mbs.china.huawei.com>
References: <CF588C77.1E5F9%jguichar@cisco.com> <53343CD0.7090400@joelhalpern.com>
In-Reply-To: <53343CD0.7090400@joelhalpern.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.76.118]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/XBgQOYjaZSW0DOzXgT3lQIIOWlg
Subject: Re: [sfc] Progression of use case documents in the SFC WG
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, 29 Mar 2014 02:56:24 -0000

Hi Joel and all, 

The current recommendation is casting the narrow nets firstly.
Shouldn't we cast the wide net first and then the specific narrow nets?

Regards,
Yuanlong


-----Original Message-----
From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Joel M. Halpern
Sent: Thursday, March 27, 2014 10:59 PM
To: sfc@ietf.org
Subject: Re: [sfc] Progression of use case documents in the SFC WG

This looks like a good idea to me.
One wide net, and then specific narrow nets where appropriate.
Liaising to appropriate SDOs or fora with the narrow documents is also 
very helpful.

Yours,
Joel

On 3/26/14, 1:54 PM, Jim Guichard (jguichar) wrote:
> WG:
>
> In a message back in January, we (the chairs) proposed that the SFC WG
> handle the topic of use case documents as follows:
>
>     1) Have the WG develop one use case document that documents a small
>     number of representative use cases.  The document presented by
>     Hongyu Li at the Vancouver BOF could serve for this purpose
>     (http://datatracker.ietf.org/doc/draft-liu-service-chaining-use-cases).
>
>
>     3) For additional use cases not covered in 1) above, allow for a
>     small number of documents that are applicable to specific
>     environments (e.g.  mobility, data center, broadband, and so forth.)
>     These documents would provide more detailed information and
>     applicability of SFC to these specific environments, and would need
>     to go beyond what is covered in the general use case document (1).
>     Note that it is not the intention to have every potential use case
>     documented.
>
>
> Since then, and based on the presentations/discussion in London, it
> appears that we have a number of documents that warrant being developed
> as standalone documents. Specifically:
>
> 1) A use case document on mobility, e.g.,
> http://datatracker.ietf.org/doc/draft-haeffner-sfc-use-case-mobility/
>
> 2) A use case document on Data Centers, e.g.,
> http://datatracker.ietf.org/doc/draft-kumar-sfc-dc-use-cases/
>
> 3) Possibly a use case document on Broadband scenarios. However, use
> cases from a broadband perspective are being developed in the BBF (see
> the liaison statement at https://datatracker.ietf.org/liaison/1304/). We
> also have
> http://datatracker.ietf.org/doc/draft-meng-sfc-broadband-usecases/.  It
> does not seem appropriate to adopt a WG document on the topic of
> broadband (at least at this time) without clarifying the relationship
> between draft-meng-sfc-broadband-usecases and the BBF work. In addition,
> we would need to understand why two efforts - one in BBF and one in the
> IETF -- on the same topic would be appropriate. Hence, at the present
> time, we do not intend to adopt a WG document on broadband scenarios,
> and expect to receive primary guidance on this topic from the BBF.
>
> That leaves: http://datatracker.ietf.org/doc/draft-liu-sfc-use-cases/, a
> more general document. But that document includes text on three topics
> that would be covered in more detail elsewhere (broadband, mobile, and
> DC). While this document could contain pointers to the other documents,
> that leaves the document with very little standalone content -- raising
> the question of what should be done with it, or what content it could
> incorporate in order to be worthwhile as a standalone document.
>
> Thus, the chairs recommendation at this time is:
>
> 1) Call for WG adoption of draft-haeffner-sfc-use-case-mobility-00.txt
> and draft-kumar-sfc-dc-use-cases-00.txt as WG documents (target:
> informational).
>
> 2) Defer action on draft-liu-service-chaining-use-cases
> <http://datatracker.ietf.org/doc/draft-liu-service-chaining-use-cases>
> and draft-meng-sfc-broadband-usecases
> <http://datatracker.ietf.org/doc/draft-meng-sfc-broadband-usecases/> per
> the above discussion.
>
> Does this make sense?
>
> Jim & Thomas
>
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc
>

_______________________________________________
sfc mailing list
sfc@ietf.org
https://www.ietf.org/mailman/listinfo/sfc