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

Hui Deng <denghui02@gmail.com> Tue, 01 April 2014 03:59 UTC

Return-Path: <denghui02@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 6996B1A0955 for <sfc@ietfa.amsl.com>; Mon, 31 Mar 2014 20:59:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-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 MmkJKnedRhzZ for <sfc@ietfa.amsl.com>; Mon, 31 Mar 2014 20:59:53 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 9B9BE1A0947 for <sfc@ietf.org>; Mon, 31 Mar 2014 20:59:53 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id sa20so8833676veb.36 for <sfc@ietf.org>; Mon, 31 Mar 2014 20:59:50 -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; bh=35KhlLCLgofxuZxEddAB1ioJDKlisAT6itsGvduMQgo=; b=ngL7rm8IhtKlk3bOL9BpmvTAowm2Q9/eGO/b8r8BiX44GR4Ow1SAyLE2xdmWlecdYz M+bXeXEuoPMBzJl1LYJkS+CeagIGkJfY8kHX5dh0xuaGCwFw3+NwkbK62EfWPiJ0Qkcv n/qcXqfCDuojhqifM2Iq0LUhjArb8iELCE5Ih/9Z269uwcvZ6Kn2XdTlLunz8cm3sZFh Wrih8DS3JVzDPmD3A8EA7492pd2Q/Zf3gXH0EXgSNTBlO1g2FSQKz30WzgDb+GtPnN6A hRd8xSwRXRH+OWlz1mS5ZVK/sgu1cMfImKplwjUFDbWHq1bXCE0CDVXP0BoCuWnIuai6 voHg==
MIME-Version: 1.0
X-Received: by 10.220.106.84 with SMTP id w20mr6456573vco.18.1396324790107; Mon, 31 Mar 2014 20:59:50 -0700 (PDT)
Received: by 10.220.252.132 with HTTP; Mon, 31 Mar 2014 20:59:49 -0700 (PDT)
In-Reply-To: <CF588C77.1E5F9%jguichar@cisco.com>
References: <CF588C77.1E5F9%jguichar@cisco.com>
Date: Tue, 01 Apr 2014 11:59:49 +0800
Message-ID: <CANF0JMCb7XyRUBRX3LRFd-uSJ1DWT0jZjtDg=MtE-po-6-_VXw@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: "Jim Guichard (jguichar)" <jguichar@cisco.com>
Content-Type: multipart/alternative; boundary="047d7b3435c01b046004f5f33355"
Archived-At: http://mailarchive.ietf.org/arch/msg/sfc/GJUmfMLNCsUf-qDnMwpqRZfjG6M
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: Tue, 01 Apr 2014 03:59:56 -0000

Speaking as a non author of any drafts here, and also voice made during the
F2F meeting.

I am getting lost why IETF needs to document 3GPP components here, they
have already started their work, what we IETF usually do is just refer to
theirs document, this is how standard bodies work together today. Even if
we document here, they maynot agree with the text, are we asking 3GPP to
refer IETF's document about their scenario, that will be weird.

Even during the F2F meeting discussion, I heard from authors of mobility,
he is proposing a general case, ==> check with minutes.

So my recommendation is that one general case would help people to
understand better about technologies and their coherence.

Best regards,

-Hui



2014-03-27 1:54 GMT+08:00 Jim Guichard (jguichar) <jguichar@cisco.com>:

>  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
>
>