[xrblock] RFC 7509 on RTP Control Protocol (RTCP) Extended Report (XR) for Post-Repair Loss Count Metrics
rfc-editor@rfc-editor.org Wed, 13 May 2015 21:14 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09F801ACE44; Wed, 13 May 2015 14:14:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 sEZFKsKdQBrx; Wed, 13 May 2015 14:14:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2551ACE2E; Wed, 13 May 2015 14:14:54 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 68337180209; Wed, 13 May 2015 14:13:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150513211307.68337180209@rfc-editor.org>
Date: Wed, 13 May 2015 14:13:07 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/xrblock/apYzgp7YkL0FnTojLR3KuPDXsLY>
Cc: drafts-update-ref@iana.org, xrblock@ietf.org, rfc-editor@rfc-editor.org
Subject: [xrblock] RFC 7509 on RTP Control Protocol (RTCP) Extended Report (XR) for Post-Repair Loss Count Metrics
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2015 21:14:56 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7509 Title: RTP Control Protocol (RTCP) Extended Report (XR) for Post-Repair Loss Count Metrics Author: R. Huang, V. Singh Status: Standards Track Stream: IETF Date: May 2015 Mailbox: rachel.huang@huawei.com, varun@comnet.tkk.fi Pages: 11 Characters: 23350 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-xrblock-rtcp-xr-post-repair-loss-count-11.txt URL: https://www.rfc-editor.org/info/rfc7509 DOI: http://dx.doi.org/10.17487/RFC7509 This document defines an RTP Control Protocol (RTCP) Extended Report (XR) block that allows reporting of a post-repair loss count metric for a range of RTP applications. In addition, another metric, repaired loss count, is also introduced in this report block for calculating the pre-repair loss count when needed, so that the RTP sender or a third-party entity is able to evaluate the effectiveness of the repair methods used by the system. This document is a product of the Metric Blocks for use with RTCPs Extended Report Framework 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/rfc.html 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
- [xrblock] RFC 7509 on RTP Control Protocol (RTCP)… rfc-editor
- Re: [xrblock] RFC 7509 on RTP Control Protocol (R… Romascanu, Dan (Dan)
- Re: [xrblock] RFC 7509 on RTP Control Protocol (R… Huangyihong (Rachel)