Re: [sfc] New Version Notification for draft-trossen-sfc-name-based-sff-01.txt
Ramin Khalili <ramin.khalili@huawei.com> Fri, 02 November 2018 15:01 UTC
Return-Path: <ramin.khalili@huawei.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD44E130DC1 for <sfc@ietfa.amsl.com>; Fri, 2 Nov 2018 08:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 advE8tyToOUX for <sfc@ietfa.amsl.com>; Fri, 2 Nov 2018 08:01:23 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBA8C1294D7 for <sfc@ietf.org>; Fri, 2 Nov 2018 08:01:23 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 2D9E41B22E06D; Fri, 2 Nov 2018 15:01:18 +0000 (GMT)
Received: from LHREML501-MBB.china.huawei.com ([10.201.109.51]) by lhreml706-cah.china.huawei.com ([10.201.108.47]) with mapi id 14.03.0415.000; Fri, 2 Nov 2018 15:01:18 +0000
From: Ramin Khalili <ramin.khalili@huawei.com>
To: "Trossen, Dirk" <Dirk.Trossen@InterDigital.com>, "Hugo, Dirk" <Dirk.von-Hugo@telekom.de>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt
Thread-Index: AQHUZlCnT02OHThu2EKJGILpi1WzfaUk9m0QgAGOOoCAExP0AIABIgCAgAHuhpA=
Date: Fri, 02 Nov 2018 15:01:17 +0000
Message-ID: <566C56D84391B845A5669C78BB642FC001440AF1@lhreml501-mbb>
References: <153980486541.27616.10379489791817114306.idtracker@ietfa.amsl.com> <DM6PR10MB2777AC96B185B8B7B24597FDF3F80@DM6PR10MB2777.namprd10.prod.outlook.com> <FRAPR01MB08012D78C3362F184DD2439AD1F90@FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE> <FRAPR01MB08016B4AE612D15FE2AEF3B3D1CD0@FRAPR01MB0801.DEUPRD01.PROD.OUTLOOK.DE> <DM6PR10MB2777F2FD3AB466F1B5F5D8F7F3CE0@DM6PR10MB2777.namprd10.prod.outlook.com>
In-Reply-To: <DM6PR10MB2777F2FD3AB466F1B5F5D8F7F3CE0@DM6PR10MB2777.namprd10.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.124.182.114]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/hmbXhFOfEuyAWmuU4zzO1NAZ9EA>
Subject: Re: [sfc] New Version Notification for draft-trossen-sfc-name-based-sff-01.txt
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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, 02 Nov 2018 15:01:26 -0000
Dear all, I agreed with Trossen and Hugo. I believe this SFC name base solution has interesting applications in 3GPP and could pave roads toward dynamic service function chaining, which is required in order to improve resource usage. Regards, Ramin -----Original Message----- From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Trossen, Dirk Sent: Thursday, November 01, 2018 10:17 AM To: Hugo, Dirk <Dirk.von-Hugo@telekom.de>; sfc@ietf.org Subject: Re: [sfc] New Version Notification for draft-trossen-sfc-name-based-sff-01.txt Dear Dirk, Many thanks for the response. Indeed, we have in mind to bring the discussion on describing control plane workflows as (named) SFCs into the eSBA study you mentioned below. Best, Dirk -----Original Message----- From: Hugo, Dirk Sent: 31 October 2018 15:59 To: Trossen, Dirk <Dirk.Trossen@InterDigital.com>; sfc@ietf.org Subject: RE: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt Dear Dirk and co-authors, Thanks for providing the useful draft again. I would like to point out the relation to 3GPPs 5G SBA use case again where network function services are introduced to be combined in a chain like manner to provide a communication service or logical network slice. Name-based addressing and routing would allow to select the optimal appropriate SF instance. I think thus it could be helpful for ongoing 3GPP SA2 study on 'Enhancements to the Service-Based Architecture' for Release 16 (TR 23.742). One minor comment for update is to refer in [_3GPP_SBA] to the actually approved version of 3GPP TS 29.500 (15.1.0) instead of draft (0.4.0) one. ;-) Thanks! Best Regards Dirk -----Original Message----- From: sfc [mailto:sfc-bounces@ietf.org] On Behalf Of Trossen, Dirk Sent: Donnerstag, 18. Oktober 2018 14:56 To: Service Function Chaining IETF list <sfc@ietf.org> Subject: [sfc] FW: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt All, Based on the input received during the Montreal meeting, we updated the name-based SFF draft (see below), providing significantly more detail on issues like SF registration, nSFF forwarding, local SF forwarding and alike. We also simplified yet focused the use case with reference to ongoing 3GPP Rel16 work. Please review and share comments on this draft version. Best, Dirk -----Original Message----- From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Sent: 17 October 2018 20:34 To: Purkayastha, Debashish <Debashish.Purkayastha@InterDigital.com>; Trossen, Dirk <Dirk.Trossen@InterDigital.com>; Purkayastha, Debashish <Debashish.Purkayastha@InterDigital.com>; Rahman, Akbar <Akbar.Rahman@InterDigital.com>; Trossen, Dirk <Dirk.Trossen@InterDigital.com> Subject: New Version Notification for draft-trossen-sfc-name-based-sff-01.txt A new version of I-D, draft-trossen-sfc-name-based-sff-01.txt has been successfully submitted by Debashish Purkayastha and posted to the IETF repository. Name: draft-trossen-sfc-name-based-sff Revision: 01 Title: Name-Based Service Function Forwarder (nSFF) component within SFC framework Document date: 2018-10-17 Group: Individual Submission Pages: 24 URL: https://www.ietf.org/internet-drafts/draft-trossen-sfc-name-based-sff-01.txt Status: https://datatracker.ietf.org/doc/draft-trossen-sfc-name-based-sff/ Htmlized: https://tools.ietf.org/html/draft-trossen-sfc-name-based-sff-01 Htmlized: https://datatracker.ietf.org/doc/html/draft-trossen-sfc-name-based-sff Diff: https://www.ietf.org/rfcdiff?url2=draft-trossen-sfc-name-based-sff-01 Abstract: Many stringent requirements are imposed on today's network, such as low latency, high availability and reliability in order to support several use cases such as IoT, Gaming, Content distribution, Robotics etc. Adoption of cloud and fog technology at the edge of the network allows operator to deploy a single "Service Function" to multiple "Execution locations". The decision to steer traffic to a specific location may change frequently based on load, proximity etc. Under the current SFC framework, steering traffic dynamically to the different execution end points require a specific 're-chaining', i.e., a change in the service function path reflecting the different IP endpoints to be used for the new execution points. In order to address this, we discuss separating the logical Service Function Path from the specific execution end points. This can be done by identifying the Service Functions using a name rather than a routable IP endpoint (or Layer 2 address). This draft describes the necessary extensions, additional functions and protocol details in SFF to handle name based relationships. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat _______________________________________________ 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] FW: New Version Notification for draft-tros… Trossen, Dirk
- Re: [sfc] New Version Notification for draft-tros… Dirk.von-Hugo
- Re: [sfc] New Version Notification for draft-tros… Dirk.von-Hugo
- Re: [sfc] New Version Notification for draft-tros… Trossen, Dirk
- Re: [sfc] New Version Notification for draft-tros… Ramin Khalili