[xrblock] RFC 6843 on RTP Control Protocol (RTCP) Extended Report (XR) Block for Delay Metric Reporting

rfc-editor@rfc-editor.org Tue, 15 January 2013 01:34 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 F20E711E80DF; Mon, 14 Jan 2013 17:34:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.154
X-Spam-Level:
X-Spam-Status: No, score=-102.154 tagged_above=-999 required=5 tests=[AWL=-0.154, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmLIoYjMBw-r; Mon, 14 Jan 2013 17:34:18 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 903A611E80E4; Mon, 14 Jan 2013 17:34:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 2405EB1E00D; Mon, 14 Jan 2013 17:23:33 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130115012333.2405EB1E00D@rfc-editor.org>
Date: Mon, 14 Jan 2013 17:23:33 -0800 (PST)
Cc: xrblock@ietf.org, rfc-editor@rfc-editor.org
Subject: [xrblock] RFC 6843 on RTP Control Protocol (RTCP) Extended Report (XR) Block for Delay 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: Tue, 15 Jan 2013 01:34:19 -0000

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

        
        RFC 6843

        Title:      RTP Control Protocol (RTCP) Extended 
                    Report (XR) Block for Delay Metric 
                    Reporting 
        Author:     A. Clark, K. Gross,
                    Q. Wu
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2013
        Mailbox:    alan.d.clark@telchemy.com, 
                    kevin.gross@avanw.com, 
                    sunseawq@huawei.com
        Pages:      9
        Characters: 18354
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-xrblock-rtcp-xr-delay-12.txt

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

This document defines an RTP Control Protocol (RTCP) Extended Report
(XR) block that allows the reporting of delay metrics for use in a
range of Real-time Transport Protocol (RTP) applications.  
[STANDARDS-TRACK]

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 Protocol.

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