RFC 8331 on RTP Payload for Society of Motion Picture and Television Engineers (SMPTE) ST 291-1 Ancillary Data
rfc-editor@rfc-editor.org Wed, 21 February 2018 05:40 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DA4B12E86C; Tue, 20 Feb 2018 21:40:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2eleVDHj2K3D; Tue, 20 Feb 2018 21:40:06 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94392124D37; Tue, 20 Feb 2018 21:40:06 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 14C8BB81822; Tue, 20 Feb 2018 21:40:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8331 on RTP Payload for Society of Motion Picture and Television Engineers (SMPTE) ST 291-1 Ancillary Data
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, payload@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180221054003.14C8BB81822@rfc-editor.org>
Date: Tue, 20 Feb 2018 21:40:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/-_1A4cq4D_Qybt3-LwrcVbX3mek>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 05:40:08 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8331
Title: RTP Payload for Society of
Motion Picture and Television Engineers (SMPTE)
ST 291-1 Ancillary Data
Author: T. Edwards
Status: Standards Track
Stream: IETF
Date: February 2018
Mailbox: thomas.edwards@fox.com
Pages: 20
Characters: 47110
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-payload-rtp-ancillary-14.txt
URL: https://www.rfc-editor.org/info/rfc8331
DOI: 10.17487/RFC8331
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).
This document is a product of the Audio/Video Transport Payloads Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC