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

<mohamed.boucadair@orange.com> Mon, 31 March 2014 06:42 UTC

Return-Path: <mohamed.boucadair@orange.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 4D2171A081D for <sfc@ietfa.amsl.com>; Sun, 30 Mar 2014 23:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Level:
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
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 u4Ptmk6V3BWC for <sfc@ietfa.amsl.com>; Sun, 30 Mar 2014 23:41:58 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias243.francetelecom.com [80.12.204.243]) by ietfa.amsl.com (Postfix) with ESMTP id 3750D1A081B for <sfc@ietf.org>; Sun, 30 Mar 2014 23:41:57 -0700 (PDT)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda13.si.francetelecom.fr (ESMTP service) with ESMTP id B40B11901DA; Mon, 31 Mar 2014 08:41:53 +0200 (CEST)
Received: from PUEXCH51.nanterre.francetelecom.fr (unknown [10.101.44.31]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 934B238404A; Mon, 31 Mar 2014 08:41:53 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.11]) by PUEXCH51.nanterre.francetelecom.fr ([10.101.44.31]) with mapi; Mon, 31 Mar 2014 08:41:53 +0200
From: mohamed.boucadair@orange.com
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, Zhen Cao <zehn.cao@gmail.com>
Date: Mon, 31 Mar 2014 08:41:51 +0200
Thread-Topic: [sfc] Progression of use case documents in the SFC WG
Thread-Index: AQHPSRxfEA3AATWG/kWi/n3iJI0NjZr2gpsAgABs1ID//+R0gIAD8Efg
Message-ID: <94C682931C08B048B7A8645303FDC9F36F5448455F@PUEXCB1B.nanterre.francetelecom.fr>
References: <CF588C77.1E5F9%jguichar@cisco.com> <CAProHARwm+vZC0YboprVMM94BCrdKXOR7m0GUA5KTxu08hKJ0w@mail.gmail.com> <53358F53.2030409@joelhalpern.com> <CF5B2896.1E7AC%jguichar@cisco.com>
In-Reply-To: <CF5B2896.1E7AC%jguichar@cisco.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.19.63615
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/ioLu0YJd4aPyxsa5xynPOenHgOw
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: Mon, 31 Mar 2014 06:42:00 -0000

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