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

"Surendra Kumar (smkumar)" <smkumar@cisco.com> Fri, 28 March 2014 17:44 UTC

Return-Path: <smkumar@cisco.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 02E7B1A093A for <sfc@ietfa.amsl.com>; Fri, 28 Mar 2014 10:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level:
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 7YSLHuOClv7g for <sfc@ietfa.amsl.com>; Fri, 28 Mar 2014 10:44:33 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB3E1A0738 for <sfc@ietf.org>; Fri, 28 Mar 2014 10:44:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4027; q=dns/txt; s=iport; t=1396028671; x=1397238271; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=QlRzNA0qTRfdDouo0ChNuPOO7lvt+Y6MuFZ1DHyb/G4=; b=QQdIfoXhhF8aexI1Ty2mvj+UcjjVdTkIfu+nRXFHoDzn3b0n3latO7uF WeQ+c9SfDorZ4n6WcV8Vdg2qpDuTAb/2ZchKM4kdOc5wPvKAAX/jQXPsp rPtHiMdIOmcuP0gPFWX0Fv7N4lLz8M1q1vJzevH4zYHjms+gtXhHqXpA5 w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFAP6zNVOtJV2b/2dsb2JhbABZgwY7V7s6hzWBGBZ0giUBAQEEAQEBGlEEFwIBCBguJwslAgQBEod5DdFzF44mITqEOASUYoNsgTORAoMwgis
X-IronPort-AV: E=Sophos;i="4.97,752,1389744000"; d="scan'208";a="31228741"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-2.cisco.com with ESMTP; 28 Mar 2014 17:44:30 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s2SHiUa5030584 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 28 Mar 2014 17:44:30 GMT
Received: from xmb-aln-x09.cisco.com ([169.254.4.162]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.03.0123.003; Fri, 28 Mar 2014 12:44:30 -0500
From: "Surendra Kumar (smkumar)" <smkumar@cisco.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/n3iJI0NjZr1W+UAgAFLFgA=
Date: Fri, 28 Mar 2014 17:44:30 +0000
Message-ID: <CF5B02A4.366CC%smkumar@cisco.com>
References: <CF588C77.1E5F9%jguichar@cisco.com> <53343CD0.7090400@joelhalpern.com>
In-Reply-To: <53343CD0.7090400@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.21.87.33]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <1DBE8751064D014690CFEF633E8050FA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/FJwq6Kipuqc1TcwHhfybO2uQb1k
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 17:44:36 -0000

I agree with the chair's proposal as well.

Surendra.

On 3/27/14 7:59 AM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:

>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