[Idr] 5G Edge -Computing Solution drafts can be used for Dyncast (dynamic anycast) use cases

Linda Dunbar <linda.dunbar@futurewei.com> Wed, 04 November 2020 17:19 UTC

Return-Path: <linda.dunbar@futurewei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F32963A0D99; Wed, 4 Nov 2020 09:19:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.456
X-Spam-Level:
X-Spam-Status: No, score=-0.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, LH_URI_DOM_IN_PATH=1.533, RCVD_IN_MSPIKE_H2=-0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.com
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 eIWrFBjOBSIm; Wed, 4 Nov 2020 09:19:04 -0800 (PST)
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (mail-eopbgr680118.outbound.protection.outlook.com [40.107.68.118]) (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 AF02B3A0D29; Wed, 4 Nov 2020 09:19:03 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=cy7+yVQwB6OgzqMtm4If9DiaqDLA36I7Ha5tO4nSHqV8ICuSbAwFIkWGKO45eSw84rAnLXOAjzpiv7f6mrpWLs1Yztm3qBevczWFyyFDQtGi7PrFdZJj07xLMoC/8pRD5FrNhZIvNq1qKN+aSTJdf54oM1JA/uE89zFvXkl3paRt+nNz5NdL4ljb17N4Cb8htJaSuWEsBtmg+2jrt6kKzzglUFI8lq0piysSDLEe/jSHhXbKcVcC1mlJ5XEFuXu/Wp84uM9CcjKW3d3W4ep/M8EjHQsXCfFsfT1TKl3gUR4iQZGYGfQ3XVJtUi7/r9IG1ME7LvsFFtFBylqG9Zm8jg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lGnCdRWHQAr1yQO0g1ZxHqFnPldbduO+lSdHpJ83sIM=; b=BtsNoT4UYHxl8HK+RIE9ssasXSg9OyENslEYDhNFJn7ddt8K871fat3BX8LmJNoEBi8IR3k4lziZUTcOICDAR1SwRQ9zIlv64htzqG/szK2vGzUuGb2yOY4P3JLXO1e5JWSQTMsvhYP0yjmc/46nBlWWTEoJlJJXX9nTh6HjQTkFHK4qUmX4d3h5vRg2h/in02sSy7bg0ZC4eDcSQza2zPFdlpim5HCQZoWqIUK+k9rlSCCG6MTjgbUpIq+IYh8txInEIJhv0MX77/PKc6kw8vyoispozlrRYTT3zbf3gSeHytT5VDN+Uzn4du5C1gqok+HD4lfzi4WfdRVodR+t1w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=lGnCdRWHQAr1yQO0g1ZxHqFnPldbduO+lSdHpJ83sIM=; b=OPSHqWcmmhxsCHCD7eogtoNukWWBvkEtBi2SznctQvLvMK0xUNegOy1oNHHUfAECyPmjby+nSO5Je1jxrEeJ7q9eoBnO3tR2cV4DD/npQC+m8Gc3B1J5DcnDZQvOEQKDQb9TZCLEwXNfUKAdP6nzxseMRWe51s0rzqXnwnpPT8I=
Received: from SN6PR13MB2334.namprd13.prod.outlook.com (2603:10b6:805:55::16) by SN6PR13MB2496.namprd13.prod.outlook.com (2603:10b6:805:54::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3541.10; Wed, 4 Nov 2020 17:19:01 +0000
Received: from SN6PR13MB2334.namprd13.prod.outlook.com ([fe80::8c05:b4f5:cc16:eeb]) by SN6PR13MB2334.namprd13.prod.outlook.com ([fe80::8c05:b4f5:cc16:eeb%7]) with mapi id 15.20.3541.017; Wed, 4 Nov 2020 17:19:01 +0000
From: Linda Dunbar <linda.dunbar@futurewei.com>
To: "rtgwg@ietf.org" <rtgwg@ietf.org>, Liyizhou <liyizhou@huawei.com>, 'Peng Liu' <liupengyjy@chinamobile.com>, =?iso-2022-jp?B?TGlhbmcgR2VuZ3wbJEJmVk48GyhC?= <gengliang@chinamobile.com>
CC: 6man WG <ipv6@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "idr@ietf.org" <idr@ietf.org>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: 5G Edge -Computing Solution drafts can be used for Dyncast (dynamic anycast) use cases
Thread-Index: AdayzpEaHu3QsaBqSGaG4F0WR2lrxQ==
Date: Wed, 4 Nov 2020 17:19:00 +0000
Message-ID: <SN6PR13MB23340B6747554039B178957D85EF0@SN6PR13MB2334.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=futurewei.com;
x-originating-ip: [2603:8081:1700:ab:51f3:c599:1978:f74d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 127d41da-cc9c-48da-1655-08d880e5b8eb
x-ms-traffictypediagnostic: SN6PR13MB2496:
x-microsoft-antispam-prvs: <SN6PR13MB2496EB6AEC04478A614E7F3D85EF0@SN6PR13MB2496.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: vO2srVcyDrJU+qm9IvrNlDGIymemeaN4vph+g0vGKtBZK8pUKHH28zAt62CTziJ1v/Qnv12cdSzBJuz5274j32VEKBmPS3fOmtpmv6kWkJyK3/Cy/y556k36tZrrVDmgbNOmljz4m0EZVo21uy0SKQnAZc0pV7nYaldBKRm8i6uv0kQwHNM4QKkta+IB566jWscLtoHGQHV0ygYtKJzTfU4Ga2zsR01WgeXoZJr4E6fe46oWSeLFSwqw3hBgEy4PvZZL2gpug7UWzgcbPWOkDRkRs/99ecFAC8D06NscjMQao4jS50iT3qnNM5CZECz61drjWXFe2aSIjb0DgXtAB/qJt8nhzR+/5KkmXWkDlsed/np4qB8MRxsNLdTBi+YCK35idumVrgjd/M2IO+/4PA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:SN6PR13MB2334.namprd13.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39840400004)(396003)(376002)(366004)(346002)(136003)(316002)(7696005)(54906003)(110136005)(186003)(86362001)(6506007)(53546011)(966005)(33656002)(8676002)(44832011)(478600001)(8936002)(66446008)(71200400001)(66946007)(76116006)(55016002)(4326008)(64756008)(83380400001)(166002)(66574015)(66476007)(66556008)(5660300002)(9686003)(2906002)(52536014); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: AO5ONy708HIZXQfGBEXG8cJv4C3slGX0bzDX9QBvluC1pmb6yiHo+HQQDQqqAgSjgw8hn3gzs1mYPsYt68FA9tsH6EWFTbmddKv2TXgw91wc40g0E+SkEla9a3UwoG2Z4sH4roB8M4etG15gu4JEh38WCiMLU8RuyU+v0XEaC8ruIjMRLyKxbcdQzMfT9u5voAIZkmYiN8/uHL8vh90i/4hLn4wpRoT5/Zxh3a0Ww/UPg7+9T0fURyCjDwUQKUAib7QyWqK1iVSFBylS+jqoDBxyxQN+mjPpYSHO5+AWZyeWIp5bdhYiojCrmZUw6IH1V1CphcizBgPFLXKknIAY/GTf/1xkLS0+Pg/UU9G+xSGd8XyyKzoGaxD0Am5YUSY2hmi1UXPASNsuIYiXs9/TXl6lGKAWsQcanAvbYG0tcTfB3pxO3q23zAjfNtAayCaYaV4RlNdf+InxN7EY4FC8sVjJFfqm0DYGVwocicQ2s6Ej+MGsQMhX8Ez8O+zJasF/W10Z3/CGrk3RsAsN3mNCO8sMv/9/y+oa6HLi5FoB8nV53AFz9RwjRSv/pzFd0gggvghzFkbApTuDOZK4hbq8fIGPelpFb1YEhXcdkeIzvjRtZzJJnIakKJ7ffJOMjO7FHwFljxBiEau4j9Nnkj3gt9Z1nY5xL3sO1RuH7mohNETfRyN2aA4O3tZwpwPjNpZG1B+NCp+/htohg46IQ1pCBA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_SN6PR13MB23340B6747554039B178957D85EF0SN6PR13MB2334namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: SN6PR13MB2334.namprd13.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 127d41da-cc9c-48da-1655-08d880e5b8eb
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Nov 2020 17:19:00.9286 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: oUkwk05dJZoVmfLrttaR5mb3Yy5BU8q2kkdzomGWT6qnbU3iht7A6p+Dv7Qrh7aQbBoReWh6vv5MkFLzhn1BSQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR13MB2496
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/y2YSn-J6hWyPDPFp2aZf6A4NwL0>
Subject: [Idr] 5G Edge -Computing Solution drafts can be used for Dyncast (dynamic anycast) use cases
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2020 17:19:06 -0000

Yi Zhou, Liang, Peng, and Peter,

We have 4 IETF drafts describing the different aspect of the solutions to 5G Edge computing, which can cover your use cases and requirement described in draft-geng-rtgwg-cfn-dyncast-ps-usecase:

Through working on the 3GPP Release 17’s 5G Edge Computing project (3GPP TR23.748), we noticed that IP Layer can do more to optimize the 5G Edge computing services.

https://datatracker.ietf.org/doc/draft-dunbar-ippm-5g-edge-compute-ip-layer-metrics/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecure-web.cisco.com%2F1yyVDIoM4pRjqoaLcFtGBohA3Our0GjTsZTI_OhhRqrwPug8uB8BZCGk2WVCYZmJMutbzptopfG2ACz4AxfZxeUgnDWbBu1hcHyGnNbsDXzkStp9bntK0rpjjQPBgg-1jY8eRWaAcB_V85O45nB_MzOBkHjs9r0q1sGjDHKPhx7WjEaZgiAzZ4IsIMfmKhXFfCy_LUF9yMT24QsWdp66L9H5a1h0hA_940C_gOSIQDClYCc_3NcAcy2w665SAxX4zkbf9KrUNoa2w1tIurssNadIg0Miqo-Q9jwqwCGrZhRa3Zf94d0HVx-aI4KJrBQi3%2Fhttps%253A%252F%252Fdatatracker.ietf.org%252Fdoc%252Fdraft-dunbar-ippm-5g-edge-compute-ip-layer-metrics%252F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7Ce5a45f19804e4ec83d4508d87bea9dc6%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637395594903951448%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=1oMRUMShQ8Q8fA9JDhv7pyDVLRPpKamyqLvNHMb51qU%3D&reserved=0> describes the IP Layer metrics and methods to measure the Edge Computing Servers running status and environment for IP networks to select the optimal Edge Computing server location in 5G Edge Computing (EC) environment. This document also describes the method of incorporating those measurements with IP routing cost to come up with a more optimal criteria in selecting ANYCAST locations.

https://datatracker.ietf.org/doc/draft-dunbar-6man-5g-edge-compute-sticky-service/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecure-web.cisco.com%2F10q2K1AolUwnJQxE-1zdp20SZ9dJ4nGbrfheOMCk6FhMP7cll-lnH4Ele1vAAkXjvGYaXHnAl_WGczRan0zDSIF25BUg7bs9aWtE1gnvQvPt8_qGMdw5gmM3jpAWOXC6_N_neane1LGU-tFdSie6E94aD3LmVxBQnkkB_qnp3glPLwHgMYiU3hGmAJ_yuBK1a2SBOFdr3VmeUxXESfiXy-k0CflGKYdeAnYHNoIGMvbqPWVpWhjEVqqxUpLISwkvVznxIeTcYl6IGePA_y9uGFwvnl_jqU3tClFSPvy1DDEp12JvdoAa6ygDA_rvVmbfW%2Fhttps%253A%252F%252Fdatatracker.ietf.org%252Fdoc%252Fdraft-dunbar-6man-5g-edge-compute-sticky-service%252F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7Ce5a45f19804e4ec83d4508d87bea9dc6%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637395594903961443%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=2cZoGaNIOEVm6twNUFp9aBP%2BYDbWnhEQrPYVVL8Alrg%3D&reserved=0> describes a solution of using IPv6 extension header to help Ingress router to stick traffic from a UE to the original App Server when the UE moves from one 5G Site to another.

https://datatracker.ietf.org/doc/draft-dunbar-idr-5g-edge-compute-app-meta-data/ describes a new BGP Network Layer Reachability Information (BGP NLRI) Path Attribute, AppMetaData, that can distribute the 5G Edge Computing App running status and environment, so that other routers in the 5G Local Data Network can make intelligent decision on optimized forwarding of flows from UEs. The goal is to improve latency and performance for 5G Edge Computing services. The extension enables a feature, called soft anchoring, which makes one Edge Computing Server at one specific location to be more preferred than others for the same application to receive packets from a specific source (UE).

https://datatracker.ietf.org/doc/draft-dunbar-lsr-5g-edge-compute-ospf-ext/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecure-web.cisco.com%2F1pN4xFsbZmNhUqdhLGnTREMAj8uivXtc4wzAe5JqGqd4rZrJsKGRniQQp0KpmomwEWdnRGFimTXd3kCsWrCfJZK1_IK7-mzNZpLXCnmLbwhM011N3KS_V9ZTbJBsQCpIAz2Se2NJ7c77M8n1w1vTCMA3Mmv9L5yO4SlFI32zj70F_87C-scozGGga61PK-wDmL2JV_2BVvpfnK0YA0ez8WpbnSvQZQsks3bCUl7SQxG2IcuZI4PxNLhA2Y_22SSoaankWjg0sU58se1h4tDt7SrAao_ZcFqSTge-iZYmOyFN996wqXhPh5ZLzGa52Gh2j%2Fhttps%253A%252F%252Fdatatracker.ietf.org%252Fdoc%252Fdraft-dunbar-lsr-5g-edge-compute-ospf-ext%252F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7Ce5a45f19804e4ec83d4508d87bea9dc6%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637395594903961443%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Qb1rHSngDnQYOSDfVH5xyCRnZ9U2WoQ3knWGrUDNcm8%3D&reserved=0> describe OSPF extension for the Routers that collect the IP Layer Metrics to propagate to all other routers.

Please let us know if the proposed solutions can solve your use cases.

Thank you
Linda Dunbar



From: rtgwg <rtgwg-bounces@ietf.org<mailto:rtgwg-bounces@ietf.org>> On Behalf Of Liyizhou
Sent: Monday, November 2, 2020 1:17 AM
To: rtgwg@ietf.org<mailto:rtgwg@ietf.org>
Cc: Lifeng (Frank) <frank.lifeng@huawei.com<mailto:frank.lifeng@huawei.com>>; Peng Liu <liupengyjy@chinamobile.com<mailto:liupengyjy@chinamobile.com>>; gengliang@chinamobile.com<mailto:gengliang@chinamobile.com>
Subject: Dyncast (dynamic anycast)

Hi folks,

We submitted two drafts about dyncast (dynamic anycast).

draft-geng-rtgwg-cfn-dyncast-ps-usecase<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-geng-rtgwg-cfn-dyncast-ps-usecase%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C868abea8ec7b458427ad08d87f5aa4e4%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637399374577973883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=pkJ6LwZfAAZCHBJpDuRo1dZLFJM1pa2H83S5BZM75UQ%3D&reserved=0>
draft-li-rtgwg-cfn-dyncast-architecture<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-li-rtgwg-cfn-dyncast-architecture%2F&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C868abea8ec7b458427ad08d87f5aa4e4%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637399374577973883%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=%2FcVca03mICRivpgTP6%2FvUIqZnXs47iU%2BJ%2B6XZQUFgf4%3D&reserved=0>


Edge computing puts the potential requirements on better load balancing among the computing resources hosted on different edges. The number of such edges could be thousand or even more depending on where the computing resources are located.
The expected approach is to consider both network status and computing resources at the same time to determine the best place to forward a new computing demand to. Current solution usually uses DNS-like approach, select the service instance first (the lowest load or roughly the geographically closest instance) and then direct the demand to it regardless how good or bad the network path reaching it.

Anycast based service addressing methodology could be used here to reach the best edge in terms of both computation resource and network status at the same time. Flow affinity and computing aware routing needs to be enhanced in such an anycast architecture. It is called dynamic anycast in the drafts.

If you have any comments or suggestions, please drop us an email. Appreciated.

Regards,
Yizhou