A layered network architecture separates responsibilities behind communication interfaces. A transport protocol can offer an application a service built over Internet Protocol without requiring each underlying network to implement that application. Layer boundaries are engineering choices: the end-to-end principle helps assess which properties a lower layer can actually establish.
A transport protocol provides communication services between its transport endpoints over an underlying network. Transmission Control Protocol supplies a reliable ordered byte stream; User Datagram Protocol supplies datagrams without that built-in recovery service. Applications can implement further mechanisms over either interface.
QUIC is a transport protocol designed over User Datagram Protocol with multiple streams and cryptographic protection. At the 17 January 2020 examination date, the cited November 2019 design was an Internet-Draft and work in progress. This historical description does not treat a later standard as already available.[ref]
User Datagram Protocol supplies a datagram transport interface without built-in reliable ordered-stream delivery. An application or another protocol can add recovery over that interface, as the pre-2020 QUIC design illustrates.
Transmission Control Protocol provides a reliable ordered byte-stream service between its endpoints, using sequencing, acknowledgements and retransmission. Receipt by that transport does not establish that a receiving application has durably stored the data or completed a user operation.[ref]

Articles by others on the same topic (0)

There are currently no matching articles.