## Agenda for the ALTO 116 WG Session (Hybrid) {#agenda-for-the-alto-116-wg-session-hybrid} https://datatracker.ietf.org/doc/agenda-116-alto/ Session: Monday, March 3,2023 Session I (09:30-11:30 UTC,04:30-06:30 EST, 01:30-03:30 PDT,17:30-19:30 Beijing Time) WG Chairs: Mohamed Boucadair (mohamed.boucadair@orange.com) Qin Wu (bill.wu@huawei.com) Available During Session: ICS: https://datatracker.ietf.org/meeting/116/sessions/alto.ics MeetEcho: https://meetings.conf.meetecho.com/ietf116/?group=alto Audio Only: http://mp3.conf.meetecho.com/ietf116/alto/1.m3u Jabber: xmpp:alto@jabber.ietf.org?join Available During and After Session: CodiMD: https://codimd.ietf.org/notes-ietf-116-alto Slides: https://datatracker.ietf.org/meeting/116/session/alto Drafts (PDF): https://datatracker.ietf.org/meeting/116/agenda/alto-drafts.pdf Drafts (TGZ): https://datatracker.ietf.org/meeting/116/agenda/alto-drafts.tgz * * * Deployment Experience Update Cascading ALTO Deployment Discussion Leader: Ingmar Poese ALTO integration with CERN/LHCONE/FTS/RUICO on Multi-domain Setting https://wiki.ietf.org/en/group/ALTO/deployment Discussion Leader: Richard Yang, with Jordi Ros Giralt/Mario Lassnig/Mihai Patrascoiu ALTO integration for Telefonica CDN https://wiki.ietf.org/en/group/ALTO/deployment Discussion Leader: Luis M. Contreras Non-Chartered items: ALTO Multi-domain Service https://www.ietf.org/archive/id/draft-yang-alto-multi-domain-01.txt https://www.ietf.org/archive/id/draft-lachos-alto-multi-domain-use-cases-02.txt Discussion Leader: Jordi Ros Giralt, with Richard Yang/Ingmar Poese/Danny Alex Lachos Perez/Mario Lassnig Network and Computing Exposure https://www.ietf.org/archive/id/draft-contreras-alto-service-edge-07.txt https://www.ietf.org/archive/id/draft-lcsr-alto-service-functions https://www.ietf.org/archive/id/draft-yao-alto-core-level-load-balancing-00.txt Discussion Leader: Luis M. Contreras/Jordi Ros Giralt Any Other Business ## Introduction (Chairs): Session intro & WG Status {#introduction-chairs-session-intro--wg-status} Current progress: * Published 4 RFCs * Four hackathons, 1 interim meetings (more to come) * Six ALTO deployments: https://wiki.ietf.org/en/group/ALTO/deployment * Open source project OpenALTO * Socializing: OPSAWG, MOPS, TVR... IP Journal article * Proposed directions ## Benocs Cascading ALTO Deployment (Ingmar Poese) {#benocs-cascading-alto-deployment-ingmar-poese} * ALTO deployment by Benocs starts in 2013. * First production implementation of ALTO in 2015 * Updates since then through 2020+ * Have a customer base * Deployments: 20+ * Total traffic for ALTO: 60TBit / ~45TBit/s * Traffic steered by Benocs: 35Tbig * Steered through ALTO: 2 trails running ALTO chicken egg problem: * Networks need enough CDNs to understand ALTO * CDN need enough network to offer ALTO So each CDN implements its own interfaces and networks run multiple interfaces * Architecture: collect IGP, BGP, augment with SNMP, etc. Convert into internal standard format. * Challenge: Building ALTO map based depends on the correct ingress point * Challenge: Cascading Path Optimization * ALTO to the rescue: multi-domain case * Interfaces are used to map hypergiants. ## ALTO Deployment CERN (Richard Yang) {#alto-deployment-cern-richard-yang} * CERN manages one of the largest science networks (LHCOPN, LHCONE) in charge of distributing the massive data sets from CERN to 40 countries globally across 170 data centers * 457 Petabyes of data in 2022 * Software stack: traditional routing, TCP/IP overlayed with data-intense workloads * Workload scheduler: Rucio / FTS * On top of basic congestion control model (TCP), providing basic fairness. On top, scheduler overlays application level control of the workload. * ALTO/FTS visibility => control * Plugins for a variety of southbound monitoring tools (e.g., glass) * Query language * RFC 9240, RFC 7285 ## ALTO Telefonica CDN Deployment (Luis Contreras) {#alto-telefonica-cdn-deployment-luis-contreras} * Recap slide from 114, 115 * Pilot Q4 2022 - 1663 subnets retrieved * Issues: * BGP-LS bug, needs OS update * Flapping between ALTO server and RR * TCPZeroWndow * Overflow * Under analysis how often we need to retreive the entire topology * Next steps: * Understand how often * Information analysis * Debuging * Producttification of ALTO * Automation * Wiki * Gaps * New Pilots (e.g, Brazil) ## ALTO Multi-domain Service (Jordi Ros-Giralt) {#alto-multi-domain-service-jordi-ros-giralt} * Challenges on buiding the paths and associated costs in multi-domain. * Partial information, no global view. * Leverage ALTO to propagate information for acquiring global knowledge. * Propagation of the information (1) Horizontally (all domains have full knowledge) or (2) Vertically (hierarchical approach). * Incremental deployment: provide guidance * We have quite a number of I-Ds on this topic * Next steps to discuss during interim meetings ## ALTO for Computing Exposure (Luis Contreras and Jordi Ros-Giralt) {#alto-for-computing-exposure-luis-contreras-and-jordi-ros-giralt} * Collection of I-Ds: alto-ietf-nef, alto-service-edge, alto-service-functions * Heterogeneous data centers * Identify suitable DC by leveraging ALTO with compute extensions * Updates in version 06: use cases, and Jordi (Qualcomm) joined * Use case for split computing * ALTO (and communicaiton/compute state exposure) is key to support new coming service placement and selection problems * service functions: use ALTO protocol (+ext) to assist on the identification of “best” chains * Not all needs to expose compute are related to traffic steering, ALTO can address this gap too