RTP Payload for Society of Motion Picture and Television Engineers (SMPTE) ST 291-1 Ancillary Data
RFC 8331

Document Type RFC - Proposed Standard (February 2018; Errata)
Last updated 2018-03-28
Replaces draft-edwards-payload-rtp-ancillary
Stream IETF
Formats plain text pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication (wg milestone: Mar 2016 - Submit RTP Payload F... )
Document shepherd Ali Begen
Shepherd write-up Show (last changed 2016-08-16)
IESG IESG state RFC 8331 (Proposed Standard)
Consensus Boilerplate Yes
Telechat date
Responsible AD Ben Campbell
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                        T. Edwards
Request for Comments: 8331                                           FOX
Category: Standards Track                                  February 2018
ISSN: 2070-1721

                            RTP Payload for
       Society of Motion Picture and Television Engineers (SMPTE)
                        ST 291-1 Ancillary Data

Abstract

   This memo describes a Real-time Transport Protocol (RTP) payload
   format for the Society of Motion Picture and Television Engineers
   (SMPTE) ancillary space (ANC) data, as defined by SMPTE ST 291-1.
   SMPTE ANC data is generally used along with professional video
   formats to carry a range of ancillary data types, including time
   code, Closed Captioning, and the Active Format Description (AFD).

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in 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/rfc8331.

Copyright Notice

   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
   (https://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.

Edwards                      Standards Track                    [Page 1]
RFC 8331             RTP Payload for Ancillary Data        February 2018

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  RTP Payload Format for SMPTE ST 291 Ancillary Data  . . . . .   4
     2.1.  Payload Header Definitions  . . . . . . . . . . . . . . .   5
   3.  Payload Format Parameters . . . . . . . . . . . . . . . . . .  11
     3.1.  Media Type Definition . . . . . . . . . . . . . . . . . .  11
   4.  SDP Considerations  . . . . . . . . . . . . . . . . . . . . .  13
     4.1.  Grouping ANC Data Streams with Other Media Streams  . . .  15
   5.  Offer/Answer Model and Declarative Considerations . . . . . .  15
     5.1.  Offer/Answer Model  . . . . . . . . . . . . . . . . . . .  15
     5.2.  Declarative SDP Considerations  . . . . . . . . . . . . .  16
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  16
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  17
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  17
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  18
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  20

1.  Introduction

   This memo describes a Real-time Transport Protocol (RTP) payload
   format for the Society of Motion Picture and Television Engineers
   (SMPTE) ancillary space (ANC) data, as defined by SMPTE ST 291-1
   [ST291].  ANC data is transmitted in the ancillary space of serial
   digital video interfaces, the space outside of the active video
   region of images intended for users to view.  Ancillary space roughly
   corresponds to vertical and horizontal blanking periods of cathode
   ray tube type displays.  ANC data can carry a range of data types,
   including time code, Closed Captioning, and the Active Format
   Description (AFD).

   ANC data is generally associated with the carriage of metadata within
   the bit stream of a Serial Digital Interface (SDI), such as the
   standard definition (SD) Serial Digital Interface, the 1.5 Gb/s
   Serial Digital Interface for high definition (HD) television
   applications, or the 3 Gb/s Signal/Data Serial Interface (SMPTE ST
   259 [ST259], SMPTE ST 292-1 [ST292], and SMPTE ST 424 [ST424]).

   ANC data packet payload definitions for a specific application are
   specified by a SMPTE Standard, Recommended Practice, Registered
   Disclosure Document, or by a document generated by another
   organization, a company, or an individual (an entity).  When a
   payload format is registered with SMPTE, it is identified by a
   registered data identification word.

Edwards                      Standards Track                    [Page 2]
Show full document text