@TechReport{ draft-wr-mptcp-single-homed,
	author = "Rolf Winter and Michael Faath and Andreas Ripke",
	title = "{Multipath TCP Support for Single-homed End-systems}",
	type = "Internet Draft",
	number = "draft-wr-mptcp-single-homed-07",
	day = "21",
	month = mar,
	year = "2016",
	institution = "IETF, Individual Submission",
	language = "english",
	abstract = "{Multipath TCP relies on the existence of multiple paths between end- systems. These are typically provided by using different IP addresses obtained by different ISPs at the end-systems. While this scenario is certainly becoming increasingly a reality~(e.g.\ mobile devices), currently most end-systems are single-homed~(e.g.\ desktop PCs in an enterprise). It seems also likely that a lot of network sites will insist on having all traffic pass a single network element~(e.g.\ for security reasons) before traffic is split across multiple paths. This memo therefore describes mechanisms to make multiple paths available to multipath TCP-capable end-systems that are not available directly at the end-systems but somewhere within the network.}",
	url = "https://tools.ietf.org/id/draft-wr-mptcp-single-homed-07.txt",
	url.size = "18573",
	url.md5 = "338bb9171a0c7f168de35110949f23aa",
	url.mime = "text/plain",
	url.checked = "2020-12-03 11:19:50 CET"
}