[Idr] Need 10 minute slot to discuss AppMetaData Path Attribute for 5G Edge Computing (was RE: Call for IETF 109 IDR agenda items

[Linda Dunbar <[e-mail]>]

IDR Chairs and Jimmy,

Can you give us a 10 minute slot to present this new draft:
https://datatracker.ietf.org/doc/draft-dunbar-idr-5g-edge-compute-app-meta-data/

This draft describes a new BGP Network Layer Reachability Information (BGP NLRI) Path Attribute, AppMetaData, that can distribute the 5G Edge Computing App running status and environment, so that other routers in the 5G Local Data Network can make intelligent decision on optimized forwarding of flows from UEs. The goal is to improve latency and performance for 5G Edge Computing services.
The extension enables a feature, called soft anchoring, which makes one Edge Computing Server at one specific location to be more preferred than others for the same application to receive packets from a specific source (UE).

A little bit background:
In 5G Edge Computing environment, one Application can have multiple Application Servers hosted in different Edge Computing data centers that are close in proximity. Those Edge Computing (mini) data centers are usually very close to, or co-located with, 5G base stations, with the goal to minimize latency and optimize the user experience.

Increasingly, Anycast is used by various application providers and CDNs because it is possible to dynamically load balance across multiple locations of the same address based on network conditions.  Application Server location selection using Anycast address leverages the proximity information present in the network (routing) layer and eliminates the single point of failure and bottleneck at the DNS resolvers and application layer load balancers. Another benefit of using ANYCAST address is removing the dependency on UEs that use their cached IP addresses instead of querying DNS when they move to a new location.

But selection of an ANYCAST location purely based on the network condition can encounter issue of the location selected by IP routing information being overutilized while there are available underutilized locations close by.
That is why we propose this AppMetaData Path Attribute for the (egress) router that have the App Servers attached to distribute the running status and environment of the App Server .

Thank you very much
Linda Dunbar


From: Idr <[e-mail]> On Behalf Of Dongjie (Jimmy)
Sent: Wednesday, October 21, 2020 8:54 PM
To: [e-mail]
Cc: idr-chairs <[e-mail]>
Subject: [Idr] Call for IETF 109 IDR agenda items

Dear all,

The draft agenda of IETF 109 is available at https://datatracker.ietf.org/meeting/109/agenda.html<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2F109%2Fagenda.html&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C883d2b5cac674529526408d8762d6f6b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637389284825152060%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=7ohOrT73nfTxU4LOo4t6tNXgvSehY49sm0ZUcelTt1E%3D&reserved=0>. IDR has 2 sessions this time:

Session 1: Monday 14:30-15:30 (UTC+7)
Session 2: Friday 16:00-18:00 (UTC +7)

Please start to send any IDR agenda item request to me and CC the chairs. Please include the name of the draft, name of the presenter, and the estimate time you'll need (including Q/A). You may also indicate your preferred session.

If you plan to make a presentation, please keep in mind the IDR tradition, "no Internet Draft - no time slot". You should also plan to send your slides to me and CC the chairs no later than 24 hours prior to the IDR meeting, though earlier is better. Please number your slides for the benefit of remote attendees. By default your slides will be converted to PDF and presented from the PDF. If you do need to use any fancy builds or transitions, please make sure to arrange this with us in advance to avoid any surprise. Thanks.

And potential presenters, please take a look at the checklist for presenting at IDR:
https://trac.tools.ietf.org/wg/idr/trac/wiki/Checklist%20for%20presenting%20at%20an%20IDR%20meeting<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftrac.tools.ietf.org%2Fwg%2Fidr%2Ftrac%2Fwiki%2FChecklist%2520for%2520presenting%2520at%2520an%2520IDR%2520meeting&data=04%7C01%7Clinda.dunbar%40futurewei.com%7C883d2b5cac674529526408d8762d6f6b%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C1%7C637389284825162053%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=i3G7TCfAdWTefQLhDVBH3FsAZq5WmGs37l%2FXgLxn%2Bqw%3D&reserved=0>


Best regards,
Jie