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)

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Wed, 17 August 2022 11:55 UTC

Return-Path: <pengshuping@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 4090CC14792A for <idr@ietfa.amsl.com>; Wed, 17 Aug 2022 04:55:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 zPhxnk52eNJI for <idr@ietfa.amsl.com>; Wed, 17 Aug 2022 04:55:33 -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 B280CC1527AD for <idr@ietf.org>; Wed, 17 Aug 2022 04:55:32 -0700 (PDT)
Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4M75wm4jgmz67hYm for <idr@ietf.org>; Wed, 17 Aug 2022 19:52:24 +0800 (CST)
Received: from canpemm500006.china.huawei.com (7.192.105.130) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2375.24; Wed, 17 Aug 2022 13:55:28 +0200
Received: from canpemm500008.china.huawei.com (7.192.105.151) by canpemm500006.china.huawei.com (7.192.105.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 17 Aug 2022 19:55:27 +0800
Received: from canpemm500008.china.huawei.com ([7.192.105.151]) by canpemm500008.china.huawei.com ([7.192.105.151]) with mapi id 15.01.2375.024; Wed, 17 Aug 2022 19:55:27 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@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+IfMfPCoxlRY2mLEfIE5uYeQO+ezaA
Date: Wed, 17 Aug 2022 11:55:27 +0000
Message-ID: <906ac0165aab481dacc3837342164ca2@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.146.62.97]
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/ETAtxixemRKRip9-Ot9qY3uGiZ4>
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: Wed, 17 Aug 2022 11:55:35 -0000

Hi Sue, all, 

I have read this draft and support its WG adoption. Please also find my answers to these questions below. 

> 1) The addition of this type of information to tunnels is useful for
> inter-domain routing within 5G networks?
> 
Yes, it is useful. 

> 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 is low and acceptable. 

> 3) Will the addition of this information aid Routing in 5G networks?
>
Yes, it will. 

Thank you!

Best Regards, 
Shuping



> -----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-me
> ta-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?
> 
> 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?
> 
> 3) Will the addition of this information aid Routing in 5G 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