Live Media and Metadata Ingest Protocol
Active Internet-Draft (individual)
||Intended RFC status
||(No stream defined)
||RFC Editor Note
||Send notices to
Internet Engineering Task Force Sam Geqiang Zhang
Expires: January 15, 2019
Intended status: Best Current Practice July 15 2018
Live Media and Metadata Ingest Protocol
This Internet draft presents a best industry practice for
ingesting encoded live media to media processing entities.
Two profiles of the media ingest are defined covering the most
common use cases. The first profile facilates active media
processing and is based on the fragmented MPEG-4 format.
The second profile enables efficient ingest of media streaming
presentations based on established streaming protocols
by also adding a manifest besides the fragmented MPEG-4 stream.
Details on carriage of metadata markers, timed text,
subtitles and encryption specific metadata are also included.
Status of This Memo
This Internet-Draft is submitted in full conformance
with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet
Engineering Task Force (IETF). Note that other groups
may also distribute working documents as Internet-Drafts.
The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum
of six months and may be updated, replaced, or obsoleted
by other documents at any time. It is inappropriate to
use Internet-Drafts as reference material or to cite
them other than as "work in progress."
Mekuria & Zhang Expires January 15 2019 [Page1]
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described
in Section 4.e of the Trust Legal Provisions and are provided
without warranty as described in the Simplified BSD License
Table of Contents
2. Conventions and Terminology
3. Media Ingest Workflows and Use Cases
4. General Media Ingest Protocol Behavior
5. Profile 1: Fragmented MPEG-4 Ingest General Considerations
6. Profile 1: Fragmented MPEG-4 Ingest Protocol Behavior
6.1 General Protocol Requirements
6.2 Requirements for Formatting Media Tracks
6.3 Requirements for Timed Text Captions and Subtitle Streams
6.4 Requirements for Timed Metadata
6.5 Requirements for Media Processing Entity Failover
6.6 Requirements for Live Media Source Failover
7. Profile 2: DASH and HLS Ingest General Considerations
8. Profile 2: DASH and HLS Ingest Protocol Behavior
8.1 General Protocol requirements
8.2 Requirements for Formatting Media Tracks
8.3 Requirements for Timed Text, Caption and Subtitle Streams
8.4 Requirements for Timed Metadata
8.5 Requirements for Media Processing Entity Failover
8.6 Requirements for Live Media Source Failover
9. Security Considerations
10. IANA Considerations
12.1. Normative References
12.2. Informative References
12.3. URL References
Mekuria & Zhang Expires January 15 2019 [Page2]
This document describes a best practice for ingesting
encoded media content from a live source such as a
live video encoder towards distributed media
processing entities. Examples of such entities
include media packagers, publishing points,
streaming origins and content delivery networks.
The combination of live sources ingesting
media and distributed media processing entities
is important in practical video streaming deployments.
In such deployments, interoperability between
live sources and downstream processing
entities can be challenging.
This challenge comes from the fact that
there are multiple levels of interoperability
that need to be adressed and achieved.
For example, the network protocol for transmission
of data and the setup of the connectivity are important.
This includes schemes for establishing the ingest
connection, handling disconnections and failures,
procedures for repeatedly sending and receving
the data, and timely resolution of hostnames.
Show full document text