Hi WG, We posted a first version of a draft to discuss the issues and potential solutions of ALTO in multi-domain settings. Any comments and suggestions will be greatly appreciated. We will follow up with more updates soon.
Thanks! Richard ---------- Forwarded message --------- From: <[email protected]> Date: Mon, Mar 13, 2023 at 6:44 PM Subject: New Version Notification for draft-yang-alto-multi-domain-01.txt To: Y. Richard Yang <[email protected]>, Mario Lassnig <[email protected]> A new version of I-D, draft-yang-alto-multi-domain-01.txt has been successfully submitted by Y. Richard Yang and posted to the IETF repository. Name: draft-yang-alto-multi-domain Revision: 01 Title: ALTO Multi-Domain Services Document date: 2023-03-13 Group: Individual Submission Pages: 9 URL: https://www.ietf.org/archive/id/draft-yang-alto-multi-domain-01.txt Status: https://datatracker.ietf.org/doc/draft-yang-alto-multi-domain/ Html: https://www.ietf.org/archive/id/draft-yang-alto-multi-domain-01.html Htmlized: https://datatracker.ietf.org/doc/html/draft-yang-alto-multi-domain Diff: https://author-tools.ietf.org/iddiff?url2=draft-yang-alto-multi-domain-01 Abstract: Application-Layer Traffic Optimization (ALTO) provides means for network applications to obtain network information. In the definitions of ALTO services ([RFC7285] and existing extensions), there is no requirement on whether the source and the destination endpoints must belong to the same autonomous network, which is a single-domain setting, or they can belong to different autonomous networks, which is a multi-domain setting. This document explains problems of realizing ALTO in multi-domain settings and then presents 3 potential solutions to realize ALTO multi-domain services. The IETF Secretariat
_______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
