SIPPING Working Group A. Johnston
Internet-Draft MCI
Expires: April 17, 2006 H. Sinnreich
Pulver
A. Clark
Telchemy Incorporated
A. Pendleton
Nortel Networks
October 14, 2005
SIP Service Quality Reporting Event
draft-johnston-sipping-rtcp-summary-08
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on April 17, 2006.
Copyright Notice
Copyright (C) The Internet Society (2005).
Abstract
This document defines a SIP event package that enables the collection
and reporting of metrics that measure the quality for VoIP sessions
using RTP [3] as their transport. The definitions of the metrics
Johnston, et al. Expires April 17, 2006 [Page 1]
Internet-Draft SIP Event for Service Quality Reporting October 2005
used in the event package are based on RTCP Extended Reports [4] and
RTCP [3].
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. SIP Events Approach . . . . . . . . . . . . . . . . . . . . . 3
3. Use of PUBLISH Method . . . . . . . . . . . . . . . . . . . . 3
4. Event Package Formal Definition . . . . . . . . . . . . . . . 4
4.1. Event Package Name . . . . . . . . . . . . . . . . . . . . 4
4.2. Event Package Parameters . . . . . . . . . . . . . . . . . 4
4.3. SUBSCRIBE Bodies . . . . . . . . . . . . . . . . . . . . . 4
4.4. Subscription Duration . . . . . . . . . . . . . . . . . . 4
4.5. NOTIFY Bodies . . . . . . . . . . . . . . . . . . . . . . 4
4.6. Voice Quality Event Syntax . . . . . . . . . . . . . . . . 5
4.7. Message Flow and Syntax Examples . . . . . . . . . . . . . 11
4.7.1. End of Session Report using PUBLISH . . . . . . . . . 12
4.7.2. Mid Session Threshold Violation using PUBLISH . . . . 13
4.7.3. End of Session Report using NOTIFY . . . . . . . . . . 15
4.7.4. Mid Session Threshold Violation using NOTIFY . . . . . 17
4.8. IANA Considerations . . . . . . . . . . . . . . . . . . . 20
4.8.1. SIP Event Package Registration . . . . . . . . . . . . 20
4.8.2. application/vq-rtcp-xr MIME Registration . . . . . . . 21
4.9. Security Considerations . . . . . . . . . . . . . . . . . 21
4.10. Updates since -07 . . . . . . . . . . . . . . . . . . . . 21
4.11. Updates since -06 . . . . . . . . . . . . . . . . . . . . 22
4.12. Updates since -04 . . . . . . . . . . . . . . . . . . . . 22
4.13. Updates since -03 . . . . . . . . . . . . . . . . . . . . 22
4.14. Contributors . . . . . . . . . . . . . . . . . . . . . . . 23
5. Informative References . . . . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 24
Intellectual Property and Copyright Statements . . . . . . . . . . 25
Johnston, et al. Expires April 17, 2006 [Page 2]
Internet-Draft SIP Event for Service Quality Reporting October 2005
1. Introduction
This document defines a new SIP event package, vq-rtcpxr, and a new
MIME type, application/vq-rtcpxr, that enable the collection and
reporting of metrics that measure quality for RTP [3] sessions. The
definitions of the metrics used in the event package are based on
RTCP Extended Reports [4] and RTCP [3]. Monitoring of voice quality
is believed to be the highest priority for usage of this mechanism
and as such, the metrics in the event package are largely tailored
for voice quality measurement. However, the event package defined
herein is designed to be extensible. The event package explicitly
provides parameters for reporting both the local and remote versions
of these statistics. Note that in multi-party calls, multiple
reports will need to be generated either one for each endpoint or one
for each session. Configuration of usage of the event package is not
covered in this document. The event package can be used either with
the SUBSCRIBE/NOTIFY methods or the PUBLISH method. Message flow
examples for both mechanims are provided in this document.
2. SIP Events Approach
This document defines a new SIP events package [6]. The intended
methods to use for this event are PUBLISH and SUBSCRIBE/NOTIFY. A
SIP UA can provide voice quality reports using either of these
methods to an entity which can make the information available to
other applications.
3. Use of PUBLISH Method
A SIP UA that supports this specification may send the service
quality metric reports using the PUBLISH method. An application
wishing to access this performance data maintains a State Agent for
the vq-rtcpxr event package. The Request-URI of the PUBLISH method
is set to the address of the resource for the VoIP application. The
PUBLISH message is sent to the normal default outbound proxy server
of the SIP UA or could be sent to other interested parties.
The use of PUBLISH by this event is unique in that it does not
require a soft or hard state to be maintained by either the Event
Publication Agent (EPA) or the Event State Compositor (ESC).
Futhermore the information that is presented by the vq-rtcpxr event
in a PUBLISH request is not expected to have an expiration, rather,
the information is associated with the timestamps in the event
itself. The primary intention of using PUBLISH for this event is
reduction of transaction processing.
Johnston, et al. Expires April 17, 2006 [Page 3]
Internet-Draft SIP Event for Service Quality Reporting October 2005
A concern over the usage of the PUBLISH method is potential
overloading of servers receiving the events, particularly in the
threshold reporting model. There are many approaches to solving this
type of problem, but clearly the EPA's needs to adhere to some
guidelines to reduce the probability of causing this overload
condition. Some suggested solutions are: a) limit sending of one
threshold report per metric per session b) limit sending of one
threshold report per session regardless of the metric c) limit
sending a new threshold report to when a metric state has been
sustained for a reasonable amount of time such as 20-30 seconds.
4. Event Package Formal Definition
4.1. Event Package Name
This document defines a SIP Event Package as defined in RFC 3265 [2].
The event-package token name for this package is:
"vq-rtcpxr"
4.2. Event Package Parameters
No event package parameters are defined.
4.3. SUBSCRIBE Bodies
No SUBSCRIBE bodies are described by this specification.
4.4. Subscription Duration
Subscriptions to this event package MAY range from minutes to weeks.
Subscriptions in hours or days are more typical and are RECOMMENDED.
The default subscription duration for this event package is one hour.
4.5. NOTIFY Bodies
There are three notify bodies: a session report, an interval session
report, and a alert report.
The session report is used for end of session reporting. This can be
generated when a voice media session terminates or when a media
change occurs, such as a codec change or a session forks. This
report is intended to allow cumulative metric reporting. The session
reports will populate the metrics with values that are measured over
the interval explicitly defined by the "start" and "stop" timestamps.
The interval report is used for periodic or interval reporting. This
Johnston, et al. Expires April 17, 2006 [Page 4]
Internet-Draft SIP Event for Service Quality Reporting October 2005
report is intended to capture short duration metric reporting.
Interval reports will populate the metrics with values that are
measured over the interval explicitly defined by the "start" and
"stop" timestamps.
The threshold report is used when voice quality degrades during a
session. The session report parameters are also included in the
alert report to provide all of the necessary diagnostic information.
Like the interval report, the metrics in the threshold reports will
be populated with values that are measured over the interval
explicitly defined by the "start" and "stop" timestamps.
This specification defines a new MIME type application/vq-rtcpxr
which is a text encoding of the RTCP and RTCP-XR statistics, along
with some additional metrics and correlation information.
4.6. Voice Quality Event Syntax
This section describes the syntax extensions required for event
publication in SIP. The formal syntax definitions described in this
section are expressed in the Augmented BNF format used in SIP [2],
and contains references to elements defined therein. Note that most
of the parameters are optional. In practice, most implementations
will send a subset of the parameters. It is not the intention of
this document to define what parameters may or may not be useful for
monitoring the quality of a voice session, but to enable reporting of
voice quality. As such, the syntax allows the implementer to choose
which metrics are most appropriate for their solution. Additionally,
the authors recognize that implementers may need to add new parameter
lines to the reports and new metrics to the existing parameter lines.
The extension tokens are intended to fulfill this need.
VoiceQualityReportEvent = AlertReport / SessionReport / IntervalReport
SessionReport = "VQSessionReport" CLRF
LocalMetrics [CLRF RemoteMetrics]
[DialogID]
IntervalReport = "VQIntervalReport" CLRF
LocalMetrics [CLRF RemoteMetrics]
[DialogID]
LocalMetrics = "LocalMetrics" COLON Metrics
RemoteMetrics = "RemoteMetrics" COLON Metrics
AlertReport = "VQAlertReport" COLON
Johnston, et al. Expires April 17, 2006 [Page 5]
Internet-Draft SIP Event for Service Quality Reporting October 2005
MetricType WSP Severity WSP Direction CLRF
"Metrics:" CLRF
Metrics
[CLRF "OtherDir Metrics:" CLRF Metrics]
Metrics = TimeStamps CLRF
SessionDescription CLRF
CallID CLRF
LocalAddr CRLF
RemoteAddr CRLF
[JitterBuffer CRLF]
[PacketLoss CRLF]
[BurstGapLoss CLRF]
[Delay CLRF]
[Signal CLRF]
[QualityScores CLRF]
*[Extension CLRF]
; timestamps are measured inaccordance with RFC 3611
TimeStamps = "Timestamps" COLON StartTime WSP StopTime
StartTime = "START" EQUAL word
StopTime = "STOP" EQUAL word
; SessionDescription provides a shortened version of the
; session SDP but contains only the relevant parameters
SessionDescription = "SessionDesc" COLON
[PayloadType WSP]
[PayloadDesc WSP]
[SampleRate WSP]
[FrameDuration WSP]
[FrameOctets WSP]
[FramesPerPacket WSP]
[FmtpOptions WSP]
[PacketLossConcealment WSP]
[SilenceSuppressionState]
*[WSP Extension]
; PayloadType provides the PT parameter used in the RTP packets
; i.e. the codec used for decoding received RTP packets
; It is recommended that IANA registered values are used where possible.
PayloadType = "PT" EQUAL (1*3DIGIT)
; PayloadDesc provides a text description of the codec in PayloadType
; It is recommended that IANA register names are used where possible.
PayloadDesc = "PD" EQUAL word
Johnston, et al. Expires April 17, 2006 [Page 6]
Internet-Draft SIP Event for Service Quality Reporting October 2005
; SampleRate provides the rate at which voice was sampled
; in the case of narrowband codecs, the value will typically be 8000
SampleRate = "SR" EQUAL (1*5DIGIT)
; FrameDuration can be combined with the FramesPerPacket to determine
; the packetization rate
FrameDuration = "FD" EQUAL (1*3DIGIT)
; FrameOctets provides the number of octets in each frame
; Used where FrameDuration is not available
FrameOctets = "FO" EQUAL (1*4DIGIT)
; FramesPerPacket provides the number of frames in each RTP packet
FramesPerPacket = "FPP" EQUAL (1*2DIGIT)
; FMTP options from SDP. Note that the parameter is deliniated
; by " " to avoid parsing issues in transitioning between SDP and
; SIP parsing
FmtpOptions = "FMTP" EQUAL "word-plus"
; PacketLossConcealment indicates whether a PLC algorithm was
; or is being used for the session. The values follow the same
; numbering convention as RFC 3611. For more details,
; please refer to RFC 3611, RTCP XR
; 0 - unspecified
; 1 - disabled
; 2 - enhanced
; 3 - standard
PacketLossConcealment = "PLC" EQUAL ("0" / "1" / "2" / "3")
; SilenceSuppressionState indicates whether silence suppression,
; also known as Voice Activity Detection (VAD) is enabled.
SilenceSuppressionState = "SSUP" EQUAL ("on" / "off")
; CallId provides the call id from the SIP header
CallID = "CID" EQUAL word [ "@" word ]
; LocalAddr provides the IP address, port and ssrc for the
; session from the perspective of the endpoint/UA which is
; sending the report
LocalAddr = "LocalAddr" COLON IPAddress WSP Port WSP Ssrc
; RemoteAddr provides the IP address, port and ssrc for the
; session from the perspective of the peer of the endpoint/UA
; that is sending the report
RemoteAddr = "RemoteAddr" COLON IPAddress WSP Port WSP Ssrc
IPAddress = "IP" EQUAL IPv6address / IPv4address
Johnston, et al. Expires April 17, 2006 [Page 7]
Internet-Draft SIP Event for Service Quality Reporting October 2005
Port = "PORT" EQUAL 1*DIGIT
Ssrc = "SSRC" EQUAL text / notAvail
JitterBuffer = "JitterBuffer" COLON
[JitterBufferAdaptive WSP]
[JitterBufferRate WSP]
[JitterBufferNominal WSP]
[JitterBufferMax WSP]
[JitterBufferAbsMax]
*[WSP Extension]
; JitterBufferAdaptive indicates whether the jitter buffer in the
; endpoint is adaptive, static, or unknown.
; The values follow the same numbering convention as RFC 3611.
; For more details, please refer to that document.
; 0 - unknown
; 1 - reserved
; 2 - non-adaptive
; 3 - adaptive
JitterBufferAdaptive = "JBA" EQUAL ("0" / "1" / "2" / "3")
; JitterBuffer metric definitions are provided in RTCP XR, RFC 3611
JitterBufferRate = "JBR" EQUAL (1*2DIGIT) ;0-15
JitterBufferNominal = "JBN" EQUAL (1*5DIGIT) ;0-65535
JitterBufferMax = "JBM" EQUAL (1*5DIGIT) ;0-65535
JitterBufferAbsMax = "JBA" EQUAL (1*5DIGIT) ;0-65535
; PacketLoss metrics definitions are provided in RTCP XR, RFC 3611
PacketLoss = "PacketLoss" COLON
[NetworkPacketLossRate WSP]
[JitterBufferDiscardRate]
*[WSP Extension]
NetworkPacketLossRate
= "NLR" EQUAL (1*3(DIGIT) ["." 1*2(DIGIT)]) ;percentage
JitterBufferDiscardRate
= "JDR" EQUAL (1*3(DIGIT) ["." 1*2(DIGIT)]) ;percentage
; BurstGapLoss metrics definitions are provided in RTCP XR, RFC 3611
BurstGapLoss = "BurstGapLoss" COLON
[BurstLossDensity WSP]
[BurstDuration WSP]
[GapLossDensity WSP]
[GapDuration WSP]
[MinimumGapThreshold]
*[WSP Extension]
Johnston, et al. Expires April 17, 2006 [Page 8]
Internet-Draft SIP Event for Service Quality Reporting October 2005
BurstLossDensity
= "BLD" EQUAL (1*3(DIGIT) ["." 1*2(DIGIT)]) ;percentage
BurstDuration
= "BD" EQUAL (1*8DIGIT) ;0-3,600,000 -- milliseconds
GapLossDensity
= "GLD" EQUAL (1*3(DIGIT) ["." 1*2(DIGIT)]) ;percentage
GapDuration
= "GD" EQUAL (1*8DIGIT) ;0-3,600,000 -- milliseconds
MinimumGapThreshold
= "GMIN" EQUAL (1*3DIGIT) ;1-255
Delay = "Delay" COLON
[RoundTripDelay WSP]
[EndSystemDelay WSP]
[OneWayDelay WSP]
[InterarrivalJitter WSP]
[MeanAbsoluteJitter]
*[WSP Extension]
; RoundTripDelay is recommended to be measured as defined in
; RTCP, RFC 3550.
RoundTripDelay = "RTD" EQUAL (1*5DIGIT) ;0-65535
; EndSystemDelay metric is provided in RTCP XR, RFC 3611
EndSystemDelay = "ESD" EQUAL (1*5DIGIT) ;0-65535
; OneWayDelay is recommended to be measured according to
; recommendations provided by the IPPM working group but may be
; based on alternative measurement recommendations
OneWayDelay = "OWD" EQUAL (1*5DIGIT) ;0-65535
; Interarrival Jitter is recommended to be measured as defined
; in RTCP, RFC 3550, but may be based on alternatives
InterarrivalJitter = "IAJ" EQUAL (1*5DIGIT) ;0-65535
; Mean Absolute Jitter is recommended to be measured as defined
; by ITU-T G.1020 where it is known as MAPDV
MeanAbsoluteJitter = "MAJ" EQUAL (1*5DIGIT)
; Signal metrics definitions are provided in RTCP XR, RFC 3611
Signal = "Signal" COLON
[SignalLevel WSP]
[NoiseLevel WSP]
[ResidualEchoReturnLoss]
*[WSP Extension]
Johnston, et al. Expires April 17, 2006 [Page 9]
Internet-Draft SIP Event for Service Quality Reporting October 2005
SignalLevel = "SL" EQUAL (["-"] 1*2DIGIT)
NoiseLevel = "NL" EQUAL (["-"] 1*2DIGIT)
ResidualEchoReturnLoss = "RERL" EQUAL (1*3DIGIT)
; Voice Quality estimation metrics
; The definition of these metrics are provided in RTCP XR, RFC 3611, and
; the new High Resolution proposal, RTCP XR bis.
; Each quality estmiate has an associated, optional algorithm parameter.
; This field permits the implementation to use a variety of different
; calculation methods for each type of metric
QualityEstimates = "QualityEst" COLON
[ListeningQualityR WSP]
[RLQEstAlg WSP]
[ConversationalQualityR WSP]
[RCQEstAlg WSP]
[ExternalR-In WSP]
[ExtRInEstAlg WSP]
[ExternalR-Out WSP]
[ExtROutEstAlg WSP]
[MOS-LQ WSP]
[MOSLQEstAlg WSP]
[MOS-CQ WSP]
[MOSCQEstAlg WSP]
[QoEEstAlg]
*[WSP Extension]
ListeningQualityR = "RLQ" EQUAL (1*3DIGIT) ; 0 - 120
RLQEstAlg = "RLQEstAlg" EQUAL word ; "PESQ", "G.107", or other
ConversationalQualityR = "RCQ" EQUAL *1*3DIGIT) ; 0 - 120
RCQEstAlg = "RCQEstAlg" EQUAL word ; "PESQ", "G.107", or other
; ExternalR-In is measured by the local endpoint for incoming
; connection on "other" side of this endpoint
; e.g. PhoneA <---> Bridge <----> Phone B
; ListeningQualityR = quality for PhoneA ----> Bridge path
; ExternalR-In = quality for Bridge <---- PhoneB path
ExternalR-In = "EXTRI" EQUAL (1*3DIGIT) ; 0 - 120
ExtRInEstAlg = "ExtRIEstAlg" EQUAL word ; "PESQ", "G.107", or other
; ExternalR-Out is copied from RTCP XR message received from the
; remote endpoint on "other" side of this endpoint
; e.g. PhoneA <---> Bridge <----> Phone B
; ExternalR-Out = quality for Bridge -----> PhoneB path
Johnston, et al. Expires April 17, 2006 [Page 10]
Internet-Draft SIP Event for Service Quality Reporting October 2005
ExternalR-Out = "EXTRO" EQUAL (1*3DIGIT) ; 0 - 120
ExtRInEstAlg = "ExtROEstAlg" EQUAL word ; "PESQ", "G.107", or other
MOS-LQ = "MOSLQ" EQUAL (DIGIT ["." 1*2DIGIT]) ; 0.0 - 4.9
MOSLQEstAlg = "MOSLQEstAlg" EQUAL word ; "PESQ", "G.107", or other
MOS-CQ = "MOSCQ" EQUAL (DIGIT ["." 1*2DIGIT] ; 0.0 - 4.9
MOSCQEstAlg = "MOSCQEstAlg" EQUAL word ; "PESQ", "G.107", or other
; alternative to the separate estimation algorithms where the same algorithm
; is used for all of the measurements
QoEEstAlg = "QoEEstAlg'
DialogID = "DialogID" COLON callid *(SEMI did-parm)
did-parm = to-tag / from-tag / generic-param
callid = *(token)
to-tag = "to-tag" EQUAL token
from-tag = "from-tag" EQUAL token
; MetricType provides the metric on which a notification of
; threshold violation was based. The more commonly used metrics
; for alerting purposes are included here explicitly and the
; token parameter allows for extension
MetricType = "Type" EQUAL "RLQ" / "RCQ" / "EXTR" /
"MOSLQ" / "MOSCQ" /
"BD" / "NLR" / "JDR" /
"RTD" / "ESD" / "IAD" /
"RERL" / Extension
Direction = "Dir" EQUAL "local" / "remote"
Severity = "Severity" EQUAL "Warning" / "Critical" /
"Clear"
Extension = word
word-plus = 1*(alphanum / "-" / "." / "!" / "%" / "*" /
"_" / "+" / "`" / "'" / "~" /
"(" / ")" / "<" / ">" / ":" /
"\" / "/" / "[" / "]" / "?" /
"{" / "}" / "=" / " ")
4.7. Message Flow and Syntax Examples
This section shows a number of message flow examples showing how the
event package works.
Johnston, et al. Expires April 17, 2006 [Page 11]
Internet-Draft SIP Event for Service Quality Reporting October 2005
4.7.1. End of Session Report using PUBLISH
Alice Proxy/Registrar Collector Bob
| | | |
| | | |
| REGISTER Allow-Event:vq-rtcpxr F1 | |
|------------------->| | |
| 200 OK F2 | | |
|<-------------------| | |
| INVITE F3 | | |
|------------------->| | |
| | INVITE F4 | |
| |---------------------------------------->|
| | 200 OK F5 | |
| |<----------------------------------------|
| 200 OK F6 | | |
|<-------------------| | |
| ACK F7 | | |
|------------------->| | |
| | ACK F8 | |
| |---------------------------------------->|
| RTP | | |
|<============================================================>|
| RTCP | | |
|<============================================================>|
| | | |
| BYE F9 | | |
|------------------->| BYE F10 | |
| |---------------------------------------->|
| | 200 OK F11 | |
| |<----------------------------------------|
| 200 OK F12 | | |
|<-------------------| | |
| PUBLISH Event:vq-rtcpxr F13 | |
|------------------->| | |
| | PUBLISH Event:vq-rtcpxr F14 |
| |------------------->| |
| | 200 OK F15 | |
| |<-------------------| |
| 200 OK F16 | | |
|<-------------------| | |
Figure 1. End of session report sent after session termination.
In the message flow depicted in Figure 1, the following message format
Johnston, et al. Expires April 17, 2006 [Page 12]
Internet-Draft SIP Event for Service Quality Reporting October 2005
is sent in F13. Note that both local and remote metrics are provided.
PUBLISH sip:collector@example.com SIP/2.0
Via: SIP/2.0/UDP pc22.example.com;branch=z9hG4bK3343d7
Max-Forwards: 70
To: <sip:proxy@example.com>
From: Alice <sip:alice@example.com>;tag=a3343df32
Call-ID: 1890463548@alice.chicago.com
CSeq: 4331 PUBLISH
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
SUBSCRIBE, NOTIFY
Event: vq-rtcpxr
Accept: application/sdp, message/sipfrag
Content-Type: application/vq-rtcpxr
Content-Length: ...
VQSessionReport
LocalMetrics:
TimeStamps:START=10012004.18.23.43 STOP=10012004.18.26.02
SessionDesc:PT=18 PD=G729 SR=8000 FD=20 FPP=2 FMTP="annexb=no" PLC=3 SSUP=on
CallID:1890463548@alice.uac.chicago.com
LocalAddr:IP=10.10.1.100 PORT=5000 SSRC=fjuekdn393k
RemoteAddr:IP=11.1.1.150 PORT=5002 SSRC=r3k3k99weid
JitterBuffer:JBA=3 JBR=2 JBN=40 JBM=80 JBA=120
PacketLoss:NLR=5.0 JDR=2.0
BurstGapLoss:BLD=0 BD=0 GLD=2.0 GD=500
Delay:RTD=200 ESD=140 IAD=2
Signal:SL=2 NL=10 RERL=14
QualityEst:RLQ=90 RCQ=85 EXTRI=90 MOSLQ=3.4 MOSCQ=3.3 QoEEstAlg=G.107
RemoteMetrics:
TimeStamps:START=10012004.18.23.43 STOP=10012004.18.26.02
SessionDesc:PT=18 PD=G729 SR=8000 FD=20 FPP=2 FMTP="annexb=no" PLC=3 SSUP=on
CallID:1890463548@alice.uac.chicago.com
LocalAddr:IP=11.1.1.150 PORT=5002 SSRC=r3k3k99weid
RemoteAddr:IP=10.10.1.100 PORT=5000 SSRC=fjuekdn393k
JitterBuffer:JBA=3 JBR=2 JBN=40 JBM=80 JBA=120
PacketLoss:NLR=5.0 JDR=2.0
BurstGapLoss:BLD=0 BD=0 GLD=2.0 GD=500
Delay:RTD=200 ESD=140 IAJ=2
Signal:SL=2 NL=10 RERL=0
QualityEst:RLQ=90 RCQ=85 MOSLQ=3.4 MOSCQ=3.3 QoEEstAlg=G.107
DialogID:38419823470834;to-tag=8472761;from-tag=9123dh311
4.7.2. Mid Session Threshold Violation using PUBLISH
Alice Proxy/Registrar Collector Bob
Johnston, et al. Expires April 17, 2006 [Page 13]
Internet-Draft SIP Event for Service Quality Reporting October 2005
| | | |
| INVITE F1 | | |
|------------------->| | |
| | INVITE F2 | |
| |---------------------------------------->|
| | 200 OK F3 | |
| |<----------------------------------------|
| 200 OK F4 | | |
|<-------------------| | |
| ACK F5 | | |
|------------------->| | |
| | ACK F6 | |
| |---------------------------------------->|
| RTP | | |
|<============================================================>|
| RTCP | | |
|<============================================================>|
| PUBLISH Event:vq-rtcpxr F7 | |
|------------------->| | |
| | PUBLISH Event:vq-rtcpxr F8 |
| |------------------->| |
| | 200 OK F9 | |
| |<-------------------| |
| 200 OK F10 | | |
|<-------------------| | |
| | | |
| BYE F12 | | |
|------------------->| BYE F13 | |
| |---------------------------------------->|
| | 200 OK F14 | |
| |<----------------------------------------|
| 200 OK F15 | | |
|<-------------------| | |
Figure 2. Mid-session threshold report message flow
In the message flow depicted in Figure 2, the following message format
is sent in F7:
PUBLISH sip:collector@chicago.example.com SIP/2.0
Via: SIP/2.0/UDP pc22.example.com;branch=z9hG4bK3343d7
Max-Forwards: 70
To: <sip:collector@example.com>
From: Alice <sip:alice@example.com>;tag=a3343df32
Call-ID: 1890463548@alice.chicago.com
CSeq: 4321 PUBLISH
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
Johnston, et al. Expires April 17, 2006 [Page 14]
Internet-Draft SIP Event for Service Quality Reporting October 2005
SUBSCRIBE, NOTIFY
Event: vq-rtcpxr
Accept: application/sdp, message/sipfrag
Content-Type: application/vq-rtcpxr
Content-Length: ...
VQAlertReport: Type=RLQ Severity=Warning Dir=local
Metrics:
TimeStamps:START=10012004.19.01.04 STOP=10012004.19.01.52
SessionDesc:PT=0 PD=PCMU SR=8000 FD=20 FPP=2 PLC=3 SSUP=on
CallID:1890463548@alice.chicago.com
LocalAddr:IP=10.10.1.100 PORT=5000 SSRC=fjuekdn393k
RemoteAddr:IP=11.1.1.150 PORT=5002 SSRC=r3k3k99weid
JitterBuffer:JBA=3 JBR=2 JBN=40 JBM=80 JBA=120
PacketLoss:NLR=5.0 JDR=2.0
BurstGapLoss:BLD=0 BD=0 GLD=2.0 GD=500
Delay:RTD=200 ESD=140 IAJ=2
Signal:SL=2 NL=10 RERL=14
QualityEst:RLQ=90 RCQ=85 EXTR=90 MOSLQ=3.4 MOSCQ=3.3 QoEEstAlg=G.107
OtherDir Metrics:
TimeStamps:START=10012004.18.23.43 STOP=10012004.18.26.02
SessionDesc:PT=0 PD=PCMU SR=8000 FD=20 FPP=2 PLC=3 SSUP=on
CallID:1890463548@alice.uac.chicago.com
LocalAddr:IP=11.1.1.150 PORT=5002 SSRC=r3k3k99weid
RemoteAddr:IP=10.10.1.100 PORT=5000 SSRC=fjuekdn393k
JitterBuffer:JBA=3 JBR=2 JBN=40 JBM=80 JBA=120
PacketLoss:NLR=5.0 JDR=2.0
BurstGapLoss:BLD=0 BD=0 GLD=2.0 GD=500
Delay:RTD=200 ESD=140 IAJ=2
Signal:SL=2 NL=10 RERL=0
QualityEst:RLQ=90 RCQ=85 EXTRI=90 MOSLQ=3.4 MOSCQ=3.3 QoEEstAlg=G.107
DialogID:38419823470834;to-tag=8472761;from-tag=9123dh3111
This alert indicates that the quality of the call in progress,
as measured by the Listening Quality R metric, has degraded to an
unacceptable level. For futher troubleshooting of the problem, all
metrics are populated, including the remote values which were obtained
via RTCP XR (RFC 3611) in the endpoints.
4.7.3. End of Session Report using NOTIFY
Alice Proxy/Registrar Collector Bob
| | | |
| | | |
| REGISTER Allow-Event:vq-rtcpxr F1 | |
|------------------->| | |
| 200 OK F2 | | |
Johnston, et al. Expires April 17, 2006 [Page 15]
Internet-Draft SIP Event for Service Quality Reporting October 2005
|<-------------------| | |
| | SUBSCRIBE Event:vq-rtcpxr F3 |
| |<-------------------| |
| SUBSCRIBE Event:vq-rtcpxr F4 | |
|<-------------------| | |
| 200 OK F5 | | |
|------------------->| | |
| | 200 OK F6 | |
| |------------------->| |
| INVITE F7 | | |
|------------------->| | |
| | INVITE F8 | |
| |---------------------------------------->|
| | 200 OK F9 | |
| |<----------------------------------------|
| 200 OK F10 | | |
|<-------------------| | |
| ACK F11 | | |
|------------------->| | |
| | ACK F12 | |
| |---------------------------------------->|
| RTP | | |
|<============================================================>|
| RTCP, RTCP XR | |
|<============================================================>|
| | | |
| BYE F13 | | |
|------------------->| BYE F14 | |
| |---------------------------------------->|
| | 200 OK F15 | |
| |<----------------------------------------|
| 200 OK F16 | | |
|<-------------------| | |
| NOTIFY Event:vq-rtcpxr F17 | |
|------------------->| | |
| | NOTIFY Event:vq-rtcpxr F18 |
| |------------------->| |
| | 200 OK F19 | |
| |<-------------------| |
| 200 OK F20 | | |
|<-------------------| | |
Figure 3. Summary report with NOTIFY sent after session termination.
In the call flow depicted in Figure 3, the following message format
is sent in F17:
Johnston, et al. Expires April 17, 2006 [Page 16]
Internet-Draft SIP Event for Service Quality Reporting October 2005
NOTIFY sip:collector@example.com SIP/2.0
Via: SIP/2.0/UDP pc22.example.com;branch=z9hG4bK3343d7
Max-Forwards: 70
To: <sip:collector@example.com>;tag=43524545
From: Alice <sip:alice@example.com>;tag=a3343df32
Call-ID: 1890463548@alice.chicago.com
CSeq: 4321 NOTIFY
Contact: <sip:alice@pc22.example.com>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
SUBSCRIBE, NOTIFY
Event: vq-rtcpxr
Accept: application/sdp, message/sipfrag
Subscription-State: active;expires=3600
Content-Type: application/vq-rtcpxr
Content-Length: ...
VQSessionReport
LocalMetrics:
TimeStamps:START=10012004.18.23.43 STOP=10012004.18.26.02
SessionDesc:PT=0 PD=PCMU SR=8000 FD=20 FPP=2 PLC=3 SSUP=on
CallID:1890463548@alice.uac.chicago.com
LocalAddr:IP=10.10.1.100 PORT=5000 SSRC=fjuekdn393k
RemoteAddr:IP=11.1.1.150 PORT=5002 SSRC=r3k3k99weid
JitterBuffer:JBA=3 JBR=2 JBN=40 JBM=80 JBA=120
PacketLoss:NLR=5.0 JDR=2.0
BurstGapLoss:BLD=0 BD=0 GLD=2.0 GD=500
Delay:RTD=200 ESD=140 IAD=2
Signal:SL=2 NL=10 RERL=14
QualityEst:RLQ=90 RCQ=85 EXTRI=90 MOSLQ=3.4 MOSCQ=3.3 QoEEstAlg=G.107
RemoteMetrics:
TimeStamps:START=10012004.18.23.43 STOP=10012004.18.26.02
SessionDesc:PT=0 PD=PCMU SR=8000 FD=20 FPP=2 PLC=3 SSUP=on
CallID:1890463548@alice.uac.chicago.com
LocalAddr:IP=11.1.1.150 PORT=5002 SSRC=r3k3k99weid
RemoteAddr:IP=10.10.1.100 PORT=5000 SSRC=fjuekdn393k
JitterBuffer:JBA=3 JBR=2 JBN=40 JBM=80 JBA=120
PacketLoss:NLR=5.0 JDR=2.0
BurstGapLoss:BLD=0 BD=0 GLD=2.0 GD=500
Delay:RTD=200 ESD=140 IAJ=2
Signal:SL=2 NL=10 RERL=0
QualityEst:RLQ=90 RCQ=85 EXTRI=90 MOSLQ=3.4 MOSCQ=3.3 QoEEstAlg=G.107
DialogID:38419823470834;to-tag=8472761;from-tag=9123dh311
4.7.4. Mid Session Threshold Violation using NOTIFY
Alice Proxy/Registrar Collector Bob
Johnston, et al. Expires April 17, 2006 [Page 17]
Internet-Draft SIP Event for Service Quality Reporting October 2005
| | | |
| | | |
| REGISTER Allow-Event:vq-rtcpxr F1 | |
|------------------->| | |
| 200 OK F2 | | |
|<-------------------| | |
| | SUBSCRIBE Event:vq-rtcpxr F3 |
| |<-------------------| |
| SUBSCRIBE Event:vq-rtcpxr F4 | |
|<-------------------| | |
| 200 OK F5 | | |
|------------------->| | |
| | 200 OK F6 | |
| |------------------->| |
| INVITE F7 | | |
|------------------->| | |
| | INVITE F8 | |
| |---------------------------------------->|
| | 200 OK F9 | |
| |<----------------------------------------|
| 200 OK F10 | | |
|<-------------------| | |
| ACK F11 | | |
|------------------->| | |
| | ACK F12 | |
| |---------------------------------------->|
| RTP | | |
|<============================================================>|
| RTCP, RTCP XR | |
|<============================================================>|
| NOTIFY Event:vq-rtcpxr F17 | |
|------------------->| | |
| | NOTIFY Event:vq-rtcpxr F18 |
| |------------------->| |
| | 200 OK F19 | |
| |<-------------------| |
| 200 OK F20 | | |
|<-------------------| | |
| | | |
| BYE F13 | | |
|------------------->| BYE F14 | |
| |---------------------------------------->|
| | 200 OK F15 | |
| |<----------------------------------------|
| 200 OK F16 | | |
|<-------------------| | |
| NOTIFY Event:vq-rtcpxr F17 | |
|------------------->| | |
Johnston, et al. Expires April 17, 2006 [Page 18]
Internet-Draft SIP Event for Service Quality Reporting October 2005
| | NOTIFY Event:vq-rtcpxr F18 |
| |------------------->| |
| | 200 OK F19 | |
| |<-------------------| |
| 200 OK F20 | | |
|<-------------------| | |
Figure 4. Summary report sent during session with threshold report.
In the call flow depicted in Figure 4, the following message format
is sent in F17:
NOTIFY sip:collector@chicago.example.com SIP/2.0
Via: SIP/2.0/UDP pc22.example.com;branch=z9hG4bK3343d7
Max-Forwards: 70
To: <sip:collector@example.com>
From: Alice <sip:alice@example.com>;tag=a3343df32
Call-ID: 1890463548@alice.chicago.com
CSeq: 4321 PUBLISH
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
SUBSCRIBE, NOTIFY
Event: vq-rtcpxr
Accept: application/sdp, message/sipfrag
Content-Type: application/vq-rtcpxr
Content-Length: ...
VQAlertReport: Type=RLQ Severity=Warning Dir=local
Metrics:
TimeStamps:START=10012004.19.01.04 STOP=10012004.19.01.52
SessionDesc:PT=0 PD=PCMU SR=8000 FD=20 FPP=2 PLC=3 SSUP=on
CallID:1890463548@alice.chicago.com
LocalAddr:IP=10.10.1.100 PORT=5000 SSRC=fjuekdn393k
RemoteAddr:IP=11.1.1.150 PORT=5002 SSRC=r3k3k99weid
JitterBuffer:JBA=3 JBR=2 JBN=40 JBM=80 JBA=120
PacketLoss:NLR=5.0 JDR=2.0
BurstGapLoss:BLD=0 BD=0 GLD=2.0 GD=500
Delay:RTD=200 ESD=140 IAJ=2
Signal:SL=2 NL=10 RERL=14
QualityEst:RLQ=90 RCQ=85 EXTR=90 MOSLQ=3.4 MOSCQ=3.3 QoEEstAlg=G.107
OtherDir Metrics:
TimeStamps:START=10012004.18.23.43 STOP=10012004.18.26.02
SessionDesc:PT=0 PD=PCMU SR=8000 FD=20 FPP=2 PLC=3 SSUP=on
CallID:1890463548@alice.uac.chicago.com
LocalAddr:IP=11.1.1.150 PORT=5002 SSRC=r3k3k99weid
RemoteAddr:IP=10.10.1.100 PORT=5000 SSRC=fjuekdn393k
JitterBuffer:JBA=3 JBR=2 JBN=40 JBM=80 JBA=120
PacketLoss:NLR=5.0 JDR=2.0
BurstGapLoss:BLD=0 BD=0 GLD=2.0 GD=500
Johnston, et al. Expires April 17, 2006 [Page 19]
Internet-Draft SIP Event for Service Quality Reporting October 2005
Delay:RTD=200 ESD=140 IAJ=2
Signal:SL=2 NL=10 RERL=0
QualityEst:RLQ=90 RCQ=85 EXTRI=90 MOSLQ=3.4 MOSCQ=3.3 QoEEstAlg=G.107
DialogID:38419823470834;to-tag=8472761;from-tag=9123dh31111
This alert indicates that the quality of the call in progress, as calculated
using the Listening Quality transmission rating R , has degraded to an
unacceptable level. For futher troubleshooting of the problem, all metrics
are populated, including the remote values which were obtained via RTCP XR [4]
in the endpoints..
4.8. IANA Considerations
This document registers a new SIP Event Package and a new MIME type.
4.8.1. SIP Event Package Registration
Package name: vq-rtcpxr
Type: package
Contact: Alan Johnston <alan.johnston@mci.com>
Published Specification: This document
Johnston, et al. Expires April 17, 2006 [Page 20]
Internet-Draft SIP Event for Service Quality Reporting October 2005
4.8.2. application/vq-rtcp-xr MIME Registration
MIME media type name: application
MIME subtype name: vq-rtcpxr
Mandatory parameters: none
Optional parameters: none
Encoding considerations: text
Security considerations: See next section.
Interoperability considerations: none.
Published specification: This document.
Applications which use this media type: This document type is
being used in notifications of VoIP quality reports.
Additional Information:
Magic Number: None
File Extension: None
Macintosh file type code: "TEXT"
Personal and email address for further information: Alan Johnston
<alan.johnston@mci.com>
Intended usage: COMMON
Author/Change controller: The IETF.
4.9. Security Considerations
RTCP reports can contain sensitive information since they can provide
information about the nature and duration of a session established
between two endpoints. As a result, any third party wishing to
obtain this information should be properly authenticated and the
information transferred securely.
4.10. Updates since -07
- Significant syntax change -- made to align with typical SIP syntax.
Johnston, et al. Expires April 17, 2006 [Page 21]
Internet-Draft SIP Event for Service Quality Reporting October 2005
Parameter lines now separate tag from value with colon and individual
parameters separate tag from value with equals.
- Clean up of examples based on comments.
4.11. Updates since -06
- Changed package name from "svcqual" to "vq-rtcpxr" as the focus
will be only voice quality reporting based on RTCP XR.
- Rewrite of verbage in document to clarify that the focus will be
voice quality reporting and not general performance or service
quality reporting.
- Removed section on "Why SNMP is not appropriate" as it was
inaccurate and misleading.
- Removed usage of SDP lines for describing the basic session
parameters. A reduced format designed specifically for this document
is provided instead.
- General clean up of syntax based on comments from WG
- Removed general description of parameters, instead referring to
RTCP XR for more details in most cases.
- Reworked message flow examples using new syntax.
4.12. Updates since -04
- Changed package name from "perfrpt" to "svcqual"
4.13. Updates since -03
- Removed discussion of alternative mechanisms
- Changed from NOTIFY transport to PUBLISH transport.
- Changed package name from "rtcp-xr" to "perfrpt"
- Corrected call flows.
- Minor updates to message body format.
- Added IANA registration for perfrpt SIP Event Package and
application/rtcp-xr MIME registration.
- Added more discussion for motivation and reasons why SNMP is not
Johnston, et al. Expires April 17, 2006 [Page 22]
Internet-Draft SIP Event for Service Quality Reporting October 2005
suitable
4.14. Contributors
The authors would like to thank Rajesh Kumar, Dave Oran and Tom
Redman for their discussions.
5. Informative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[2] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,
Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP:
Session Initiation Protocol", RFC 3261, June 2002.
[3] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson,
"RTP: A Transport Protocol for Real-Time Applications", STD 64,
RFC 3550, July 2003.
[4] Friedman, T., Caceres, R., and A. Clark, "RTP Control Protocol
Extended Reports (RTCP XR)", RFC 3611, November 2003.
[5] Huitema, C., "Real Time Control Protocol (RTCP) attribute in
Session Description Protocol (SDP)", RFC 3605, October 2003.
[6] Roach, A., "Session Initiation Protocol (SIP)-Specific Event
Notification", RFC 3265, June 2002.
[7] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[8] Niemi, A., "An Event State Publication Extension to the Session
Initiation Protocol (SIP)", draft-ietf-sip-publish-04 (work in
progress), May 2004.
Johnston, et al. Expires April 17, 2006 [Page 23]
Internet-Draft SIP Event for Service Quality Reporting October 2005
Authors' Addresses
Alan Johnston
MCI
100 South 4th Street
St. Louis, MO 63104
Email: alan.johnston@mci.com
Henry Sinnreich
Pulver
115 Broadhollow Drive, Suite 250
Melville, NY 11747, NY 11747
Email: henry@pulver.com
Alan Clark
Telchemy Incorporated
3360 Martins Farm Road, Suite 200
Suwanee, GA 30024
Email: alan@telchemy.com
Amy Pendleton
Nortel Networks
2380 Performance Drive
Richardson, TX 75081
Email: aspen@nortelnetworks.com
Johnston, et al. Expires April 17, 2006 [Page 24]
Internet-Draft SIP Event for Service Quality Reporting October 2005
Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Disclaimer of Validity
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the
Internet Society.
Johnston, et al. Expires April 17, 2006 [Page 25]