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

[Linda Dunbar <[e-mail]>]

Jeffrey, 

Thanks for including CAN mailing list to the discussion. 

draft-dunbar-idr-5g-edge-compute-app-meta-data is only for requesting a new subType under Opaque Extended Community  for egress routers to notify site capacity index to the ingress nodes for mass number of routes changes caused by a degradation of a site/pot, also another new subType for a subTLV under Tunnel-Encap Path attribute to indicate the load capacity for the associated client routes. 

The CAN (Computing Aware Networking) includes the overarching architecture, functional modules (e.g. DYNCAST), computing resource characterization, profiles, representations, routing control plane protocols and potentially data plane extensions. 

The new subTypes requested by draft-dunbar-idr-5g-edge-compute-app-meta-data can be used by the protocol extension needed by CAN if BGP is used.  Those subTypes values assigned by IANA doesn't change regardless of the CAN's scope and status.  

Linda

-----Original Message-----
From: Idr <[e-mail]> On Behalf Of Jeffrey (Zhaohui) Zhang
Sent: Thursday, August 4, 2022 12:50 PM
To: Susan Hares <[e-mail]>; [e-mail]; [e-mail]
Subject: Re: [Idr] Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt (7/29/2022 to 8/12/2022)

Hi,

There was a CAN BOF in IETF113:

https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fbofreq-liu-computing-aware-networking-can%2F&amp;data=05%7C01%7Clinda.dunbar%40futurewei.com%7C5644de2e08a146ad8cf908da7641db2b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637952322490239481%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=KjboTPCk2ejjnUy6IWHlCgJ9l3WG3n3K72KtuhJomUQ%3D&amp;reserved=0
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_0uanSBJz5c%26ab_channel%3DIETF-InternetEngineeringTaskForce&amp;data=05%7C01%7Clinda.dunbar%40futurewei.com%7C5644de2e08a146ad8cf908da7641db2b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637952322490239481%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=a%2Bp%2FSFDAMZ3dYdZN5yodfQClWccin9HCshgCUsP9Gws%3D&amp;reserved=0

There have been extensive and on-going discussions on whether we should solve the problem in routing. There were two presentations on the follow-up in IETF114 as well. My understandings are:

- It is not decided yet if/where there will be a CAN WG and whether we should standardize a routing-based solution
- This draft is a routing-based solution for the use case

Based on above, I do not think we should rush to adopt it - it should be deferred to until CAN is decided.

I am copying the CAN mailing list ([e-mail]).

Thanks.
Jeffrey


Juniper Business Use Only

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

[External Email. Be cautious of content]


This begins a 3 week WG Adoption call for draft-dunbar-idr-5g-edge-compute-app-meta-data-09.txt
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-dunbar-idr-5g-edge-compute-app-meta-data%2F__%3B!!NEt6yMaO-gk!FUoaLlWqdv8TPFCwzEtE2-8x6PRa-AsjklFfcIuNSadWVhqdf7uktC31Ynli5-IYysRSNv_WVVS6-sg%24&amp;data=05%7C01%7Clinda.dunbar%40futurewei.com%7C5644de2e08a146ad8cf908da7641db2b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637952322490239481%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=%2BWrnlaBrIQSq4XoRlrDJdqhIqk%2FaV8sKPKVtYiFlzNc%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://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr__%3B!!NEt6yMaO-gk!FUoaLlWqdv8TPFCwzEtE2-8x6PRa-AsjklFfcIuNSadWVhqdf7uktC31Ynli5-IYysRSNv_W1s6-HKo%24&amp;data=05%7C01%7Clinda.dunbar%40futurewei.com%7C5644de2e08a146ad8cf908da7641db2b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637952322490239481%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=sQwLa67xcmL6jFabmxfYwLUUJnWSR9vdCv8ZmPJvkhg%3D&amp;reserved=0

_______________________________________________
Idr mailing list
[e-mail]
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fidr&amp;data=05%7C01%7Clinda.dunbar%40futurewei.com%7C5644de2e08a146ad8cf908da7641db2b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637952322490395718%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=AZR67tMbcBTmE1dpefkOIYX1tgVxVDaLHuwCEeIKwFQ%3D&amp;reserved=0