RTP Payload Format for HTTP Adaptive Streaming
draft-wei-payload-has-over-rtp-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-30
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
INTERNET-DRAFT                                                    Q. Wei
Intended Status: Standard Track                                 R. Huang
Expires: May 2, 2017                                            H. Zheng
                                                                  Huawei
                                                        October 29, 2016

             RTP Payload Format for HTTP Adaptive Streaming
                   draft-wei-payload-has-over-rtp-01

Abstract

   whis document introduces a new RTP payload format for encapsulating
   the HTTP Adaptive Streaming (HAS) data into RTP, so that current RTP
   schemes can be leveraged into OTT video delivery services. For
   example, operators can easily deliver OTT live content through
   multicast eliminating the impact of live content consumption peaks.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2016 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
 

<Wei&Huang>               Expires May 2, 2017                   [Page 1]
INTERNET DRAFT        <RTP Payload Format for HAS>      October 29, 2016

   (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

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Existing Technologies  . . . . . . . . . . . . . . . . . . . .  3
     3.1  HTTP Adaptive Streaming . . . . . . . . . . . . . . . . . .  3
     3.2  Multicast Adaptive Bit Rate (Multicast-ABR) . . . . . . . .  4
   4.  HAS Over RTP Use Scenarios . . . . . . . . . . . . . . . . . .  5
   5.  Overview of HTTP Adaptive Streaming over RTP . . . . . . . . .  5
   6.  HTTP Adaptive Streaming Payload  . . . . . . . . . . . . . . .  7
     6.1  RTP Payload Format for HAS Content  . . . . . . . . . . . .  7
     6.2  Use Existing RTP Payload Format for HAS Content . . . . . . 10
     6.3  Manifest file and Initial Information Consideration . . . . 10
   7.  Payload Format Parameters  . . . . . . . . . . . . . . . . . . 11
     7.1  Media Type Definition . . . . . . . . . . . . . . . . . . . 11
     7.2  SDP Signaling . . . . . . . . . . . . . . . . . . . . . . . 12
   8.  Congestion Control . . . . . . . . . . . . . . . . . . . . . . 12
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   10.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
   11.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
   12.  References  . . . . . . . . . . . . . . . . . . . . . . . . . 13
     12.1  Normative References . . . . . . . . . . . . . . . . . . . 13
     12.2  Informative References . . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

 

<Wei&Huang>               Expires May 2, 2017                   [Page 2]
INTERNET DRAFT        <RTP Payload Format for HAS>      October 29, 2016

1.  Introduction

   Video consumption has exploded over the last few years as more and
   more consumers are watching live Over-the-Top (OTT) content on
   smartphones, tablets, PCs and other IP connected devices. Since OTT
   video services rely on HTTP adaptive streaming (HAS) technology,
   e.g., DASH and HTTP Live Streaming (HLS), to deliver content, so
   every time a user requests a piece of content, a stream is sent
Show full document text