One document matched: draft-ietf-xrblock-rtcp-xr-jb-00.xml
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com)
by Daniel M Kohn (private) -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY rfc2119 PUBLIC "" "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
]>
<rfc category="std" docName="draft-ietf-xrblock-rtcp-xr-jb-00.txt"
ipr="trust200902">
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<front>
<title abbrev="RTCP XR Jitter Buffer">RTCP XR Report Block for Jitter
Buffer Metric Reporting</title>
<author fullname="Geoff Hunt" initials="G." surname="Hunt">
<organization>Unaffiliated</organization>
<address>
<email>r.geoff.hunt@gmail.com</email>
</address>
</author>
<author fullname="Alan Clark" initials="A." surname="Clark">
<organization abbrev="Telchemy">Telchemy Incorporated</organization>
<address>
<postal>
<street>2905 Premiere Parkway, Suite 280</street>
<city>Duluth</city>
<region>GA</region>
<code>30097</code>
<country>USA</country>
</postal>
<email>alan.d.clark@telchemy.com</email>
</address>
</author>
<author fullname="Varun Singh" initials="V." surname="Singh">
<organization>Aalto University</organization>
<address>
<postal>
<street>Otakaari 5 A</street>
<region>Espoo</region>
<code>FIN 02150</code>
<country>Finland</country>
</postal>
<email>vsingh.ietf@gmail.com</email>
</address>
</author>
<author fullname="Qin Wu" initials="Q." surname="Wu">
<organization>Huawei</organization>
<address>
<postal>
<street>101 Software Avenue, Yuhua District</street>
<city>Nanjing</city>
<region>Jiangsu</region>
<code>210012</code>
<country>China</country>
</postal>
<email>sunseawq@huawei.com</email>
</address>
</author>
<date year="2012" />
<area>Real-time Applications and Infrastructure Area</area>
<workgroup>Audio/Video Transport Working Group</workgroup>
<keyword>RFC</keyword>
<keyword>Request for Comments</keyword>
<keyword>I-D</keyword>
<keyword>Internet-Draft</keyword>
<keyword>Real Time Control Protocol</keyword>
<abstract>
<t>This document defines an RTCP XR Report Block that allows the
reporting of Jitter Buffer metrics for a range of RTP applications.</t>
</abstract>
</front>
<middle>
<section anchor="intro" title="Introduction">
<section title="Jitter Buffer Metrics Block">
<t>This draft defines a new block type to augment those defined in
<xref target="RFC3611"></xref>, for use in a range of RTP
applications.</t>
<t>The new block type provides information on jitter buffer
configuration and performance.</t>
<t>The metric belongs to the class of transport-related terminal
metrics defined in <xref target="MONARCH"></xref> (work in
progress).</t>
<t>Instances of this Metrics Block refer by SSRC to the separate
auxiliary Measurement Information block <xref target="MEASI"></xref>
which contains information such as the SSRC of the measured stream,
and RTP sequence numbers and time intervals indicating the span of the
report.</t>
</section>
<section title="RTCP and RTCP XR Reports">
<t>The use of RTCP for reporting is defined in <xref
target="RFC3550"></xref>. <xref target="RFC3611"></xref> defined an
extensible structure for reporting using an RTCP Extended Report (XR).
This draft defines a new Extended Report block that MUST be used as
defined in <xref target="RFC3550"></xref> and <xref
target="RFC3611"></xref>.</t>
</section>
<section title="Performance Metrics Framework">
<t>The Performance Metrics Framework <xref target="RFC6390"></xref>
provides guidance on the definition and specification of performance
metrics. The RTP Monitoring Architectures <xref
target="MONARCH"></xref> provides guideline for reporting block format
using RTCP XR. Metrics described in this draft are in accordance with
the guidelines in <xref target="RFC6390"></xref><xref
target="MONARCH"></xref>.</t>
</section>
<section title="Applicability">
<t>These metrics are applicable to a range of RTP applications.</t>
</section>
</section>
<section title="Jitter Buffer Metrics Block">
<t>This block describes the configuration and operating parameters of
the jitter buffer in the receiver of the RTP end system or RTP mixer
which sends the report. Instances of this Metrics Block refer by SSRC to
the separate auxiliary Measurement Information block [MEASI] which
contains measurement intervals. This metric block relies on the
measurement interval in the Measurement Information block indicating the
span of the report and should be sent in the same compound RTCP packet
as the measurement information block. If the measurement interval is not
received in the same compound RTCP packet as this metric block, this
metric block should be discarded. </t>
<section title="Report Block Structure">
<t>JB Metrics Block<figure title="Figure 1: Report Block Structure">
<artwork>
0 1 2 3
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| BT=NJB | I |jb cfg |rsv| block length=3 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of Source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JB nominal | JB maximum |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| JB high water mark | JB low water mark |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure></t>
</section>
<section title="Definition of Fields in Jitter Buffer Metrics Block">
<t><list style="hanging">
<t hangText="Block type (BT): 8 bits"><vspace blankLines="1" /> A
Jitter Buffer Metrics Report Block is identified by the constant
NJB.<vspace blankLines="1" /> [Note to RFC Editor: please replace
NJB with the IANA provided RTCP XR block type for this
block.]<vspace blankLines="1" /></t>
<t hangText="Interval Metric flag (I): 2 bits"><vspace
blankLines="1" />This field is used to indicate whether the Jitter
Buffer metrics are Sampled, Interval or Cumulative metrics, that
is, whether the reported values applies to the most recent
measurement interval duration between successive metrics reports
(I=10) (the Interval Duration) or to the accumulation period
characteristic of cumulative measurements (I=11) (the Cumulative
Duration) or is a sampled instantaneous value (I=01) (Sampled
Value). <vspace blankLines="1" /></t>
<t hangText="Jitter Buffer Configuration (jb cfg): 4 bits"><vspace
blankLines="1" /> This field is used to identify the jitter buffer
method in use at the receiver, according to the following
code:<list>
<t>bits 014-011<list>
<t>0 = Fixed jitter buffer</t>
<t>1 = Adaptive jitter buffer</t>
<t>Other values reserved</t>
</list></t>
</list><vspace blankLines="1" /></t>
<t hangText="Reserved (resv): 2 bits"><vspace
blankLines="1" />These bits are reserved. They SHOULD be set to
zero by senders and MUST be ignored by receivers.<vspace
blankLines="1" /></t>
<t hangText="block length: 16 bits"><vspace blankLines="1" /> The
length of this report block in 32-bit words, minus one. For the
Delay block, the block length is equal to 3.<vspace
blankLines="1" /></t>
<t
hangText="jitter buffer nominal delay (JB nominal): 16 bits"><vspace
blankLines="1" /> This is the current nominal jitter buffer delay
in milliseconds, which corresponds to the nominal jitter buffer
delay for packets that arrive exactly on time. This parameter MUST
be provided for both fixed and adaptive jitter buffer
implementations.<vspace blankLines="1" /> If the measured value
exceeds 0xFFFD, the value 0xFFFE SHOULD be reported to indicate an
over-range measurement. If the measurement is unavailable, the
value 0xFFFF SHOULD be reported.<vspace blankLines="1" /></t>
<t
hangText="jitter buffer maximum delay (JB maximum): 16 bits"><vspace
blankLines="1" /> This is the current maximum jitter buffer delay
in milliseconds which corresponds to the earliest arriving packet
that would not be discarded. In simple queue implementations this
may correspond to the nominal size. In adaptive jitter buffer
implementations, this value may dynamically. This parameter MUST
be provided for both fixed and adaptive jitter buffer
implementations.<vspace blankLines="1" /> If the measured value
exceeds 0xFFFD, the value 0xFFFE SHOULD be reported to indicate an
over-range measurement. If the measurement is unavailable, the
value 0xFFFF SHOULD be reported.<vspace blankLines="1" /></t>
<t
hangText="jitter buffer high water mark (JB high water mark): 16 bits"><vspace
blankLines="1" /> This is the highest value of the jitter buffer
nominal delay which occurred at any time during the reporting
interval.<vspace blankLines="1" /> If the measured value exceeds
0xFFFD, the value 0xFFFE SHOULD be reported to indicate an
over-range measurement. If the measurement is unavailable, the
value 0xFFFF SHOULD be reported.<vspace blankLines="1" /></t>
<t
hangText="jitter buffer low water mark (JB low water mark): 16 bits"><vspace
blankLines="1" />This is the lowest value of the jitter buffer
nominal delay which occurred at any time during the reporting
interval.<vspace blankLines="1" /> If the measured value exceeds
0xFFFD, the value 0xFFFE SHOULD be reported to indicate an
over-range measurement. If the measurement is unavailable, the
value 0xFFFF SHOULD be reported.<vspace blankLines="1" /></t>
</list></t>
</section>
</section>
<section title="SDP Signaling">
<t>[RFC3611] defines the use of SDP (Session Description Protocol) <xref
target="RFC4566"></xref> for signaling the use of XR blocks. XR blocks
MAY be used without prior signaling.</t>
<t>This section augments the SDP <xref target="RFC4566"></xref>
attribute "rtcp-xr" defined in <xref target="RFC3611"></xref> by
providing an additional value of "xr-format" to signal the use of the
report block defined in this document.<figure>
<artwork>
rtcp-xr-attrib = "a=" "rtcp-xr" ":" [xr-format *(SP xr-format)] CRLF
(defined in [RFC3611])
xr-format =/ xr-jb-block
xr-jb-block = "jitter-bfr"
</artwork>
</figure></t>
</section>
<section title="IANA Considerations">
<t>New block types for RTCP XR are subject to IANA registration. For
general guidelines on IANA considerations for RTCP XR, refer to <xref
target="RFC3611"></xref>.</t>
<section title="New RTCP XR Block Type value">
<t>This document assigns the block type value NJB in the IANA "RTCP XR
Block Type Registry" to the "JB Metrics Block".</t>
<t>[Note to RFC Editor: please replace NJB with the IANA provided RTCP
XR block type for this block.]</t>
</section>
<section title="New RTCP XR SDP Parameter">
<t>This document also registers a new parameter "jitter-bfr" in the
"RTCP XR SDP Parameters Registry".</t>
</section>
<section title="Contact information for registrations">
<t><figure>
<artwork>
The contact information for the registrations is:
Geoff Hunt (r.geoff.hunt@gmail.com)
Orion 2 PP3, Adastral Park, Martlesham Heath, Ipswich IP5 3RE, United
Kingdom
</artwork>
</figure><vspace blankLines="1" /></t>
</section>
</section>
<section title="Security Considerations">
<t>It is believed that this proposed RTCP XR report block introduces no
new security considerations beyond those described in <xref
target="RFC3611"></xref>. This block does not provide per-packet
statistics so the risk to confidentiality documented in Section 7,
paragraph 3 of <xref target="RFC3611"></xref> does not apply.</t>
</section>
<section title="Acknowledgments">
<t>The authors gratefully acknowledge the comments and contributions
made by Bruce Adams, Philip Arden, Amit Arora, Bob Biskner, Kevin
Connor, Claus Dahm, Randy Ethier, Roni Even, Jim Frauenthal, Albert
Higashi, Tom Hock, Shane Holthaus, Paul Jones, Rajesh Kumar, Keith
Lantz, Mohamed Mostafa, Amy Pendleton, Colin Perkins, Mike Ramalho, Ravi
Raviraj, Albrecht Schwarz, Tom Taylor, and Hideaki Yamada.</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="RFC2119">
<front>
<title abbrev="RFC Key Words">Key words for use in RFCs to Indicate
Requirement Levels</title>
<author fullname="Scott Bradner" initials="S." surname="Bradner">
<organization>Harvard University</organization>
<address>
<postal>
<street>1350 Mass. Ave.</street>
<street>Cambridge</street>
<street>MA 02138</street>
</postal>
<phone>- +1 617 495 3864</phone>
<email>sob@harvard.edu</email>
</address>
</author>
<date month="March" year="1997" />
<area>General</area>
<keyword>keyword</keyword>
<abstract>
<t>In many standards track documents several words are used to
signify the requirements in the specification. These words are
often capitalized. This document defines these words as they
should be interpreted in IETF documents. Authors who follow these
guidelines should incorporate this phrase near the beginning of
their document: <list>
<t>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 RFC 2119.</t>
</list></t>
<t>Note that the force of these words is modified by the
requirement level of the document in which they are used.</t>
</abstract>
</front>
</reference>
<reference anchor="RFC3611">
<front>
<title>RTP Control Protocol Extended Reports (RTCP XR)</title>
<author fullname="T. Friedman" initials="T." surname="Friedman">
<organization></organization>
</author>
<author fullname="R. Caceres" initials="R." surname="Caceres">
<organization></organization>
</author>
<author fullname="A. Clark" initials="A." surname="Clark">
<organization></organization>
</author>
<date month="November" year="2003" />
<abstract>
<t>This document defines the Extended Report (XR) packet type for
the RTP Control Protocol (RTCP), and defines how the use of XR
packets can be signaled by an application if it employs the
Session Description Protocol (SDP). XR packets are composed of
report blocks, and seven block types are defined here. The purpose
of the extended reporting format is to convey information that
supplements the six statistics that are contained in the report
blocks used by RTCP's Sender Report (SR) and Receiver Report (RR)
packets. Some applications, such as multicast inference of network
characteristics (MINC) or voice over IP (VoIP) monitoring, require
other and more detailed statistics. In addition to the block types
defined here, additional block types may be defined in the future
by adhering to the framework that this document provides.</t>
</abstract>
</front>
</reference>
<reference anchor="RFC4566">
<front>
<title>SDP: Session Description Protocol</title>
<author fullname="M. Handley" initials="M." surname="Handley">
<organization></organization>
</author>
<author fullname="V. Jacobson" initials="V." surname="Jacobson">
<organization></organization>
</author>
<author fullname="C. Perkins" initials="C." surname="Perkins">
<organization></organization>
</author>
<date month="July" year="2006" />
<abstract>
<t>This memo defines the Session Description Protocol (SDP). SDP
is intended for describing multimedia sessions for the purposes of
session announcement, session invitation, and other forms of
multimedia session initiation. [STANDARDS-TRACK]</t>
</abstract>
</front>
</reference>
<reference anchor="RFC3550">
<front>
<title>RTP: A Transport Protocol for Real-Time Applications</title>
<author fullname="Henning Schulzrinne" initials="H."
surname="Schulzrinne">
<organization>Columbia University</organization>
</author>
<date month="July" year="2003" />
</front>
<seriesInfo name="RFC" value="3550" />
<format type="TXT" />
</reference>
</references>
<references title="Informative References">
<reference anchor="MONARCH">
<front>
<title>Monitoring Architectures for RTP</title>
<author fullname="Geoff Hunt" initials="G." surname="Hunt">
<organization></organization>
</author>
<date month="April" year="2012" />
</front>
<seriesInfo name="ID" value="draft-ietf-avtcore-monarch-12" />
<format type="TXT" />
</reference>
<reference anchor="RFC6390">
<front>
<title>Framework for Performance Metric Development</title>
<author fullname="Alan Clark" initials="A." surname="Clark">
<organization></organization>
</author>
<author fullname="Benoit Claise " initials="B." surname="Claise">
<organization></organization>
</author>
<date month="October" year="2011" />
</front>
<seriesInfo name="RFC" value="6390" />
</reference>
<reference anchor="MEASI">
<front>
<title>Measurement Identity and information Reporting using SDES
item and XR Block</title>
<author fullname="Geoff Hunt" initials="G." surname="Hunt">
<organization></organization>
</author>
<date month="April" year="2012" />
</front>
<seriesInfo name="ID"
value="draft-ietf-xrblock-rtcp-xr-meas-identity-06" />
<format type="TXT" />
</reference>
</references>
<section title="Change Log">
<t>Note to the RFC-Editor: please remove this section prior to
publication as an RFC.</t>
<section title="draft-ietf-xrblock-rtcp-xr-jb-00">
<t>The following are the major changes to previous version : <list
style="symbols">
<t>Boilerplate updates.</t>
<t>references updates</t>
<t>allocate 32 bit field in report block for SSRC</t>
<t>Other editorial changes to get alignment with MONARCH
draft.</t>
</list></t>
</section>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 15:11:57 |