RTP Payload Format for SMPTE 336M Encoded Data
draft-ietf-payload-rtp-klv-03

The information below is for an old version of the document
Document Type Active Internet-Draft (payload WG)
Last updated 2012-02-16 (latest revision 2012-02-01)
Replaces draft-ietf-avt-rtp-klv
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Ali Begen
IESG IESG state IESG Evaluation::Revised I-D Needed
Telechat date
Needs a YES. Needs 8 more YES or NO OBJECTION positions to pass.
Responsible AD Robert Sparks
IESG note The document shepherd is Ali Begen (abegen@cisco.com).
Send notices to payload-chairs@tools.ietf.org, draft-ietf-payload-rtp-klv@tools.ietf.org
Payload Working Group                                      J. Downs, Ed.
Internet-Draft                              PAR Government Systems Corp.
Intended status: Standards Track                        J. Arbeiter, Ed.
Expires: August 4, 2012                                 February 1, 2012

             RTP Payload Format for SMPTE 336M Encoded Data
                     draft-ietf-payload-rtp-klv-03

Abstract

   This document specifies the payload format for packetization of KLV
   (Key-Length-Value) Encoded Data, as defined by the Society of Motion
   Picture and Television Engineers (SMPTE) in SMPTE 336M, into the
   Real-time Transport Protocol (RTP).

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

   This Internet-Draft will expire on August 4, 2012.

Copyright Notice

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

Downs & Arbeiter         Expires August 4, 2012                 [Page 1]
Internet-Draft       RTP Format for SMPTE 336M Data        February 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Conventions, Definitions and Acronyms  . . . . . . . . . . . .  3
   3.  Media Format Background  . . . . . . . . . . . . . . . . . . .  3
   4.  Payload Format . . . . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  RTP Header Usage . . . . . . . . . . . . . . . . . . . . .  4
     4.2.  Payload Data . . . . . . . . . . . . . . . . . . . . . . .  5
       4.2.1.  The KLVunit  . . . . . . . . . . . . . . . . . . . . .  5
       4.2.2.  KLVunit Mapping to RTP Packet Payload  . . . . . . . .  5
     4.3.  Implementation Considerations  . . . . . . . . . . . . . .  6
       4.3.1.  Loss of Data . . . . . . . . . . . . . . . . . . . . .  6
         4.3.1.1.  Damaged KLVunits . . . . . . . . . . . . . . . . .  6
         4.3.1.2.  Treatment of Damaged KLVunits  . . . . . . . . . .  7
   5.  Congestion Control . . . . . . . . . . . . . . . . . . . . . .  8
   6.  Payload Format Parameters  . . . . . . . . . . . . . . . . . .  8
     6.1.  Media Type Definition  . . . . . . . . . . . . . . . . . .  8
     6.2.  Mapping to SDP . . . . . . . . . . . . . . . . . . . . . .  9
       6.2.1.  Offer/Answer Model and Declarative Considerations  . .  9
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 11
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12

Downs & Arbeiter         Expires August 4, 2012                 [Page 2]
Internet-Draft       RTP Format for SMPTE 336M Data        February 2012

1.  Introduction

   This document specifies the payload format for packetization of KLV
   (Key-Length-Value) Encoded Data, as defined by the Society of Motion
   Picture and Television Engineers (SMPTE) in [SMPTE336M], into the
   Real-time Transport Protocol (RTP) [RFC3550].

   The payload format is defined in such a way that arbitrary KLV data
   can be carried.  No restrictions are placed on which KLV data keys
   can be used.

   A brief description of SMPTE 336M, KLV Encoded Data, is given.  The
   payload format itself, including use of the RTP header fields, is
   specified in Section 4.  The media type and IANA considerations are
   also described.  This document concludes with security considerations
Show full document text