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

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 28 March 2014 15:04 UTC

Return-Path: <jmh@joelhalpern.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 B9A251A06DD for <sfc@ietfa.amsl.com>; Fri, 28 Mar 2014 08:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 OGQAWcQ_-eaI for <sfc@ietfa.amsl.com>; Fri, 28 Mar 2014 08:04:24 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id BA2F41A0739 for <sfc@ietf.org>; Fri, 28 Mar 2014 08:04:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id E65BC140A07; Fri, 28 Mar 2014 08:04:17 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-134-57.clppva.east.verizon.net [70.106.134.57]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 54779140A05; Fri, 28 Mar 2014 08:04:06 -0700 (PDT)
Message-ID: <53358F53.2030409@joelhalpern.com>
Date: Fri, 28 Mar 2014 11:03:47 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Zhen Cao <zehn.cao@gmail.com>
References: <CF588C77.1E5F9%jguichar@cisco.com> <CAProHARwm+vZC0YboprVMM94BCrdKXOR7m0GUA5KTxu08hKJ0w@mail.gmail.com>
In-Reply-To: <CAProHARwm+vZC0YboprVMM94BCrdKXOR7m0GUA5KTxu08hKJ0w@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/sF1xKd8WZ4Nr3hZmBT7dbtaAPps
Cc: "sfc@ietf.org" <sfc@ietf.org>
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: Fri, 28 Mar 2014 15:04:26 -0000

One aspect in the chairs proposal that struck me has particularly useful 
was keeping the use case document for specific partners separate.  That 
way, it is MUCH easier to liaise with 3GPP or the BBF on the aspects of 
the use cases that are important to them.

Yours,
Joel

On 3/28/14, 4:34 AM, Zhen Cao wrote:
> Dear Chairs,
>
> I do not know how we come to this conclusion given the below facts
> 1) Email discussion on January,
> http://www.ietf.org/mail-archive/web/sfc/current/msg00966.html, with
> many supports of moving forward the  document draft-liu-sfc-use-cases.
>
> 2) London discussion as per
> http://www.ietf.org/proceedings/89/minutes/minutes-89-sfc , where
> several people voice out that we need one document
>
> As for draft-liu-sfc-use-cases, I'd say it is not a simple 'general'
> use cases write-up, actually it has already merged with one mobility
> use case from Med, and it also describe the use cases from the
> abstract point of view, i.e. two angles that try to summarize the
> existing activities.
>
> Technically, one use cases document is much better for people both
> inside and outside to understand the sfc activities better. The
> draft-liu-sfc-use-cases serves this target very well. And many use
> cases are basically the same according the chaining logic, why we need
> so many...
>
> So based on previous discussion both on the list and f2f meeting,  I
> am suggesting that we move forward the general document and consider
> other documents in meanwhile as they turn out to be significant.
>
> Many thanks,
> zhen cao
> china mobile
>
>> 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  and
>> 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
>