RFC 9223: Real-Time Transport Object Delivery over Unidirectional Transport (ROUTE)
In plain English — editorial summary, not part of the RFC
The Real-time Transport Object delivery over Unidirectional Transport (ROUTE) protocol is specified for robust delivery of Application Objects, including Application Objects with real-time delivery constraints, to receivers over a unidirectional transport. Application Objects consist of data that has meaning to applications that use the ROUTE protocol for delivery of data to receivers; for example, it can be a file, a Dynamic Adaptive Streaming over HTTP (DASH) or HTTP Live Streaming (HLS) segment, a WAV audio clip, etc. The ROUTE protocol also supports low-latency streaming applications. The ROUTE protocol is suitable for unicast, broadcast, and multicast transport. Therefore, it can be run over UDP/IP, including multicast IP. The ROUTE protocol can leverage the features of the underlying protocol layer, e.g., to provide security, it can leverage IP security protocols such as IPsec. This document specifies the ROUTE protocol such that it could be used by a variety of services for delivery of Application Objects by specifying their own profiles of this protocol (e.g., by adding or constraining some features). This is not an IETF specification and does not have IETF consensus.
Document record
- Document ID
- RFC9223
- Published
- April 2022
- Authors
- W. Zia; T. Stockhammer; L. Chaponniere; G. Mandyam; M. Luby
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 9317Operational Considerations for Streaming MediaCurrent
October 2022
- RFC 9119Multicast Considerations over IEEE 802 Wireless MediaCurrent
October 2021
- RFC 4563The Key ID Information Type for the General Extension Payload in Multimedia Internet KEYing (MIKEY)Updated
June 2006
- RFC 3695Compact Forward Error Correction (FEC) SchemesObsoleted
February 2004
- RFC 3452Forward Error Correction (FEC) Building BlockObsoleted
December 2002
- RFC 1301Multicast Transport ProtocolCurrent
February 1992
- RFC 9262Tree Engineering for Bit Index Explicit Replication (BIER-TE)Current
October 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?