RFC 8451 on Considerations for Selecting RTP Control Protocol (RTCP) Extended Report (XR) Metrics for the WebRTC Statistics API
rfc-editor@rfc-editor.org Wed, 19 September 2018 13:30 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 132C7130FE9; Wed, 19 Sep 2018 06:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 GQq5myTzoIWC; Wed, 19 Sep 2018 06:30:26 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA8CF130E0C; Wed, 19 Sep 2018 06:30:26 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2788EB80D18; Wed, 19 Sep 2018 06:30:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8451 on Considerations for Selecting RTP Control Protocol (RTCP) Extended Report (XR) Metrics for the WebRTC Statistics API
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, xrblock@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180919133026.2788EB80D18@rfc-editor.org>
Date: Wed, 19 Sep 2018 06:30:26 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/2cA3aqIAoEU1AUpY_NdPPv1a7TQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2018 13:30:28 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8451
Title: Considerations for Selecting RTP Control
Protocol (RTCP) Extended Report (XR) Metrics
for the WebRTC Statistics API
Author: V. Singh,
R. Huang,
R. Even,
D. Romascanu,
L. Deng
Status: Informational
Stream: IETF
Date: September 2018
Mailbox: varun@callstats.io,
rachel.huang@huawei.com,
roni.even@huawei.com,
dromasca@gmail.com,
denglingli@chinamobile.com
Pages: 18
Characters: 38823
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-10.txt
URL: https://www.rfc-editor.org/info/rfc8451
DOI: 10.17487/RFC8451
This document describes monitoring features related to media streams
in Web real-time communication (WebRTC). It provides a list of
RTP Control Protocol (RTCP) Sender Report (SR), Receiver Report (RR), and
Extended Report (XR) metrics, which may need to be supported by RTP
implementations in some diverse environments. It lists a set of
identifiers for the WebRTC's statistics API. These identifiers are a set
of RTCP SR, RR, and XR metrics related to the transport of multimedia
flows.
This document is a product of the Metric Blocks for use with RTCP's Extended Report Framework Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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/retrieve/bulk
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