rfc9439v6.txt | rfc9439.txt | |||
---|---|---|---|---|
skipping to change at line 14 ¶ | skipping to change at line 14 ¶ | |||
Category: Standards Track Y. Yang | Category: Standards Track Y. Yang | |||
ISSN: 2070-1721 Yale University | ISSN: 2070-1721 Yale University | |||
Y. Lee | Y. Lee | |||
Samsung | Samsung | |||
D. Dhody | D. Dhody | |||
Huawei | Huawei | |||
S. Randriamasy | S. Randriamasy | |||
Nokia Networks France | Nokia Networks France | |||
L. Contreras | L. Contreras | |||
Telefonica | Telefonica | |||
July 2023 | August 2023 | |||
Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics | Application-Layer Traffic Optimization (ALTO) Performance Cost Metrics | |||
Abstract | Abstract | |||
The cost metric is a basic concept in Application-Layer Traffic | The cost metric is a basic concept in Application-Layer Traffic | |||
Optimization (ALTO), and different applications may use different | Optimization (ALTO), and different applications may use different | |||
types of cost metrics. Since the ALTO base protocol (RFC 7285) | types of cost metrics. Since the ALTO base protocol (RFC 7285) | |||
defines only a single cost metric (namely, the generic "routingcost" | defines only a single cost metric (namely, the generic "routingcost" | |||
metric), if an application wants to issue a cost map or an endpoint | metric), if an application wants to issue a cost map or an endpoint | |||
skipping to change at line 1640 ¶ | skipping to change at line 1640 ¶ | |||
Events (SSE)", RFC 8895, DOI 10.17487/RFC8895, November | Events (SSE)", RFC 8895, DOI 10.17487/RFC8895, November | |||
2020, <https://www.rfc-editor.org/info/rfc8895>. | 2020, <https://www.rfc-editor.org/info/rfc8895>. | |||
[RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | [RFC9110] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke, | |||
Ed., "HTTP Semantics", STD 97, RFC 9110, | Ed., "HTTP Semantics", STD 97, RFC 9110, | |||
DOI 10.17487/RFC9110, June 2022, | DOI 10.17487/RFC9110, June 2022, | |||
<https://www.rfc-editor.org/info/rfc9110>. | <https://www.rfc-editor.org/info/rfc9110>. | |||
[RFC9438] Xu, L., Ha, S., Rhee, I., Goel, V., and L. Eggert, Ed., | [RFC9438] Xu, L., Ha, S., Rhee, I., Goel, V., and L. Eggert, Ed., | |||
"CUBIC for Fast and Long-Distance Networks", RFC 9438, | "CUBIC for Fast and Long-Distance Networks", RFC 9438, | |||
DOI 10.17487/RFC9438, July 2023, | DOI 10.17487/RFC9438, August 2023, | |||
<https://www.rfc-editor.org/info/rfc9438>. | <https://www.rfc-editor.org/info/rfc9438>. | |||
9.2. Informative References | 9.2. Informative References | |||
[FlowDirector] | [FlowDirector] | |||
Pujol, E., Poese, I., Zerwas, J., Smaragdakis, G., and A. | Pujol, E., Poese, I., Zerwas, J., Smaragdakis, G., and A. | |||
Feldmann, "Steering Hyper-Giants' Traffic at Scale", ACM | Feldmann, "Steering Hyper-Giants' Traffic at Scale", ACM | |||
CoNEXT '19, December 2019. | CoNEXT '19, December 2019. | |||
[G2] Ros-Giralt, J., Bohara, A., Yellamraju, S., Harper | [G2] Ros-Giralt, J., Bohara, A., Yellamraju, S., Harper | |||
skipping to change at line 1742 ¶ | skipping to change at line 1742 ¶ | |||
Y. Richard Yang | Y. Richard Yang | |||
Yale University | Yale University | |||
51 Prospect St. | 51 Prospect St. | |||
New Haven, CT 06520 | New Haven, CT 06520 | |||
United States of America | United States of America | |||
Email: yry@cs.yale.edu | Email: yry@cs.yale.edu | |||
Young Lee | Young Lee | |||
Samsung | Samsung | |||
Email: young.lee@gmail.com | Email: younglee.tx@gmail.com | |||
Dhruv Dhody | Dhruv Dhody | |||
Huawei | Huawei | |||
India | India | |||
Email: dhruv.ietf@gmail.com | Email: dhruv.ietf@gmail.com | |||
Sabine Randriamasy | Sabine Randriamasy | |||
Nokia Networks France | Nokia Networks France | |||
France | France | |||
Email: sabine.randriamasy@nokia-bell-labs.com | Email: sabine.randriamasy@nokia-bell-labs.com | |||
End of changes. 3 change blocks. | ||||
3 lines changed or deleted | 3 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |