RFC 6597: RTP Payload Format for Society of Motion Picture and Television Engineers (SMPTE) ST 336 Encoded Data
In plain English — editorial summary, not part of the RFC
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 ST 336, into the Real-time Transport Protocol (RTP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6597
- Published
- April 2012
- Authors
- J. Downs; J. Arbeiter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6569Guidelines for Development of an Audio Codec within the IETFCurrent
March 2012
- RFC 6647Email Greylisting: An Applicability Statement for SMTPCurrent
June 2012
- RFC 6648Deprecating the "X-" Prefix and Similar Constructs in Application ProtocolsCurrent
June 2012
- RFC 6544TCP Candidates with Interactive Connectivity Establishment (ICE)Current
March 2012
- RFC 6657Update to MIME regarding "charset" Parameter Handling in Textual Media TypesCurrent
July 2012
- RFC 6659Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) MethodCurrent
July 2012
- RFC 6665SIP-Specific Event NotificationUpdated
July 2012
- RFC 6522The Multipart/Report Media Type for the Reporting of Mail System Administrative MessagesUpdated
January 2012
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?