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

[Kausik Majumdar <[e-mail]>]

Hi Sue,
 
I support the IDR WG adoption on this important Draft.
 
The main crack of the Draft is the Egress Router shares the Application Meta Data metrics through BGP RR to the Ingress Routers (the Routers that are interested in selecting the proper Egress Routers GW for the associated DC based on the application Meta Data Matrices). The application servers hosted in the DC need to support the Anycast IP as a requirement based on this Draft.
 
We need to progress on this Draft, and in MS Azure, we will be looking forward to advancing this Draft to load share between the DCs from the Ingress Routers. It's a purely routing-based solution with some BGP dependency. Hence, adopting this Draft in the IDR WG would be good.
 
Once the CAN BOF is settled down, we can present over there to capture the CAN requirements. But I don't think we should create a dependency on this proposed routing-based proposal with the CAN BOF. That can be progressed independently irrespective of the adoption in IDR WG.
 
On the specific questions below -
 
1) The addition of this type of information to tunnels is useful for inter-domain routing within 5G networks?
Yes.
 
2) What type of additional load this data to Basic Tunnel encapsulation [RFC9012]?  
I don't see it poses any additional load to the Basic Tunnel encapsulation that is defined in RFC 9012. Any tunneling mechanism to the Egress Router can be done here to forward the packet to the Anycast IP Application Servers. This could be the existing VXLAN Tunnel, SR-TE Tunnel, RSVP-TE Tunnels, etc. We are not proposing any new Tunnels as part of this Draft but instead would be using the existing Tunneling mechanism to the Egress Router GW attached to the DCs.
 
3) Will the addition of this information aid Routing in 5G networks?
Yes, it will be helpful for the Ingress path selections to the UEs that are part of the 5G networks.
 
Regards,
Kausik

-----Original Message-----
From: Idr <[e-mail]> On Behalf Of Susan Hares
Sent: Friday, July 29, 2022 3:23 AM
To: [e-mail]
Subject: [EXTERNAL] [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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-dunbar-idr-5g-edge-compute-app-meta-data%2F&amp;data=05%7C01%7Ckmajumdar%40microsoft.com%7C5fd5400dc5ee44105cc508da714c6c16%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637946870305337834%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=vb5mojUhc3z1CL0K4UcsOWXZuLXZ0oOnj6sl9MV4vjA%3D&amp;reserved=0

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
[e-mail]
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr&amp;data=05%7C01%7Ckmajumdar%40microsoft.com%7C5fd5400dc5ee44105cc508da714c6c16%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637946870305337834%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=42MJdU7YS1UFROl7FppQNvlwhGkP0r9ZrqArhm169sw%3D&amp;reserved=0