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

"Diego R. Lopez" <diego@tid.es> Sat, 29 March 2014 19:08 UTC

Return-Path: <diego@tid.es>
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 E2B8B1A06B8 for <sfc@ietfa.amsl.com>; Sat, 29 Mar 2014 12:08:39 -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 U0HdUzPXoYus for <sfc@ietfa.amsl.com>; Sat, 29 Mar 2014 12:08:36 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED951A07C5 for <sfc@ietf.org>; Sat, 29 Mar 2014 12:08:35 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0N3700EMZP678I@tid.hi.inet> for sfc@ietf.org; Sat, 29 Mar 2014 20:08:32 +0100 (MET)
Received: from dequeue_removeroute (tid.hi.inet [10.95.64.10]) by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 35.A3.03314.F2A17335; Sat, 29 Mar 2014 20:08:32 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0N3700EMTP678I@tid.hi.inet> for sfc@ietf.org; Sat, 29 Mar 2014 20:08:31 +0100 (MET)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.136]) by EX10-HTCAS8-MAD.hi.inet ([fe80::41c8:e965:8a6:de67%11]) with mapi id 14.03.0158.001; Sat, 29 Mar 2014 20:08:31 +0100
Date: Sat, 29 Mar 2014 19:08:30 +0000
From: "Diego R. Lopez" <diego@tid.es>
In-reply-to: <3B0A1BED22CAD649A1B3E97BE5DDD68B5A6F0D17@szxema506-mbs.china.huawei.com>
X-Originating-IP: [10.95.64.115]
To: Jiangyuanlong <jiangyuanlong@huawei.com>
Message-id: <ADCF5138-6393-47FB-B7D4-786D9C2CC290@tid.es>
Content-id: <4D775C283A8E4640845B5CBB41868D8E@hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset="utf-8"
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US, es-ES
Thread-topic: [sfc] Progression of use case documents in the SFC WG
Thread-index: AQHPSRxfEA3AATWG/kWi/n3iJI0NjZrzuQYAgAO6+YCAAO4TgA==
X-AuditID: 0a5f4068-b7fe58e000000cf2-be-53371a2f126c
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmkeLIzCtJLcpLzFFi42Lhinfg0jWQMg82+Def0eLJg63sDoweS5b8 ZApgjOKySUnNySxLLdK3S+DK+P/3M1vBPLOKydM2sDQwvjHpYuTkkBAwkdiwfRszhC0mceHe ejYQW0jgAKPE6z16XYxcQPZXRok/z18wQiQ2MkocvMIOYrMIqEpMWTCRBcRmA7IfNf8GiwsL OEksvTsbbCinQIRE0+XTjBALFCT+nHsMVi8ioCPxdc8lsBpmgRqJg6s3M3UxcnDwClhKrG60 hwibSWw/3gnWyisgKPFj8j0WkBJmAXWJKVNyIUrEJZpbb7JA2IoS0xY1gJUzCshKvJs/nxVi k7PEm8bbTBC2k8S90x+ZIK4RkFiy5zzU66ISLx//Y4V4dwGjxJ3HzWwTGCVmITljFpIzZiGc MQvJGbOQnLGAkXUVo1hxUlFmekZJbmJmTrqBoV5Gpl5mXmrJJkZIxGXsYFy+U+UQowAHoxIP b0GfabAQa2JZcWXuIUYJDmYlEd4d98yChXhTEiurUovy44tKc1KLDzEycXBKNTAGNVf0Te1M UF66c0V7fvHDGx8lPxf93W/DNPvSzCXS4ufNGMRn3YnKkWOZ8MXi9o1QtU/8z+bXpmzitXxV Fmz39XHrk2NnRHR3K9U27wqf/boksUZo4tUlXXo5UeHzzplvvljev+1j0PsL5RvmPNt67/vZ Fb+51r9/ea1J0MGpqO5csaiu793rSizFGYmGWsxFxYkAV11ziZYCAAA=
References: <CF588C77.1E5F9%jguichar@cisco.com> <533331D0.6020709@joelhalpern.com> <3B0A1BED22CAD649A1B3E97BE5DDD68B5A6F0D17@szxema506-mbs.china.huawei.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/IyZ1sXclZRmCBCnv-SjZYxttj0o
Cc: "Jim Guichard (jguichar)" <jguichar@cisco.com>, "Joel M. Halpern" <jmh@joelhalpern.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: Sat, 29 Mar 2014 19:08:40 -0000

Hi Yuanlong,

And therefore I'd say it deserves a section by itself...

Be goode,

On 29 Mar 2014, at 05:58 , Jiangyuanlong <jiangyuanlong@huawei.com> wrote:

> Joel,
> This seems like a general use case which fits into DC, broadband, mobility and etc.
> Cheers,
> Yuanlong
>
> -----Original Message-----
> From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Joel M. Halpern
> Sent: Thursday, March 27, 2014 4:00 AM
> To: Jim Guichard (jguichar); sfc@ietf.org
> Subject: Re: [sfc] Progression of use case documents in the SFC WG
>
> Where does the long-lived flows case we presented in London fit?
>
> Thank you,
> 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
>
> _______________________________________________
> sfc mailing list
> sfc@ietf.org
> https://www.ietf.org/mailman/listinfo/sfc


--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego@tid.es
Tel:    +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------------


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx