rfc9817v1.txt | rfc9817.txt | |||
---|---|---|---|---|
Internet Research Task Force (IRTF) I. Kunze | Internet Research Task Force (IRTF) I. Kunze | |||
Request for Comments: 9817 K. Wehrle | Request for Comments: 9817 K. Wehrle | |||
Category: Informational RWTH Aachen | Category: Informational RWTH Aachen | |||
ISSN: 2070-1721 D. Trossen | ISSN: 2070-1721 D. Trossen | |||
Huawei | DaPaDOT Tech | |||
M-J. Montpetit | M-J. Montpetit | |||
McGill | McGill | |||
X. de Foy | X. de Foy | |||
InterDigital Communications, LLC | InterDigital Communications, LLC | |||
D. Griffin | D. Griffin | |||
M. Rio | M. Rio | |||
UCL | UCL | |||
July 2025 | July 2025 | |||
Use Cases for In-Network Computing | Use Cases for In-Network Computing | |||
skipping to change at line 1018 ¶ | skipping to change at line 1018 ¶ | |||
* RQ 4.1.3: How to find suitable tradeoffs regarding simplicity of | * RQ 4.1.3: How to find suitable tradeoffs regarding simplicity of | |||
the control function ("accuracy of the control") and | the control function ("accuracy of the control") and | |||
implementation complexity ("implementability")? | implementation complexity ("implementability")? | |||
* RQ 4.1.4: How to (dynamically) distribute simplified versions of | * RQ 4.1.4: How to (dynamically) distribute simplified versions of | |||
the global (control) function among COIN execution environments? | the global (control) function among COIN execution environments? | |||
* RQ 4.1.5: How to (dynamically) compose or recompose the | * RQ 4.1.5: How to (dynamically) compose or recompose the | |||
distributed control functions? | distributed control functions? | |||
* RQ 4.1.6: Can there be different control levels, e.g., "quite | * RQ 4.1.6: Can there be different control levels? For example, | |||
inaccurate & very low latency" (PNDs, deep in the network), "more | "quite inaccurate & very low latency" for PNDs deep in the | |||
accurate & higher latency" (more powerful COIN execution | network; "more accurate & higher latency" for more powerful COIN | |||
environments, farther away), "very accurate & very high latency" | execution environments that are farther away; and "very accurate & | |||
(cloud environments, far away)? | very high latency" for cloud environments that are far away. | |||
* RQ 4.1.7: Who decides which control instance is executed and which | * RQ 4.1.7: Who decides which control instance is executed and which | |||
information can be used for this decision? | information can be used for this decision? | |||
* RQ 4.1.8: How do the different control instances interact and how | * RQ 4.1.8: How do the different control instances interact and how | |||
can we define their hierarchy? | can we define their hierarchy? | |||
4.1.6. Additional Desirable Capabilities | 4.1.6. Additional Desirable Capabilities | |||
In addition to the capabilities driven by the research questions | In addition to the capabilities driven by the research questions | |||
skipping to change at line 1596 ¶ | skipping to change at line 1596 ¶ | |||
network programming of individual virtual switches. To our | network programming of individual virtual switches. To our | |||
knowledge, no complete solution has been developed for deploying | knowledge, no complete solution has been developed for deploying | |||
virtual COIN programs over mobile or data center networks. | virtual COIN programs over mobile or data center networks. | |||
5.3.4. Opportunities | 5.3.4. Opportunities | |||
Virtual network programming by tenants could bring benefits such as: | Virtual network programming by tenants could bring benefits such as: | |||
* A unified programming model, which can facilitate porting COIN | * A unified programming model, which can facilitate porting COIN | |||
programs between data centers, 5G networks, and other fixed and | programs between data centers, 5G networks, and other fixed and | |||
wireless networks, as well as sharing controller, code and | wireless networks, as well as sharing controllers, code, and | |||
expertise. | expertise. | |||
* Increasing the level of customization available to customers/ | * Increasing the level of customization available to customers/ | |||
tenants of mobile networks or data centers compared to typical | tenants of mobile networks or data centers compared to typical | |||
configuration capabilities. For example, 5G network evolution | configuration capabilities. For example, 5G network evolution | |||
points to an ever-increasing specialization and customization of | points to an ever-increasing specialization and customization of | |||
private mobile networks, which could be handled by tenants using a | private mobile networks, which could be handled by tenants using a | |||
programming model similar to P4. | programming model similar to P4. | |||
* Using network programs to influence underlying network services | * Using network programs to influence underlying network services | |||
skipping to change at line 2129 ¶ | skipping to change at line 2129 ¶ | |||
[RÜTH] Rüth, J., Glebke, R., Wehrle, K., Causevic, V., and S. | [RÜTH] Rüth, J., Glebke, R., Wehrle, K., Causevic, V., and S. | |||
Hirche, "Towards In-Network Industrial Feedback Control", | Hirche, "Towards In-Network Industrial Feedback Control", | |||
Proceedings of the 2018 Morning Workshop on In-Network | Proceedings of the 2018 Morning Workshop on In-Network | |||
Computing, pp. 14-19, DOI 10.1145/3229591.3229592, August | Computing, pp. 14-19, DOI 10.1145/3229591.3229592, August | |||
2018, <https://doi.org/10.1145/3229591.3229592>. | 2018, <https://doi.org/10.1145/3229591.3229592>. | |||
[SA2-5GLAN] | [SA2-5GLAN] | |||
3GPP-5glan, "SP-181129, Work Item Description, | 3GPP-5glan, "SP-181129, Work Item Description, | |||
Vertical_LAN(SA2), 5GS Enhanced Support of Vertical and | Vertical_LAN(SA2), 5GS Enhanced Support of Vertical and | |||
LAN Services", 3GPP , 2021, | LAN Services", 3GPP , 2021, | |||
<http://www.3gpp.org/ftp/tsg_sa/TSG_SA/Docs/SP- | <https://www.3gpp.org/ftp/tsg_sa/TSG_SA/TSGS_82/Docs/SP- | |||
181120.zip>. | 181120.zip>. | |||
[SarNet2021] | [SarNet2021] | |||
Glebke, R., Trossen, D., Kunze, I., Lou, D., Ruth, J., | Glebke, R., Trossen, D., Kunze, I., Lou, D., Ruth, J., | |||
Stoffers, M., and K. Wehrle, "Service-based Forwarding via | Stoffers, M., and K. Wehrle, "Service-based Forwarding via | |||
Programmable Dataplanes", 2021 IEEE 22nd International | Programmable Dataplanes", 2021 IEEE 22nd International | |||
Conference on High Performance Switching and Routing | Conference on High Performance Switching and Routing | |||
(HPSR), pp. 1-8, DOI 10.1109/hpsr52026.2021.9481814, June | (HPSR), pp. 1-8, DOI 10.1109/hpsr52026.2021.9481814, June | |||
2021, <https://doi.org/10.1109/hpsr52026.2021.9481814>. | 2021, <https://doi.org/10.1109/hpsr52026.2021.9481814>. | |||
skipping to change at line 2159 ¶ | skipping to change at line 2159 ¶ | |||
Rodriguez, P., and P. Steenkiste, "Multi-Context TLS | Rodriguez, P., and P. Steenkiste, "Multi-Context TLS | |||
(mcTLS): Enabling Secure In-Network Functionality in TLS", | (mcTLS): Enabling Secure In-Network Functionality in TLS", | |||
ACM SIGCOMM Computer Communication Review, vol. 45, no. 4, | ACM SIGCOMM Computer Communication Review, vol. 45, no. 4, | |||
pp. 199-212, DOI 10.1145/2829988.2787482, August 2015, | pp. 199-212, DOI 10.1145/2829988.2787482, August 2015, | |||
<https://doi.org/10.1145/2829988.2787482>. | <https://doi.org/10.1145/2829988.2787482>. | |||
[Stoyanov] Stoyanov, R. and N. Zilberman, "MTPSA: Multi-Tenant | [Stoyanov] Stoyanov, R. and N. Zilberman, "MTPSA: Multi-Tenant | |||
Programmable Switches", Proceedings of the 3rd P4 Workshop | Programmable Switches", Proceedings of the 3rd P4 Workshop | |||
in Europe, pp. 43-48, DOI 10.1145/3426744.3431329, | in Europe, pp. 43-48, DOI 10.1145/3426744.3431329, | |||
December 2020, | December 2020, | |||
<https://eng.ox.ac.uk/media/6354/stoyanov2020mtpsa.pdf>. | <https://dl.acm.org/doi/10.1145/3426744.3431329>. | |||
[Sultana] Sultana, N., Sonchack, J., Giesen, H., Pedisich, I., Han, | [Sultana] Sultana, N., Sonchack, J., Giesen, H., Pedisich, I., Han, | |||
Z., Shyamkumar, N., Burad, S., DeHon, A., and B. T. Loo, | Z., Shyamkumar, N., Burad, S., DeHon, A., and B. T. Loo, | |||
"Flightplan: Dataplane Disaggregation and Placement for P4 | "Flightplan: Dataplane Disaggregation and Placement for P4 | |||
Programs", | Programs", | |||
<https://flightplan.cis.upenn.edu/flightplan.pdf>. | <https://flightplan.cis.upenn.edu/flightplan.pdf>. | |||
[TLSSURVEY] | [TLSSURVEY] | |||
de Carné de Carnavalet, X. and P. van Oorschot, "A Survey | de Carné de Carnavalet, X. and P. van Oorschot, "A Survey | |||
and Analysis of TLS Interception Mechanisms and | and Analysis of TLS Interception Mechanisms and | |||
skipping to change at line 2242 ¶ | skipping to change at line 2242 ¶ | |||
Email: kunze@comsys.rwth-aachen.de | Email: kunze@comsys.rwth-aachen.de | |||
Klaus Wehrle | Klaus Wehrle | |||
RWTH Aachen University | RWTH Aachen University | |||
Ahornstr. 55 | Ahornstr. 55 | |||
D-52074 Aachen | D-52074 Aachen | |||
Germany | Germany | |||
Email: wehrle@comsys.rwth-aachen.de | Email: wehrle@comsys.rwth-aachen.de | |||
Dirk Trossen | Dirk Trossen | |||
Huawei Technologies Duesseldorf GmbH | DaPaDOT Tech UG (haftungsbeschränkt) | |||
Riesstr. 25C | Palestrinastr. 7A | |||
D-80992 Munich | D-80639 Munich | |||
Germany | Germany | |||
Email: Dirk.Trossen@Huawei.com | Email: dirk@dapadot-tech.eu | |||
Marie-Jose Montpetit | Marie-Jose Montpetit | |||
McGill University | McGill University | |||
680 Sherbrooke Street W. | 680 Sherbrooke Street W. | |||
Montreal H3A 3R1 | Montreal H3A 3R1 | |||
Canada | Canada | |||
Email: marie-jose.montpetit@mcgill.ca | Email: marie-jose.montpetit@mcgill.ca | |||
Xavier de Foy | Xavier de Foy | |||
InterDigital Communications, LLC | InterDigital Communications, LLC | |||
End of changes. 7 change blocks. | ||||
13 lines changed or deleted | 13 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |