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

Aijun Wang <> Mon, 08 August 2022 09:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D0CBAC13CCCA for <>; Mon, 8 Aug 2022 02:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2awc4eUop1hx for <>; Mon, 8 Aug 2022 02:29:19 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EFE9FC14F72A for <>; Mon, 8 Aug 2022 02:29:17 -0700 (PDT)
Received: from DESKTOP2IOH5QC (unknown []) by (Hmail) with ESMTPA id 64D288000BB; Mon, 8 Aug 2022 17:29:15 +0800 (CST)
From: "Aijun Wang" <>
To: "'Susan Hares'" <>, <>
References: <>
In-Reply-To: <>
Date: Mon, 8 Aug 2022 17:29:11 +0800
Message-ID: <005101d8ab09$53f59b50$fbe0d1f0$>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQIn1VA1LnVOYQjUnMdo18/zmCHJaK0GZU0g
Content-Language: zh-cn
X-HM-Tid: 0a827cc97bddb03akuuu64d288000bb
Archived-At: <>
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-Mailman-Version: 2.1.39
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Aug 2022 09:29:21 -0000

Hi, Susan:

I support its adoption.
Knowing the status of application servers in 5G Edge environment can
certainly aid the selection of optimized servers at the ingress router.

One point to the authors: I agree with the comments from Huaimo, and think
put all these meta data  under one position, for example, Tunnel Encap
Attributes, will be more appropriate.
The reason that put "Capacity Site Index" under Extended Community seems not
too sound. 

And, I want to know, what is the next step for the related usage document?
sage-00. Is it just for references? 
Is it necessary to extract some contents into this adopted documents? For
example, the usage of these app meta data?

Best Regards

Aijun Wang
China Telecom

-----Original Message-----
From: <> On Behalf Of Susan Hares
Sent: Friday, July 29, 2022 6:23 PM
Subject: [Idr] Adoption call for
draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to

This begins a 3 week WG Adoption call for

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? 

2) What type of additional load this data to Basic Tunnel encapsulation

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? 

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

Cheers, Sue Hares 

Idr mailing list