From nobody Wed Oct 24 01:04:34 2018 Return-Path: X-Original-To: bec@ietfa.amsl.com Delivered-To: bec@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61B16130DF2 for ; Wed, 24 Oct 2018 01:04:32 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 WeGsKJeM3CQ5 for ; Wed, 24 Oct 2018 01:04:30 -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 AEF5F1293FB for ; Wed, 24 Oct 2018 01:04:30 -0700 (PDT) Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id B1D9B5C861924 for ; Wed, 24 Oct 2018 09:04:27 +0100 (IST) Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 24 Oct 2018 09:03:33 +0100 Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.52]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0399.000; Wed, 24 Oct 2018 16:03:26 +0800 From: "Liubing (Remy)" To: "bec@ietf.org" Thread-Topic: New draft: Service Function Chaining Applicability in Industrial Edge Computing Thread-Index: AdRrboF1TTE99kTkSaGvSpz/FwPvQg== Date: Wed, 24 Oct 2018 08:03:25 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.130.180.83] Content-Type: multipart/alternative; boundary="_000_BB09947B5326FE42BA3918FA28765C2EEB04FEDGGEMM506MBXchina_" MIME-Version: 1.0 X-CFilter-Loop: Reflected Archived-At: Subject: [Bec] New draft: Service Function Chaining Applicability in Industrial Edge Computing X-BeenThere: bec@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: BEC - Beyond Edge Computing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2018 08:04:32 -0000 --_000_BB09947B5326FE42BA3918FA28765C2EEB04FEDGGEMM506MBXchina_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, Please find our new draft on edge computing at https://datatracker.ietf.or= g/doc/draft-liu-iiot-sfc-edge-computing-applicability/ In the last edge computing side meeting, task indication and offloading are= identified as two of the gaps. In edge computing, except the applications have to be deployed at the edge = gateway due to timely response requirement, or the on cloud due to high com= putional complexity, the other applcations can be deployed at the edge gate= way, edge cloud or public cloud. Thus when the data is forwarded, the devic= e needs to know where the next application is deployed. That's why task in= dication is needed. An edge computing device could be fully loaded if many applications are dep= loyed on it. Then some of the applications need to be offloaded to higher l= ayer devices, e.g. edge could or the cloud. Applications can be offloaded f= rom the cloud to the edge as well. In this draft, we discussed how to use service function chaining to deal wi= th the aforementioned problems. Different paths of the same chain can be b= uilt and configured to the devices. By choosing a path at the classifier, u= sing the path ID can deliver the packet to the right device holding the nex= t application. When an applcation on the current path is overloded, the ne= xt packet flow will be guided to another path on which the same application= is deployed somewhere else. Please check the draft for more information. Looking forward to your comments. Best regards, Remy --_000_BB09947B5326FE42BA3918FA28765C2EEB04FEDGGEMM506MBXchina_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear all,

 

Please find our new draft on edge computing at &n= bsp;https://datatracker.ietf.org/doc/draft-liu-iiot-sfc-= edge-computing-applicability/

 

In the last edge computing side meeting, task ind= ication and offloading are identified as two of the gaps.

 

In edge computing, except the applications have t= o be deployed at the edge gateway due to timely response requirement, or th= e on cloud due to high computional complexity, the other applcations can be= deployed at the edge gateway, edge cloud or public cloud. Thus when the data is forwarded, the device needs t= o know where the next application is deployed.  That’s why task = indication is needed.

 

An edge computing device could be fully loaded if= many applications are deployed on it. Then some of the applications need t= o be offloaded to higher layer devices, e.g. edge could or the cloud. Appli= cations can be offloaded from the cloud to the edge as well.

 

In this draft, we discussed how to use service fu= nction chaining to deal with the aforementioned problems.  Different p= aths of the same chain can be built and configured to the devices. By choos= ing a path at the classifier, using the path ID can deliver the packet to the right device holding the next applic= ation.  When an applcation on the current path is overloded, the next = packet flow will be guided to another path on which the same application is= deployed somewhere else.

 

Please check the draft for more information.

 

Looking forward to your comments.

 

Best regards,

Remy

 

--_000_BB09947B5326FE42BA3918FA28765C2EEB04FEDGGEMM506MBXchina_--