IETF Logo Mail Archive

Re: [Idr] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)

"Chenxia (D)" <jescia.chenxia@huawei.com> Tue, 16 August 2022 08:24 UTC

Return-Path: <jescia.chenxia@huawei.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 5A24AC1522CF for <idr@ietfa.amsl.com>; Tue, 16 Aug 2022 01:24:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.208
X-Spam-Level:
X-Spam-Status: No, score=-4.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zl21IfdVAppc for <idr@ietfa.amsl.com>; Tue, 16 Aug 2022 01:24:06 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 676A7C1522C2 for <idr@ietf.org>; Tue, 16 Aug 2022 01:24:06 -0700 (PDT)
Received: from fraeml737-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4M6PHK6nRvz688wM for <idr@ietf.org>; Tue, 16 Aug 2022 16:21:01 +0800 (CST)
Received: from canpemm100003.china.huawei.com (7.192.104.85) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 16 Aug 2022 10:24:03 +0200
Received: from canpemm500001.china.huawei.com (7.192.104.163) by canpemm100003.china.huawei.com (7.192.104.85) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 16 Aug 2022 16:24:01 +0800
Received: from canpemm500001.china.huawei.com ([7.192.104.163]) by canpemm500001.china.huawei.com ([7.192.104.163]) with mapi id 15.01.2375.024; Tue, 16 Aug 2022 16:24:01 +0800
From: "Chenxia (D)" <jescia.chenxia@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)
Thread-Index: AdijNQ+IfMfPCoxlRY2mLEfIE5uYeQOERt1Q
Date: Tue, 16 Aug 2022 08:24:01 +0000
Message-ID: <0f4b461ecdf04540ad7d01335a3ae315@huawei.com>
References: <BYAPR08MB4872CFF0336A359D8D1210D0B3999@BYAPR08MB4872.namprd08.prod.outlook.com>
In-Reply-To: <BYAPR08MB4872CFF0336A359D8D1210D0B3999@BYAPR08MB4872.namprd08.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.244]
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/idr/XH6A7K3NCoHNyV4HUwu2K5AIE1g>
Subject: Re: [Idr] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 16 Aug 2022 08:24:10 -0000

Hi Sue,

I have read this draft and support its adoption. Please find my answers to the questions below and some comments further below.

Xia Chen

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Friday, July 29, 2022 6:23 PM
To: idr@ietf.org
Subject: [Idr] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)

This begins a 3 week WG Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt
https://datatracker.ietf.org/doc/draft-dunbar-idr-5g-edge-compute-app-meta-data/

This draft proposes a new SubTLV (AppMetaData) for the BGP Tunnel Encapsulation Attribute [RFC9012] that indicates the running status and environment of directly attached 5G Edge Computing (EC) instances.
 
The AppMetaData can be used by routers in the 5G Local Data Network to make path selection not only based on the routing distance but also the running environment of the destinations. The goal is to improve latency and performance for 5G EC services.

In your discussion of this adoption call, please consider these questions: 

1) The addition of this type of information to tunnels is useful for inter-domain routing within 5G networks? 
The computing load and running status information is useful for IDR within 5G EC scenario.  This can be used for public network or VPN
But it should allow a new Path Attribute to carry the load metrics for the specific prefix of EC instances, so that UPDATE can reflect load information for the prefixes that don't need tunnels or the prefixes using default configured tunnel.

2) What type of additional load this data to Basic Tunnel encapsulation [RFC9012]?  
For example is the load placed by this draft equal or Less than the SR routing additions from such as draft-ietf-idr-segment-routing-te-policy? 

The additional load of new path attribute is reasonable. Only some prefixes need add the new path attribute when used in specific scenario.

3) Will the addition of this information aid Routing in 5G networks? 

Yes. Especially in EC scenario. Ant not only mobile networks but also fixed networks.

Cheers, Sue Hares 

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr

v2.23.0 | Report a Bug | By Email