RFC 8286 on RTP/RTCP Extension for RTP Splicing Notification
rfc-editor@rfc-editor.org Thu, 26 October 2017 00:23 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 0CA9F13F511; Wed, 25 Oct 2017 17:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 LUjkU541A564; Wed, 25 Oct 2017 17:23:46 -0700 (PDT)
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 007A113F4F6; Wed, 25 Oct 2017 17:23:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 57368B80E21; Wed, 25 Oct 2017 17:23:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8286 on RTP/RTCP Extension for RTP Splicing Notification
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, avtext@ietf.org
Message-Id: <20171026002334.57368B80E21@rfc-editor.org>
Date: Wed, 25 Oct 2017 17:23:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/yh6jpPFyFCOEiMJeXb2E_9S5Cwk>
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: Thu, 26 Oct 2017 00:23:48 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8286
Title: RTP/RTCP Extension for RTP Splicing
Notification
Author: J. Xia,
R. Even,
R. Huang,
L. Deng
Status: Standards Track
Stream: IETF
Date: October 2017
Mailbox: xiajinwei@huawei.com,
roni.even@huawei.com,
rachel.huang@huawei.com,
denglingli@chinamobile.com
Pages: 22
Characters: 45384
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-avtext-splicing-notification-09.txt
URL: https://www.rfc-editor.org/info/rfc8286
DOI: 10.17487/RFC8286
Content splicing is a process that replaces the content of a main
multimedia stream with other multimedia content and that delivers the
substitutive multimedia content to the receivers for a period of
time. The splicer is designed to handle RTP splicing and needs to
know when to start and end the splicing.
This memo defines two RTP/RTCP extensions to indicate the
splicing-related information to the splicer: an RTP header extension
that conveys the information "in band" and an RTP Control Protocol
(RTCP) packet that conveys the information out of band.
This document is a product of the Audio/Video Transport Extensions 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