[xrblock] RFC 6958 on RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Loss Metric Reporting

rfc-editor@rfc-editor.org Fri, 24 May 2013 23:21 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE76B21F8CA5; Fri, 24 May 2013 16:21:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.116
X-Spam-Level:
X-Spam-Status: No, score=-102.116 tagged_above=-999 required=5 tests=[AWL=-0.116, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8P70SnfOYQxR; Fri, 24 May 2013 16:21:46 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id E745621F8C23; Fri, 24 May 2013 16:21:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 20AA962109; Fri, 24 May 2013 16:21:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130524232105.20AA962109@rfc-editor.org>
Date: Fri, 24 May 2013 16:21:05 -0700 (PDT)
Cc: xrblock@ietf.org, rfc-editor@rfc-editor.org
Subject: [xrblock] RFC 6958 on RTP Control Protocol (RTCP) Extended Report (XR) Block for Burst/Gap Loss Metric Reporting
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 24 May 2013 23:21:48 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6958

        Title:      RTP Control Protocol (RTCP) Extended 
                    Report (XR) Block for Burst/Gap Loss 
                    Metric Reporting 
        Author:     A. Clark, S. Zhang,
                    J. Zhao, Q. Wu, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2013
        Mailbox:    alan.d.clark@telchemy.com, 
                    zhangyx@sttri.com.cn, 
                    zhaojing@sttri.com.cn,
                    sunseawq@huawei.com
        Pages:      16
        Characters: 31057
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-xrblock-rtcp-xr-burst-gap-loss-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6958.txt

This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) Block that allows the reporting of burst and gap loss metrics
for use in a range of RTP applications. 

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://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