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

I support WG adoption as co-author.

I believe the AppMetadata for path selection can be very useful for
optimized inter domain routing within 5G networks.

The AppMetaData SubTLV is also applicable as Linda mentioned to the over
arching CAN BOF  DynCast Architecture.

https://datatracker.ietf.org/doc/bofreq-liu-computing-aware-networking-can/

Regards

Gyan

On Fri, Jul 29, 2022 at 6:23 AM Susan Hares <shares@ndzh.com> wrote:

> 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?
>
> 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
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*

*M 301 502-1347*