RFC 0000 ROUTE March 2022
Surname Informational [Page]
Stream:
Independent Submission
RFC:
0000
Category:
Informational
Published:
ISSN:
2070-1721
Author:
I. Surname

RFC 0000

Real-time Transport Object delivery over Unidirectional Transport (ROUTE)

Abstract

Abstract [REPLACE]

Status of This Memo

This document is not an Internet Standards Track specification; it is published for informational purposes.

This is a contribution to the RFC Series, independently of any other RFC stream. The RFC Editor has chosen to publish this document at its discretion and makes no statement about its value for implementation or deployment. Documents approved for publication by the RFC Editor are not candidates for any level of Internet Standard; see Section 2 of RFC 7841.

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc0000.

Table of Contents

1. Introduction

Table 1: Interoperability Chart
Element ATSC-ROUTE This Document DVB-MABR
LCT header field: PSI LSB Set to 0 for Source Flow Not defined Set to 1 for Source Flow for CMAF Random access chunk
LCT header field: CCI May be set to 0 May be set to EPT for Source Flow
LCT header extensions EXT_ROUTE_​PRESENTATION_TIME Header used for MDE mode Not defined; may be added by a profile. Shall not be used.
EXT_TIME Header linked to MDE mode in Annex A.3.7.2 EXT_TIME Header may be used regardless (for FDT-Instance@Expires calculation)
Codepoints Full set Does not specify range 11 - 255 (leaves to profiles) Restricted to 5 - 9
Session metadata Full set Only defines a small subset of data necessary for setting up Source and Repair Flows. Does not define format or encoding of data except if data is integral/alphanumerical. Leaves rest to profiles. Reuses A/331 metadata, duplicated from its own service signaling.
Extended FDT Instance shall not be sent with Source Flow Not restricted, may be restricted by a profile. Instance shall not be sent with Source Flow
No restriction Only allowed in File Mode
Delivery Object Mode File, Entity, Signed/unsigned package Signed/unsigned package not allowed
Sender operation: Packetization Defined for DASH segment Defined for DASH segment and CMAF Chunks
Receiver object recovery Object handed to application upon complete reception Object may be handed before completion if MPD@availabilityTimeOffset signaled
- Fast Stream acquisition guideline provided

Author's Address

Fullname