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

Zhen Cao <zehn.cao@gmail.com> Tue, 01 April 2014 02:58 UTC

Return-Path: <zehn.cao@gmail.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 C9F2D1A0931 for <sfc@ietfa.amsl.com>; Mon, 31 Mar 2014 19:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 4tg1F2wSadE5 for <sfc@ietfa.amsl.com>; Mon, 31 Mar 2014 19:58:48 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 8211B1A091D for <sfc@ietf.org>; Mon, 31 Mar 2014 19:58:48 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id f51so8323672qge.2 for <sfc@ietf.org>; Mon, 31 Mar 2014 19:58:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=btoauKXzw+6fmUBaMHx0bAmqb4m5ggJKFJHOfxspE/c=; b=o3MMr91/thO0cZXkGRAHq6PhUCdfy8NednRkIA2k8ZnEi05z13zvGeT4KJ1dddNgeS ADNmOvPO7vRXI0ULzHXiQxuufLEvHfv0oL9acViQdN7owca0eK2CPopt+HOYP0aX+rug BCB6Nz9aQfy09a/DRQ/nEcELivtZL9e63q7tiFN2o67hwxdjYZSzN8/0gb0M3vP7PQ4T vXEBJCWGnjqes3kap+aq26ZRL9Wt0Pjshu5sJibICZrHTLWuYSjbDAy12EhwklKGxHv7 LVBmgOvRzXycIYIHhy/SAKstmYGApIxeZ2OtBNOgoDqRaCfeGn4PJuB/PPxHbIclU78j 3XYg==
MIME-Version: 1.0
X-Received: by 10.224.7.199 with SMTP id e7mr13009264qae.58.1396321125089; Mon, 31 Mar 2014 19:58:45 -0700 (PDT)
Received: by 10.96.111.169 with HTTP; Mon, 31 Mar 2014 19:58:44 -0700 (PDT)
In-Reply-To: <2691CE0099834E4A9C5044EEC662BB9D4536BB5B@dfweml701-chm.china.huawei.com>
References: <CF588C77.1E5F9%jguichar@cisco.com> <CAProHARwm+vZC0YboprVMM94BCrdKXOR7m0GUA5KTxu08hKJ0w@mail.gmail.com> <53358F53.2030409@joelhalpern.com> <CF5B2896.1E7AC%jguichar@cisco.com> <94C682931C08B048B7A8645303FDC9F36F5448455F@PUEXCB1B.nanterre.francetelecom.fr> <2691CE0099834E4A9C5044EEC662BB9D4536BB5B@dfweml701-chm.china.huawei.com>
Date: Tue, 01 Apr 2014 10:58:44 +0800
Message-ID: <CAProHASbX++jVzKrsCChEyGnuZmJPoj96pfvnP1JY2pR73FPAw@mail.gmail.com>
From: Zhen Cao <zehn.cao@gmail.com>
To: Lucy yong <lucy.yong@huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/wxfWJ1iicCtFTeMqWmOLBMOYT8Y
Cc: "Jim Guichard (jguichar)" <jguichar@cisco.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "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: Tue, 01 Apr 2014 02:58:51 -0000

+ 1

and expecting an answer...

On Tue, Apr 1, 2014 at 12:07 AM, Lucy yong <lucy.yong@huawei.com> wrote:
> +1.
>
> -----Original Message-----
> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of mohamed.boucadair@orange.com
> Sent: Monday, March 31, 2014 1:42 AM
> To: Jim Guichard (jguichar); Joel M. Halpern; Zhen Cao
> Cc: sfc@ietf.org
> Subject: Re: [sfc] Progression of use case documents in the SFC WG
>
> How can you judge the support of your suggested position at this stage? What does mean "a lot of support" here?!.
>
> As a chair you should not bias the discussion.
>
> Cheers,
> Med
>
>>-----Message d'origine-----
>>De : sfc [mailto:sfc-bounces@ietf.org] De la part de Jim Guichard
>>(jguichar)
>>Envoyé : vendredi 28 mars 2014 18:25
>>À : Joel M. Halpern; Zhen Cao
>>Cc : sfc@ietf.org
>>Objet : Re: [sfc] Progression of use case documents in the SFC WG
>>
>>Thank you Joel. Yes, this is the approach we plan to take and I see a
>>lot of support for that on the list.
>>
>>On 3/28/14, 11:03 AM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:
>>
>>>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
>>>>
>>>
>>>_______________________________________________
>>>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
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc