Diff: rfc9817v4.txt - rfc9817.txt

	rfc9817v4.txt		rfc9817.txt

	skipping to change at line 99 ¶		skipping to change at line 99 ¶
	11. Informative References		11. Informative References
	Acknowledgements		Acknowledgements
	Authors' Addresses		Authors' Addresses

	1. Introduction		1. Introduction

	The Internet was designed as a best-effort packet network, forwarding		The Internet was designed as a best-effort packet network, forwarding
	packets from source to destination with limited guarantees regarding		packets from source to destination with limited guarantees regarding
	their timely and successful reception. Data manipulation,		their timely and successful reception. Data manipulation,
	computation, and more complex protocol functionalities are generally		computation, and more complex protocol functionalities are generally

	provided by the end hosts, while network nodes are traditionally kept		provided by the end hosts, while network nodes are commonly kept
	simple and only offer a "store and forward" packet facility. This		simple and only offer a "store and forward" packet facility. This
	simplicity of purpose of the network has shown to be suitable for a		simplicity of purpose of the network has shown to be suitable for a
	wide variety of applications and has facilitated the rapid growth of		wide variety of applications and has facilitated the rapid growth of
	the Internet. However, introducing middleboxes with specialized		the Internet. However, introducing middleboxes with specialized
	functionality for enhancing performance has often led to problems due		functionality for enhancing performance has often led to problems due
	to their inflexibility.		to their inflexibility.

	However, with the rise of new services, some of which are described		However, with the rise of new services, some of which are described
	in this document, there is a growing number of application domains		in this document, there is a growing number of application domains
	that require more than best-effort forwarding, including strict		that require more than best-effort forwarding, including strict

	skipping to change at line 185 ¶		skipping to change at line 185 ¶
	for any COIN solution addressing the particular use case; we limit		for any COIN solution addressing the particular use case; we limit
	these capabilities to those directly affecting COIN, recognizing		these capabilities to those directly affecting COIN, recognizing
	that any use case will realistically require many additional		that any use case will realistically require many additional
	capabilities for its realization. We omit this dedicated section		capabilities for its realization. We omit this dedicated section
	if relevant capabilities are already sufficiently covered by the		if relevant capabilities are already sufficiently covered by the
	corresponding research questions.		corresponding research questions.

	This document discusses these six aspects along a number of		This document discusses these six aspects along a number of
	individual use cases to demonstrate the diversity of COIN		individual use cases to demonstrate the diversity of COIN
	applications. It is intended as a basis for further analyses and		applications. It is intended as a basis for further analyses and

	discussions within the wider research community. This document		discussions within the wider research community. This document has
	represents the consensus of COINRG.		received review comments at different stages of its development, by
			experts within and out of COINRG, as detailed in the Acknowledgements