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

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Sat, 29 March 2014 12:19 UTC

Return-Path: <cpignata@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 E1A491A04C2 for <sfc@ietfa.amsl.com>; Sat, 29 Mar 2014 05:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 iUM7WGcdqMtM for <sfc@ietfa.amsl.com>; Sat, 29 Mar 2014 05:19:16 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE911A04C1 for <sfc@ietf.org>; Sat, 29 Mar 2014 05:19:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11116; q=dns/txt; s=iport; t=1396095554; x=1397305154; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=DCLEc9eOSabLYsnKB7OlSB/jHU1DEz0DWpzsg8sXDw4=; b=EtyhUnKxM9FynT7cgxVFcuARar/EKBmft5kugI4jpiXWrmH0SDeB7ivz q0yyOLGHwetY+EAT50msITRZyRWW3pKxuba+EohJmfStkDuXyXR4MQDYM P/e25y3SBdGuvr868kv1O8gR70rXpRoHVZ5Jtv6hl6ZEW2IhdZTW2vyIz E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvoFAEO5NlOtJXG//2dsb2JhbABZgkJEO0sMrEKNToE/hzWBFBZ0giYBAQQBAQEaUQQHEAIBCD8HJwsUEQIEDgWHeQ3RLBeOK1AEB4MkgRQElGKDbIEzkQKDMIIr
X-IronPort-AV: E=Sophos; i="4.97,756,1389744000"; d="scan'208,217"; a="313795718"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-6.cisco.com with ESMTP; 29 Mar 2014 12:19:13 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s2TCJDtS010850 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <sfc@ietf.org>; Sat, 29 Mar 2014 12:19:13 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.99]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Sat, 29 Mar 2014 07:19:12 -0500
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>
Thread-Topic: [sfc] Progression of use case documents in the SFC WG
Thread-Index: AQHPS0kXEA3AATWG/kWi/n3iJI0NjQ==
Date: Sat, 29 Mar 2014 12:19:11 +0000
Message-ID: <2CD01C4C-F626-4BA6-9070-517A29908D5A@cisco.com>
References: <CF588C77.1E5F9%jguichar@cisco.com>
In-Reply-To: <CF588C77.1E5F9%jguichar@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.226.251]
Content-Type: multipart/alternative; boundary="_000_2CD01C4CF6264BA69070517A29908D5Aciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/21cgmKy6MqrKzYFwpB9ja7FFzyU
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: Sat, 29 Mar 2014 12:19:19 -0000

Jim, Thomas,

This sounds like a great approach. Thanks for organizing the use-case puzzle into this recommendation.

Thanks,

Carlos.

On Mar 26, 2014, at 1:54 PM, Jim Guichard (jguichar) <jguichar@cisco.com<mailto:jguichar@cisco.com>> 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<mailto:sfc@ietf.org>
https://www.ietf.org/mailman/listinfo/sfc