[xrblock] RFC 6776 on Measurement Identity and Information Reporting Using a Source Description (SDES) Item and an RTCP Extended Report (XR) Block

rfc-editor@rfc-editor.org Thu, 25 October 2012 04: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 6FEA011E80F6; Wed, 24 Oct 2012 21:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.962
X-Spam-Level:
X-Spam-Status: No, score=-101.962 tagged_above=-999 required=5 tests=[AWL=0.038, 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 vcF+nR8PI5Qy; Wed, 24 Oct 2012 21:21:05 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 9046511E80E9; Wed, 24 Oct 2012 21:21:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 253E4B1E004; Wed, 24 Oct 2012 21:15:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20121025041519.253E4B1E004@rfc-editor.org>
Date: Wed, 24 Oct 2012 21:15:19 -0700 (PDT)
Cc: xrblock@ietf.org, rfc-editor@rfc-editor.org
Subject: [xrblock] RFC 6776 on Measurement Identity and Information Reporting Using a Source Description (SDES) Item and an RTCP Extended Report (XR) Block
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: Thu, 25 Oct 2012 04:21:06 -0000

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

        
        RFC 6776

        Title:      Measurement Identity and Information Reporting 
                    Using a Source Description (SDES) Item 
                    and an RTCP Extended Report (XR) 
                    Block 
        Author:     A. Clark, Q. Wu
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2012
        Mailbox:    alan.d.clark@telchemy.com, 
                    sunseawq@huawei.com
        Pages:      9
        Characters: 17259
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-xrblock-rtcp-xr-meas-identity-10.txt

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

This document defines an RTP Control Protocol (RTCP) Source
Description (SDES) item and an RTCP Extended Report (XR) block
carrying parameters that identify and describe a measurement period
to which one or more other RTCP XR blocks may refer.  [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