MSYNC
draft-bichot-msync-00

Document Type Active Internet-Draft (individual)
Authors Sophie Bale  , Remy Brebion  , Guillaume Bichot 
Last updated 2020-10-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized 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                                                   S. Bale
Intended Status: Standards track                              R. Brebion
Expires: April 16 2021                                         G. Bichot
                                                               Broadpeak
                                                         October 13 2020

                                 MSYNC 
                         draft-bichot-msync-00

Abstract

   This document describes the  Multicast Synchronisation (MSYNC)
   Protocol that aims at transferring video media objects over IP
   multicast operating preferably RTP. Although generic, MSYNC has been
   primarily designed for transporting HTTP adaptive streaming (HAS)
   objects including manifest/playlists and media segments (e.g. MP4,
   CMAF) according to an HAS protocol such as Apple HLS or MPEG DASH
   between a multicast server and a multicast gateway.          

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) 2020 IETF Trust and the persons identified as the
   document authors. All rights reserved.

 

Bale et aL.              Expires April 16 2021                  [Page 1]
Internet-Draft                   MSYNC                  October 13, 2020

   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

   1  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.2  Definitions . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
   3. MSYNC Protocol  . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.1. MSYNC packet format . . . . . . . . . . . . . . . . . . . .  6
     3.2. Object info packet  . . . . . . . . . . . . . . . . . . . .  7
     3.3. Object data packet  . . . . . . . . . . . . . . . . . . . .  8
     3.4. Object HTTP header packet . . . . . . . . . . . . . . . . .  9
     3.5. Object data-part packet . . . . . . . . . . . . . . . . . . 10
     3.6. Maximum size of a MSYNC packet  . . . . . . . . . . . . . . 11
     3.7. Sending MSYNC objects over IP/transport multicast
          sessions  . . . . . . . . . . . . . . . . . . . . . . . . . 11
     3.8. Mapping player request with IP/transport multicast 
          sessions  . . . . . . . . . . . . . . . . . . . . . . . . . 12
     3.9. HAS protocol dependency . . . . . . . . . . . . . . . . . . 13
       3.9.1. Object info packet  . . . . . . . . . . . . . . . . . . 13
         3.9.1.1. media sequence  . . . . . . . . . . . . . . . . . . 13
         3.9.1.3. object URI  . . . . . . . . . . . . . . . . . . . . 14
       3.9.2. Sending rules . . . . . . . . . . . . . . . . . . . . . 14
     3.10. RTP as the transport multicast session protocol  . . . . . 15
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 16
   5.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
     5.1.  Normative References . . . . . . . . . . . . . . . . . . . 16
     5.2.  Informative References . . . . . . . . . . . . . . . . . . 17
   Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . . . 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17

 

Bale et aL.              Expires April 16 2021                  [Page 2]
Internet-Draft                   MSYNC                  October 13, 2020

1  Introduction

   MSYNC relies preferably on RTP that makes it particularly suited for
   transitioning IPTV legacy(MPEG2 TS/RTP) to the HAS ecosystem. MSYNC
Show full document text