< draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-05.txt		draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06.txt >
	XR Block Working Group V. Singh		XR Block Working Group V. Singh
	Internet-Draft callstats.io		Internet-Draft callstats.io
	Intended status: Standards Track R. Huang		Intended status: Standards Track R. Huang
	Expires: May 31, 2017 R. Even		Expires: January 21, 2018 R. Even
	Huawei		Huawei
	D. Romascanu		D. Romascanu
	L. Deng		L. Deng
	China Mobile		China Mobile
	November 27, 2016		July 20, 2017
	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-05		draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06
	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 1, line 43 ¶		skipping to change at page 1, line 43 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	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 May 31, 2017.		This Internet-Draft will expire on January 21, 2018.
	Copyright Notice		Copyright Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2017 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 2, line 50 ¶		skipping to change at page 2, line 50 ¶
	6.7. Burst Packet Loss and Burst Discards . . . . . . . . . . 11		6.7. Burst Packet Loss and Burst Discards . . . . . . . . . . 11
	6.8. Burst/Gap Rates . . . . . . . . . . . . . . . . . . . . . 12		6.8. Burst/Gap Rates . . . . . . . . . . . . . . . . . . . . . 12
	6.9. Frame Impairment Metrics . . . . . . . . . . . . . . . . 12		6.9. Frame Impairment Metrics . . . . . . . . . . . . . . . . 12
	7. Adding new metrics to WebRTC Statistics API . . . . . . . . . 13		7. Adding new metrics to WebRTC Statistics API . . . . . . . . . 13
	8. Security Considerations . . . . . . . . . . . . . . . . . . . 13		8. Security Considerations . . . . . . . . . . . . . . . . . . . 13
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13		9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13		10. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
	10.1. Normative References . . . . . . . . . . . . . . . . . . 13		10.1. Normative References . . . . . . . . . . . . . . . . . . 13
	10.2. Informative References . . . . . . . . . . . . . . . . . 15		10.2. Informative References . . . . . . . . . . . . . . . . . 15
	Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16		Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 16
	A.1. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-04 . 16		A.1. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-05
	A.2. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-02,		and -06 . . . . . . . . . . . . . . . . . . . . . . . . . 16
			A.2. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-04 . 16
			A.3. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-02,
	-03 . . . . . . . . . . . . . . . . . . . . . . . . . . . 16		-03 . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
			A.4. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01 . 16
	A.3. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01 . 16		A.5. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-00 . 16
	A.4. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-00 . 16		A.6. changes in draft-huang-xrblock-rtcweb-rtcp-xr-metrics-04 16
	A.5. changes in draft-huang-xrblock-rtcweb-rtcp-xr-metrics-04 16		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
	1. Introduction		1. Introduction
	Web real-time communication (WebRTC) deployments are emerging and		Web real-time communication (WebRTC) deployments are emerging and
	applications need to be able to estimate the service quality. If		applications need to be able to estimate the service quality. If
	sufficient information (metrics or statistics) are provided to the		sufficient information (metrics or statistics) are provided to the
	applications, it can attempt to improve the media quality. [RFC7478]		applications, it can attempt to improve the media quality. [RFC7478]
	specifies a requirement for statistics:		specifies a requirement for statistics:
	F38 The browser must be able to collect statistics, related to the		F38 The browser must be able to collect statistics, related to the
	transport of audio and video between peers, needed to estimate		transport of audio and video between peers, needed to estimate
	quality of experience.		quality of experience.
	The WebRTC Stats API [W3C.WD-webrtc-stats-20160527] currently lists		The WebRTC Stats API [W3C.WD-webrtc-stats-20161214] currently lists
	metrics reported in the RTCP Sender and Receiver Report (SR/RR)		metrics reported in the RTCP Sender and Receiver Report (SR/RR)
	[RFC3550] to fulfill this requirement. However, the basic metrics		[RFC3550] to fulfill this requirement. However, the basic metrics
	from RTCP SR/RR are not sufficient for precise quality monitoring, or		from RTCP SR/RR are not sufficient for precise quality monitoring, or
	diagnosing potential issues.		diagnosing potential issues.
	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]. The		metrics for the WebRTC getStats() API [W3C.WD-webrtc-20161124]. The
	document also creates a registry containing identifiers from the		document also creates a registry containing identifiers from the
	metrics reported in the RTCP Sender, Receiver, and Extended Reports.		metrics reported in the RTCP Sender, Receiver, and Extended Reports.
	All identifiers proposed in this document are RECOMMENDED to be		All identifiers proposed in this document are RECOMMENDED to be
	skipping to change at page 7, line 29 ¶		skipping to change at page 7, line 31 ¶
	encoding to accurately communicate the status of each packet in the		encoding to accurately communicate the status of each packet in the
	interval to the other endpoint. [RFC3611], [RFC7097] define run-		interval to the other endpoint. [RFC3611], [RFC7097] define run-
	length encoding for lost and duplicate packets, and discarded		length encoding for lost and duplicate packets, and discarded
	packets, respectively.		packets, respectively.
	The WebRTC application could benefit from the additional information.		The WebRTC application could benefit from the additional information.
	If losses occur after discards, an endpoint may be able to correlate		If losses occur after discards, an endpoint may be able to correlate
	the two run length vectors to identify congestion-related losses,		the two run length vectors to identify congestion-related losses,
	i.e., a router queue became overloaded causing delays and then		i.e., a router queue became overloaded causing delays and then
	overflowed. If the losses are independent, it may indicate bit-error		overflowed. If the losses are independent, it may indicate bit-error
	corruption. For the WebRTC Stats API [W3C.WD-webrtc-stats-20160527],		corruption. For the WebRTC Stats API [W3C.WD-webrtc-stats-20161214],
	these types of metrics are not recommended for use due to the large		these types of metrics are not recommended for use due to the large
	amount of data and the computation involved.		amount of data and the computation involved.
	5.2. Application Impact Metrics		5.2. Application Impact Metrics
	5.2.1. Discard Octets Metric		5.2.1. Discard Octets Metric
	The metric reports the cumulative size of the packets discarded in		The metric reports the cumulative size of the packets discarded in
	the interval, it is complementary to number of discarded packets. An		the interval, it is complementary to number of discarded packets. An
	application measures sent octets and received octets to calculate		application measures sent octets and received octets to calculate
	skipping to change at page 13, line 42 ¶		skipping to change at page 13, line 42 ¶
	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		10. References
	10.1. Normative References		10.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/		Requirement Levels", BCP 14, RFC 2119,
	RFC2119, March 1997,		DOI 10.17487/RFC2119, March 1997,
	<http://www.rfc-editor.org/info/rfc2119>.		<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)", RFC		"RTP Control Protocol Extended Reports (RTCP XR)",
	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>.
	[RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R.
	Hakenberg, "RTP Retransmission Payload Format", RFC 4588,
	DOI 10.17487/RFC4588, July 2006,
	<http://www.rfc-editor.org/info/rfc4588>.
	[RFC5725] Begen, A., Hsu, D., and M. Lague, "Post-Repair Loss RLE		[RFC5725] Begen, A., Hsu, D., and M. Lague, "Post-Repair Loss RLE
	Report Block Type for RTP Control Protocol (RTCP) Extended		Report Block Type for RTP Control Protocol (RTCP) Extended
	Reports (XRs)", RFC 5725, DOI 10.17487/RFC5725, February		Reports (XRs)", RFC 5725, DOI 10.17487/RFC5725, February
	2010, <http://www.rfc-editor.org/info/rfc5725>.		2010, <http://www.rfc-editor.org/info/rfc5725>.
	[RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information		[RFC6776] Clark, A. and Q. Wu, "Measurement Identity and Information
	Reporting Using a Source Description (SDES) Item and an		Reporting Using a Source Description (SDES) Item and an
	RTCP Extended Report (XR) Block", RFC 6776, DOI 10.17487/		RTCP Extended Report (XR) Block", RFC 6776,
	RFC6776, October 2012,		DOI 10.17487/RFC6776, October 2012,
	<http://www.rfc-editor.org/info/rfc6776>.		<http://www.rfc-editor.org/info/rfc6776>.
	[RFC6958] Clark, A., Zhang, S., Zhao, J., and Q. Wu, Ed., "RTP		[RFC6958] Clark, A., Zhang, S., Zhao, J., and Q. Wu, Ed., "RTP
	Control Protocol (RTCP) Extended Report (XR) Block for		Control Protocol (RTCP) Extended Report (XR) Block for
	Burst/Gap Loss Metric Reporting", RFC 6958, DOI 10.17487/		Burst/Gap Loss Metric Reporting", RFC 6958,
	RFC6958, May 2013,		DOI 10.17487/RFC6958, May 2013,
	<http://www.rfc-editor.org/info/rfc6958>.		<http://www.rfc-editor.org/info/rfc6958>.
	[RFC7002] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol		[RFC7002] Clark, A., Zorn, G., and Q. Wu, "RTP Control Protocol
	(RTCP) Extended Report (XR) Block for Discard Count Metric		(RTCP) Extended Report (XR) Block for Discard Count Metric
	Reporting", RFC 7002, DOI 10.17487/RFC7002, September		Reporting", RFC 7002, DOI 10.17487/RFC7002, September
	2013, <http://www.rfc-editor.org/info/rfc7002>.		2013, <http://www.rfc-editor.org/info/rfc7002>.
	[RFC7003] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control		[RFC7003] Clark, A., Huang, R., and Q. Wu, Ed., "RTP Control
	Protocol (RTCP) Extended Report (XR) Block for Burst/Gap		Protocol (RTCP) Extended Report (XR) Block for Burst/Gap
	Discard Metric Reporting", RFC 7003, DOI 10.17487/RFC7003,		Discard Metric Reporting", RFC 7003, DOI 10.17487/RFC7003,
	September 2013, <http://www.rfc-editor.org/info/rfc7003>.		September 2013, <http://www.rfc-editor.org/info/rfc7003>.
	[RFC7004] Zorn, G., Schott, R., Wu, Q., Ed., and R. Huang, "RTP		[RFC7004] Zorn, G., Schott, R., Wu, Q., Ed., and R. Huang, "RTP
	Control Protocol (RTCP) Extended Report (XR) Blocks for		Control Protocol (RTCP) Extended Report (XR) Blocks for
	Summary Statistics Metrics Reporting", RFC 7004, DOI		Summary Statistics Metrics Reporting", RFC 7004,
	10.17487/RFC7004, September 2013,		DOI 10.17487/RFC7004, September 2013,
	<http://www.rfc-editor.org/info/rfc7004>.		<http://www.rfc-editor.org/info/rfc7004>.
	[RFC7005] Clark, A., Singh, V., and Q. Wu, "RTP Control Protocol		[RFC7005] Clark, A., Singh, V., and Q. Wu, "RTP Control Protocol
	(RTCP) Extended Report (XR) Block for De-Jitter Buffer		(RTCP) Extended Report (XR) Block for De-Jitter Buffer
	Metric Reporting", RFC 7005, DOI 10.17487/RFC7005,		Metric Reporting", RFC 7005, DOI 10.17487/RFC7005,
	September 2013, <http://www.rfc-editor.org/info/rfc7005>.		September 2013, <http://www.rfc-editor.org/info/rfc7005>.
	[RFC7097] Ott, J., Singh, V., Ed., and I. Curcio, "RTP Control		[RFC7097] Ott, J., Singh, V., Ed., and I. Curcio, "RTP Control
	Protocol (RTCP) Extended Report (XR) for RLE of Discarded		Protocol (RTCP) Extended Report (XR) for RLE of Discarded
	Packets", RFC 7097, DOI 10.17487/RFC7097, January 2014,		Packets", RFC 7097, DOI 10.17487/RFC7097, January 2014,
	skipping to change at page 15, line 22 ¶		skipping to change at page 15, line 17 ¶
	Discarded Metric", RFC 7243, DOI 10.17487/RFC7243, May		Discarded Metric", RFC 7243, DOI 10.17487/RFC7243, May
	2014, <http://www.rfc-editor.org/info/rfc7243>.		2014, <http://www.rfc-editor.org/info/rfc7243>.
	[RFC7509] Huang, R. and V. Singh, "RTP Control Protocol (RTCP)		[RFC7509] Huang, R. and V. Singh, "RTP Control Protocol (RTCP)
	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", RFC		Independent Reporting of Burst/Gap Discard Metrics",
	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		10.2. Informative References
			[I-D.ietf-rtcweb-rtp-usage]
			Perkins, C., Westerlund, M., and J. Ott, "Web Real-Time
			Communication (WebRTC): Media Transport and Use of RTP",
			draft-ietf-rtcweb-rtp-usage-26 (work in progress), March
			2016.
			[I-D.ietf-rtcweb-security]
			Rescorla, E., "Security Considerations for WebRTC", draft-
			ietf-rtcweb-security-08 (work in progress), February 2015.
	[RFC7478] Holmberg, C., Hakansson, S., and G. Eriksson, "Web Real-		[RFC7478] Holmberg, C., Hakansson, S., and G. Eriksson, "Web Real-
	Time Communication Use Cases and Requirements", RFC 7478,		Time Communication Use Cases and Requirements", RFC 7478,
	DOI 10.17487/RFC7478, March 2015,		DOI 10.17487/RFC7478, March 2015,
	<http://www.rfc-editor.org/info/rfc7478>.		<http://www.rfc-editor.org/info/rfc7478>.
	[W3C.WD-webrtc-20161124]		[W3C.WD-webrtc-20161124]
	Sporny, M. and D. Longley, "WebRTC 1.0: Real-time		Sporny, M. and D. Longley, "WebRTC 1.0: Real-time
	Communication Between Browsers", World Wide Web Consortium		Communication Between Browsers", World Wide Web Consortium
	WD WD-webrtc-20161124, November 2016,		WD WD-webrtc-20161124, November 2016,
	<https://www.w3.org/TR/2016/WD-webrtc-20161124>.		<https://www.w3.org/TR/2016/WD-webrtc-20161124>.
	[I-D.ietf-rtcweb-rtp-usage]		[W3C.WD-webrtc-stats-20161214]
	Perkins, C., Westerlund, M., and J. Ott, "Web Real-Time
	Communication (WebRTC): Media Transport and Use of RTP",
	draft-ietf-rtcweb-rtp-usage-26 (work in progress), March
	2016.
	[I-D.ietf-rtcweb-security]
	Rescorla, E., "Security Considerations for WebRTC", draft-
	ietf-rtcweb-security-08 (work in progress), February 2015.
	[W3C.WD-webrtc-stats-20160527]
	Alvestrand, H. and V. Singh, "Identifiers for		Alvestrand, H. and V. Singh, "Identifiers for
	WebRTC&#039;s Statistics API", World Wide Web Consortium		WebRTC&#039;s Statistics API", World Wide Web Consortium
	WD WD-webrtc-stats-20160527, May 2016,		WD WD-webrtc-stats-20161214, December 2016,
	<http://www.w3.org/TR/2016/WD-webrtc-stats-20160527>.		<https://www.w3.org/TR/2016/WD-webrtc-stats-20161214>.
	[RFC6390] Clark, A. and B. Claise, "Guidelines for Considering New
	Performance Metric Development", BCP 170, RFC 6390, DOI
	10.17487/RFC6390, October 2011,
	<http://www.rfc-editor.org/info/rfc6390>.
	Appendix A. Change Log		Appendix A. Change Log
	Note to the RFC-Editor: please remove this section prior to		Note to the RFC-Editor: please remove this section prior to
	publication as an RFC.		publication as an RFC.
	A.1. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-04		A.1. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-05 and -06
			o Keep alive the document! Keeping it alive.
			A.2. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-04
	o Removed IANA registry.		o Removed IANA registry.
	A.2. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-02, -03		A.3. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-02, -03
	o Keep-alive versions, updates to references.		o Keep-alive versions, updates to references.
	A.3. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01		A.4. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-01
	o Create new registry for WebRTC media metrics.		o Create new registry for WebRTC media metrics.
	o Using camelCase instead of TitleCase for identifier names.		o Using camelCase instead of TitleCase for identifier names.
	o Imported RTCP SR and RR metrics from the registry in alvestrand-		o Imported RTCP SR and RR metrics from the registry in alvestrand-
	rtcweb-stats-registry.		rtcweb-stats-registry.
	o Added Burst/Gap rate metrics.		o Added Burst/Gap rate metrics.
	o Added Frames sent and received metrics.		o Added Frames sent and received metrics.
	A.4. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-00		A.5. changes in draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-00
	o Submitted as WG Draft.		o Submitted as WG Draft.
	A.5. changes in draft-huang-xrblock-rtcweb-rtcp-xr-metrics-04		A.6. changes in draft-huang-xrblock-rtcweb-rtcp-xr-metrics-04
	o Addressed comments from the London IETF meeting:		o Addressed comments from the London IETF meeting:
	o Removed ECN metrics.		o Removed ECN metrics.
	o Merged draft-singh-xrblock-webrtc-additional-stats-01		o Merged draft-singh-xrblock-webrtc-additional-stats-01
	Authors' Addresses		Authors' Addresses
	Varun Singh		Varun Singh
	CALLSTATS I/O Oy		CALLSTATS I/O Oy
	Runeberginkatu 4c A 4		Annankatu 31-33 C 42
	Helsinki 00100		Helsinki 00100
	Finland		Finland
	Email: varun@callstats.io		Email: varun@callstats.io
	URI: https://www.callstats.io/about		URI: https://www.callstats.io/about
	Rachel Huang		Rachel Huang
	Huawei		Huawei
	101 Software Avenue, Yuhua District		101 Software Avenue, Yuhua District
	Nanjing, CN 210012		Nanjing, CN 210012
End of changes. 26 change blocks.
	56 lines changed or deleted		50 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/