Real-time Transport Object delivery over Unidirectional Transport (ROUTE)
draft-zia-route-00

Document Type Expired Internet-Draft (individual)
Authors Waqar Zia  , Thomas Stockhammer 
Last updated 2020-12-31 (latest revision 2020-06-29)
Stream Independent Submission
Intended RFC status Informational
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream ISE state In ISE Review
Consensus Boilerplate Unknown
Document shepherd Adrian Farrel
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to Adrian Farrel <rfc-ise@rfc-editor.org>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-zia-route-00.txt

Abstract

The Real-time Transport Object delivery over Unidirectional Transport protocol (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, or a DASH or 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 IP/UDP including multicast IP. 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.

Authors

Waqar Zia (wzia@qti.qualcomm.com)
Thomas Stockhammer (tsto@qti.qualcomm.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)