Agenda for the ALTO 117 WG Session (Hybrid)
https://datatracker.ietf.org/doc/agenda-117-alto/
Session:
Thursday, July 27, 2023
WG Chairs:
Mohamed Boucadair (mohamed.boucadair@orange.com)
Qin Wu (bill.wu@huawei.com)
Available During Session:
ICS: https://datatracker.ietf.org/meeting/117/sessions/alto.ics
MeetEcho: https://meetings.conf.meetecho.com/ietf117/?group=alto
Audio Only: http://mp3.conf.meetecho.com/ietf117/alto/1.m3u
Jabber: xmpp:alto@jabber.ietf.org?join
Available During and After Session:
CodiMD: https://codimd.ietf.org/notes-ietf-117-alto
Slides: https://datatracker.ietf.org/meeting/117/session/alto
Drafts (PDF):
https://datatracker.ietf.org/meeting/117/agenda/alto-drafts.pdf
Drafts (TGZ):
https://datatracker.ietf.org/meeting/117/agenda/alto-drafts.tgz
Introduction & WG Status (Chairs) 5 min
Pending Issues from the AD review (Transport) 5 min
CATS/ALTO Work on Metrics Definition (CATS Chairs) 5 min
Future of the WG (45 min)
Context (Chairs) 5 min
A Word from the AD 5 min
Recharter Discussion: ALTO Deployment Catalyst Charter item Proposals
ALTO southbound implementation based on IETF mechanisms (Richard) 5 min
BGP Community for Network Map (Luis/Danny) 5 min
Compute Information Retrieval and Exposure (Qi/Jordi) 5 min
Discussion & Next Steps 20 min
Wrap-up
[MD] There is a lot of HTTP based out there and not much best
practice. Opportunity for best practice
[RY] Dany and folks implementing it are on vacation
[MD] We can wait
Potential Joint Deployment ALTO and CATS so that the host is making the
choice about set of servers to target, pushing that out to the edge and
normal CATS processing takes over.
Service based info is used by CATS and ALTO.
CATS interested in topology, capabilities and state. Also compute.
Easily combinable with traffic metrics.
From TE if metric is simple, then easy to proceed.
Quite overlap between CATS and ALTO.
Wouldn't it be nice if metrics could be common across.
Suggesting with the chairs to have a joint interim meeting.
Host is where the ALTO client lives. And end user device.
CATS is on its own, ALTO is own its own, both are happening.
We will come up with couple of dates to do interim to see how we can
mesh.
Good sustainable dedicated friendly group.
How can we enhance adoption.
Direction: recharter or declare success.
Assessment pretty accurate. I can see a gap in putting into an ALTO DB.
I don't think that's ALTO, I really don't think this is in the transport
area.
For aggregation thing, maybe a new WG.
Using IETF mechanisms.
ALTO components. Major missing piece is southbound.
Southbound compleixity in realizing base alto cost service.
Benocs solution, implemented in 15-20 networks.
Proposal: evaluate, guide and propose solutions for southbound.
Only IETF standard mechanism.
CERN, Benocs, Telefonica interested
Using BGP-LS implementation.
BGP communities quite extensively used by operators.
ALTO has the concept of PID, similar to BGP community.
To allow ALTO to process BGP community info.
provide network cost maps based on communities.
Towards facilitating the integration of ALTO in operational networks.
Gap analysis: CATS covers path selection. ALTO to focus on service
placement/selection.
Both are needed to ensure operators and application clients can optimize
the full service/application life cycle.
Prime applications will need this interface, including distributed AI
and XR workloads.
Proposal: to write an information draft focusing on
Discussion goes around whether there is a need to work on the southbound
interface.
AD says WG can stay open for the next months to finalize tasks, but
suggest no session in 118.