< draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-07.txt		draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-08.txt >
	XR Block Working Group V. Singh		XR Block Working Group V. Singh
	Internet-Draft callstats.io		Internet-Draft callstats.io
	Intended status: Informational R. Huang		Intended status: Informational R. Huang
	Expires: June 14, 2018 R. Even		Expires: August 13, 2018 R. Even
	Huawei		Huawei
	D. Romascanu		D. Romascanu
	Individual		Individual
	L. Deng		L. Deng
	China Mobile		China Mobile
	December 11, 2017		February 9, 2018
	Considerations for Selecting RTCP Extended Report (XR) Metrics for the		Considerations for Selecting RTCP Extended Report (XR) Metrics for the
	WebRTC Statistics API		WebRTC Statistics API
	draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-07		draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-08
	Abstract		Abstract
	This document describes monitoring features related to media streams		This document describes monitoring features related to media streams
	in Web real-time communication (WebRTC). It provides a list of RTCP		in Web real-time communication (WebRTC). It provides a list of RTCP
	Sender Report, Receiver Report and Extended Report metrics, which may		Sender Report, Receiver Report and Extended Report metrics, which may
	need to be supported by RTP implementations in some diverse		need to be supported by RTP implementations in some diverse
	environments. It lists a set of identifiers for the WebRTC's		environments. It lists a set of identifiers for the WebRTC's
	statistics API. These identifiers are a set of RTCP SR, RR, and XR		statistics API. These identifiers are a set of RTCP SR, RR, and XR
	metrics related to the transport of multimedia flows.		metrics related to the transport of multimedia flows.
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on January 21, 2018.		This Internet-Draft will expire on January 21, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2017 IETF Trust and the persons identified as the		Copyright (c) 2018 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 3, line 43 ¶		skipping to change at page 3, line 43 ¶
	In this document, we provide rationale for choosing additional RTP		In this document, we provide rationale for choosing additional RTP
	metrics for the WebRTC getStats() API [W3C.WD-webrtc-20161124]. All		metrics for the WebRTC getStats() API [W3C.WD-webrtc-20161124]. All
	identifiers proposed in this document are recommended to be		identifiers proposed in this document are recommended to be
	implemented by an WebRTC endpoint. An endpoint may choose not to		implemented by an WebRTC endpoint. An endpoint may choose not to
	expose an identifier if it does not implement the corresponding RTCP		expose an identifier if it does not implement the corresponding RTCP
	Report.		Report.
	2. Terminology		2. Terminology
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in [RFC2119].
	ReportGroup: It is a set of metrics identified by a common		ReportGroup: It is a set of metrics identified by a common
	Synchronization source (SSRC).		Synchronization source (SSRC).
	3. RTP Statistics in WebRTC Implementations		3. RTP Statistics in WebRTC Implementations
	The RTCP Sender Reports (SRs) and Receiver Reports (RRs) [RFC3550]		The RTCP Sender Reports (SRs) and Receiver Reports (RRs) [RFC3550]
	exposes the basic metrics for the local and remote media streams.		exposes the basic metrics for the local and remote media streams.
	However, these metrics provides only partial or limited information,		However, these metrics provides only partial or limited information,
	which may not be sufficient for diagnosing problems or quality		which may not be sufficient for diagnosing problems or quality
	monitoring. For example, it may be useful to distinguish between		monitoring. For example, it may be useful to distinguish between
	skipping to change at page 13, line 34 ¶		skipping to change at page 13, line 34 ¶
	This document focuses on listing the RTCP XR metrics defined in the		This document focuses on listing the RTCP XR metrics defined in the
	corresponding RTCP reporting extensions and do not give rise to any		corresponding RTCP reporting extensions and do not give rise to any
	new security vulnerabilities beyond those described in [RFC3611] and		new security vulnerabilities beyond those described in [RFC3611] and
	[RFC3792].		[RFC3792].
	The overall security considerations for RTP used in WebRTC		The overall security considerations for RTP used in WebRTC
	applicaitons is described in [I-D.ietf-rtcweb-rtp-usage] and [I-		applicaitons is described in [I-D.ietf-rtcweb-rtp-usage] and [I-
	D.ietf-rtcweb-security], which are also apply to this memo.		D.ietf-rtcweb-security], which are also apply to this memo.
	9. Acknowledgements		9. IANA Consideration
			This document requests no action by IANA.
			10. Acknowledgements
	The authors would like to thank Bernard Aboba, Harald Alvestrand, Al		The authors would like to thank Bernard Aboba, Harald Alvestrand, Al
	Morton, Colin Perkins, and Shida Schubert for their valuable comments		Morton, Colin Perkins, and Shida Schubert for their valuable comments
	and suggestions on earlier version of this document.		and suggestions on earlier version of this document.
	10. References		11. References
	10.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		11.1. Normative References
	Requirement Levels", BCP 14, RFC 2119,
	DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.
	[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.		[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
	Jacobson, "RTP: A Transport Protocol for Real-Time		Jacobson, "RTP: A Transport Protocol for Real-Time
	Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,		Applications", STD 64, RFC 3550, DOI 10.17487/RFC3550,
	July 2003, <http://www.rfc-editor.org/info/rfc3550>.		July 2003, <http://www.rfc-editor.org/info/rfc3550>.
	[RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,		[RFC3611] Friedman, T., Ed., Caceres, R., Ed., and A. Clark, Ed.,
	"RTP Control Protocol Extended Reports (RTCP XR)",		"RTP Control Protocol Extended Reports (RTCP XR)",
	RFC 3611, DOI 10.17487/RFC3611, November 2003,		RFC 3611, DOI 10.17487/RFC3611, November 2003,
	<http://www.rfc-editor.org/info/rfc3611>.		<http://www.rfc-editor.org/info/rfc3611>.
	skipping to change at page 15, line 22 ¶		skipping to change at page 15, line 21 ¶
	Extended Report (XR) for Post-Repair Loss Count Metrics",		Extended Report (XR) for Post-Repair Loss Count Metrics",
	RFC 7509, DOI 10.17487/RFC7509, May 2015,		RFC 7509, DOI 10.17487/RFC7509, May 2015,
	<http://www.rfc-editor.org/info/rfc7509>.		<http://www.rfc-editor.org/info/rfc7509>.
	[RFC8015] Singh, V., Perkins, C., Clark, A., and R. Huang, "RTP		[RFC8015] Singh, V., Perkins, C., Clark, A., and R. Huang, "RTP
	Control Protocol (RTCP) Extended Report (XR) Block for		Control Protocol (RTCP) Extended Report (XR) Block for
	Independent Reporting of Burst/Gap Discard Metrics",		Independent Reporting of Burst/Gap Discard Metrics",
	RFC 8015, DOI 10.17487/RFC8015, November 2016,		RFC 8015, DOI 10.17487/RFC8015, November 2016,
	<http://www.rfc-editor.org/info/rfc8015>.		<http://www.rfc-editor.org/info/rfc8015>.
	10.2. Informative References		11.2. Informative References
	[I-D.ietf-rtcweb-rtp-usage]		[I-D.ietf-rtcweb-rtp-usage]
	Perkins, C., Westerlund, M., and J. Ott, "Web Real-Time		Perkins, C., Westerlund, M., and J. Ott, "Web Real-Time
	Communication (WebRTC): Media Transport and Use of RTP",		Communication (WebRTC): Media Transport and Use of RTP",
	draft-ietf-rtcweb-rtp-usage-26 (work in progress), March		draft-ietf-rtcweb-rtp-usage-26 (work in progress), March
	2016.		2016.
	[I-D.ietf-rtcweb-security]		[I-D.ietf-rtcweb-security]
	Rescorla, E., "Security Considerations for WebRTC", draft-		Rescorla, E., "Security Considerations for WebRTC", draft-
	ietf-rtcweb-security-08 (work in progress), February 2015.		ietf-rtcweb-security-08 (work in progress), February 2015.
End of changes. 9 change blocks.
	17 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/