[xrblock] RFC 7244 on RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Synchronization Delay and Offset Metrics Reporting
rfc-editor@rfc-editor.org Fri, 16 May 2014 21:40 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 3FE411A02D3; Fri, 16 May 2014 14:40:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 FUleof-YWP5v; Fri, 16 May 2014 14:39:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 8DADE1A02E3; Fri, 16 May 2014 14:39:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B61C9180450; Fri, 16 May 2014 14:38:44 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140516213844.B61C9180450@rfc-editor.org>
Date: Fri, 16 May 2014 14:38:44 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/xrblock/d3ZkDJSktpr11LXVjU6wJtDQk5M
Cc: drafts-update-ref@iana.org, xrblock@ietf.org, rfc-editor@rfc-editor.org
Subject: [xrblock] RFC 7244 on RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Synchronization Delay and Offset Metrics Reporting
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: Fri, 16 May 2014 21:40:00 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7244
Title: RTP Control Protocol (RTCP) Extended
Report (XR) Blocks for Synchronization Delay
and Offset Metrics Reporting
Author: H. Asaeda, Q. Wu, R. Huang
Status: Standards Track
Stream: IETF
Date: May 2014
Mailbox: asaeda@nict.go.jp,
bill.wu@huawei.com,
Rachel@huawei.com
Pages: 13
Characters: 27341
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-xrblock-rtcp-xr-synchronization-09.txt
URL: http://www.rfc-editor.org/rfc/rfc7244.txt
This document defines two RTP Control Protocol (RTCP) Extended Report (XR)
blocks that allow the reporting of initial synchronization delay and
synchronization offset 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/search
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