RFC 6035: Session Initiation Protocol Event Package for Voice Quality Reporting
In plain English — editorial summary, not part of the RFC
This document defines a Session Initiation Protocol (SIP) event package that enables the collection and reporting of metrics that measure the quality for Voice over Internet Protocol (VoIP) sessions. Voice call quality information derived from RTP Control Protocol Extended Reports (RTCP-XR) and call information from SIP is conveyed from a User Agent (UA) in a session, known as a reporter, to a third party, known as a collector. A registration for the application/ vq-rtcpxr media type is also included. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6035
- Published
- November 2010
- Authors
- A. Pendleton; A. Clark; A. Johnston; H. Sinnreich
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
- RFC 5866Diameter Quality-of-Service ApplicationCurrent
May 2010
- RFC 7090Public Safety Answering Point (PSAP) CallbackCurrent
April 2014
- RFC 8866SDP: Session Description ProtocolCurrent
January 2021
- RFC 6080A Framework for Session Initiation Protocol User Agent Profile DeliveryCurrent
March 2011
- RFC 5954Essential Correction for IPv6 ABNF and URI Comparison in RFC 3261Current
August 2010
- RFC 5876Updates to Asserted Identity in the Session Initiation Protocol (SIP)Current
April 2010
- RFC 5874An Extensible Markup Language (XML) Document Format for Indicating a Change in XML Configuration Access Protocol (XCAP) ResourcesCurrent
May 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?