One document matched: draft-ietf-xrblock-rtcp-xr-meas-identity-05.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-meas-identity-05.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="Measurement Reporting">Measurement Identity and information
Reporting using SDES item and XR Block</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="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 RTP Control Protocol (RTCP) Source
Description (SDES) item and an RTCP Extended Report (XR) Block carrying
parameters that identify and describe a measurement period, to which one
or more other RTCP XR Report Blocks may refer. </t>
</abstract>
</front>
<middle>
<section anchor="intro" title="Introduction">
<t>This document defines one new RTP Control Protocol (RTCP) Source
Description (SDES) <xref target="RFC3550"></xref> item, and one new
Extended Report (XR) Report Block carrying parameters that identify and
describe a measurement period, to which one or more other RTCP XR Report
Blocks may refer. </t>
<t>The SDES item provides a field for an application specific auxiliary
identifier. This identifier may be used to correlate data in XR Blocks
within an RTP session with data from a non-RTP session.</t>
<t>A RTCP Measurement Identity SDES packet may be associated with a set
of RTCP XR metrics blocks which share the same application specific
measurement identifier.</t>
<t>The XR Report Block does not contain any measurement results
(metrics). Instead, it provides information relevant to a measurement
reported in one or more other block types, including: <list
style="symbols">
<t>the sequence number of the first packet of the RTP session,</t>
<t>the extended sequence numbers of the first packet of the current
measurement interval, and the last packet included in the
measurement,</t>
<t>the duration of the most recent measurement interval and</t>
<t>the duration of the interval applicable to cumulative
measurements (which may be the duration of the RTP session to
date).</t>
</list></t>
<t>The method for calculation of the extended RTP sequence number is
provide in Real-time Transport Protocol (RTP) <xref
target="RFC3550"></xref>.</t>
<t>The RTCP XR Report Block containing the measurement information is
intended to provide a single copy of the information necessary to relate
measurement data in the RTCP XR blocks to the stream, and measurement
period, to which they refer. Commonly, multiple other small metric
blocks contain measurement data for the same stream and period, and it
would be a large overhead if all of these metric blocks carried
duplicated data for measurement identification.</t>
<t>The RTCP XR Report Block may be associated with a set of RTCP XR
metrics blocks which share the same information relevant to a reported
measurement. There may be several such sets in an RTCP packet, in which
each set share the same information relevant to a reported measurement.
There may also be RTCP XR blocks in the packet which are not associated
with a Measurement Information block, for example blocks which were
defined before the Measurement Identity and information mechanism was
introduced by this document.</t>
<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> defines an
extensible structure for reporting using an RTCP Extended Report (XR).
This document 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. The SDES item and XR Block described in this document
are in accordance with <xref target="RFC6390"></xref> and <xref
target="MONARCH"></xref>.</t>
</section>
<section title="Applicability">
<t>The RTCP SDES item and the RTCP XR block defined in this document
provides information relevant to the measurements for members of a
family of RTCP XR metrics blocks which are designed to use it. To use
the mechanism defined here, the RTCP XR block containing measurement
information is not required to be in the same RTCP packet as the SDES
item containing measurement identity.</t>
</section>
</section>
<section title="Terminology">
<section title="Standards Language">
<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 <xref
target="RFC2119"></xref>.</t>
</section>
</section>
<section title="Measurement Identity SDES Item">
<t>This section defines the format of the Measurement Identity SDES
item. The SDES item is carried in the RTCP SDES packet. The packet
format for the RTCP SDES is defined in Section 6.5 of <xref
target="RFC3550"></xref>. Each SDES packet is composed of a header with
fixed-length fields for version, source count, packet type (PT), and
length, followed by zero of more SDES items. In the SDES packet, the PT
field is set to SDES (202).</t>
<section title="APSI: Application Specific Identifier SDES Item">
<figure>
<artwork>
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| APSI=TBD | length |application specific identifier
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ....
+-+-+-+-+-+-+-+-+</artwork>
</figure>
<t>Application specific identifier is an additional identifier which
is useful in the context of a specific application, e.g. an MPEG-2
transport identifier <xref target="MPEG2"></xref>. This item MUST be
ignored by applications that are not configured to make use of it. The
identifier is variable length. Its length is described by the length
field. The value of the length field does not include the two octet
SDES item header. If no identifier is provided, the length field MUST
be set to zero.</t>
</section>
</section>
<section title="Measurement Information XR Block">
<section title="Report Block Structure">
<figure title="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=NMI | Reserved | block length = 6 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SSRC of stream source |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved | first sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| extended first sequence number of interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| extended last sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Duration (Cumulative) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Measurement Duration (Interval) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
</artwork>
</figure>
</section>
<section title="Definition of Fields in Measurement Information Report Block">
<t><list style="hanging">
<t hangText="Block type (BT): 8 bits"><vspace blankLines="1" />A
Measurement Information Report Block is identified by the constant
NMI. <vspace blankLines="1" />[Note to RFC Editor: please replace
NMI with the IANA provided RTCP XR block type for this block.]
<vspace blankLines="1" /></t>
<t hangText="Reserved.: 8 bits"><vspace blankLines="1" />These
bits are reserved. They MUST be set to zero by senders and 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
Measurement Information block, the block length is equal to 6.
<vspace blankLines="1" /></t>
<t hangText="SSRC of source: 32 bits"><vspace blankLines="1" /> As
defined in Section 4.1 of <xref target="RFC3611"></xref>. <vspace
blankLines="1" /></t>
<t hangText="Reserved: 16 bits"><vspace blankLines="1" />These
bits are reserved. They MUST be set to zero by senders and ignored
by receivers. <vspace blankLines="1" /></t>
<t hangText="First sequence number: 16 bits"><vspace
blankLines="1" />The RTP sequence number of the first received RTP
packet of the session, used to determine the number of packets
contributing to cumulative measurements. <vspace
blankLines="1" /></t>
<t
hangText="Extended first sequence number of interval: 32 bits"><vspace
blankLines="1" />The extended RTP sequence number of the first
received RTP packet of the current measurement interval. In
accordance with <xref target="RFC3550"></xref>, the extended
sequence number is expressed as the low 16 bits value containing
the sequence number received in an RTP data packet and the most
significant 16 bits value containing the corresponding count of
sequence number cycles.<vspace blankLines="1" /></t>
<t hangText="Extended last sequence number: 32 bits"><vspace
blankLines="1" />The extended RTP sequence number of the last
received RTP packet which contributed to this measurement. In
accordance with <xref target="RFC3550"></xref>, the extended
sequence number is expressed as the low 16 bits value containing
the sequence number received in an RTP data packet and the most
significant 16 bits value containing the corresponding count of
sequence number cycles.<vspace blankLines="1" /></t>
<t hangText="Measurement Duration (Cumulative) : 32 bits"><vspace
blankLines="1" />The duration, expressed in units of 1/65536
seconds, of the reporting interval applicable to Cumulative
reports which use this Measurement Information block. The value of
this field can be calculated by the receiver of the RTP media
stream, for example, based on received RTP media packets or using
RTCP method described in <xref target="RFC3550"></xref>. <vspace
blankLines="1" /></t>
<t hangText="Measurement Duration (Interval) : 32 bits"><vspace
blankLines="1" />The duration, expressed in units of 1/65536
seconds, of the reporting interval applicable to Interval reports
which use this Measurement Information block . The value of this
field can be calculated by the receiver of the RTP media stream,
for example, based on received RTP media packets or using RTCP
method described in <xref target="RFC3550"></xref>. <vspace
blankLines="1" /></t>
</list></t>
</section>
</section>
<section title="IANA Considerations">
<t>New SDES types for RTCP SDES are subject to IANA registration. For
general guidelines on IANA considerations for RTCP SDES, refer to <xref
target="RFC3550"></xref>.</t>
<section title="New RTCP SDES Type value">
<t>This document assigns one additional SDES type in the IANA "RTCP XR
Block Type Registry" to the Measurement Identity SDES items as follow:
<figure>
<artwork>
abbrev. name value
APSI: Application Specific Identifier TBD
</artwork>
</figure></t>
<t>[Note to RFC Editor: please replace APSI with the IANA provided
RTCP SDES type for the SDES item.]</t>
</section>
<section title="New RTCP XR Block Type value">
<t>This document assigns the block type value NMI in the IANA "RTCP XR
Block Type Registry" to the "Measurement Information Block".</t>
<t>[Note to RFC Editor: please replace NMI with the IANA provided RTCP
XR block type for this block.]</t>
</section>
<section title="Contact information for registrations">
<t><figure>
<artwork>
The contact information for the registrations is:
Qin Wu (sunseawq@huawei.com)
101 Software Avenue, Yuhua District
Nanjing, Jiangsu 210012
China
</artwork>
</figure><vspace blankLines="1" /></t>
</section>
</section>
<section title="Security Considerations">
<t>RTCP reports can contain sensitive information, including information
about the nature and duration of a session established between two or
more endpoints. Therefore, the use of security mechanisms with RTP, as
documented in Section 9 of <xref target="RFC3550"></xref> SHOULD
apply.</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="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>
<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>
</references>
<references title="Informative References">
<reference anchor="MONARCH">
<front>
<title>Monitoring Architectures for RTP</title>
<author fullname="Qin Wu" initials="Q." surname="Wu">
<organization></organization>
</author>
<author fullname="Geoff Hunt" initials="G." surname="Hunt">
<organization></organization>
</author>
<author fullname="Philip Arden" initials="P.">
<organization></organization>
</author>
<date month="March" year="2012" />
</front>
<seriesInfo name="ID" value="draft-ietf-avtcore-monarch-11" />
<format type="TXT" />
</reference>
<reference anchor="MPEG2">
<front>
<title>ISO/IEC, "Standard 13818-1"</title>
<author>
<organization></organization>
</author>
<date month="December" year="2000" />
</front>
</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>
</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-xr-rtcp-meas-identity-00">
<t>The following are the major changes to
draft-ietf-avt-rtcp-xr-meas-identity-02: <list style="symbols">
<t>Change the use of SDES item to convey measurement identity
instead of XR Block in section 2.</t>
<t>Update references.</t>
<t>Update security section and remove SDP signaling section.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-xr-rtcp-meas-identity-01">
<t>The following are the major changes to
draft-ietf-xrblock-xr-rtcp-meas-identity-00: <list style="symbols">
<t>Replace SDES item containing additional measurement information
with XR Block.</t>
<t>Add section 2 to describe following RFC2119 language.</t>
<t>Add Section 1.2 to make SDES item and XR Report be compliant
with RFC3550 and RFC3611</t>
<t>Add Section 1.3 to make SDES item and XR Report follow
Performance Metrics Framework and RTP Monitoring Architecture.</t>
<t>Add section5.2 to register the new RTCP XR Block Type
value.</t>
<t>Remove RTCP SDES Type values that are needed.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-xr-rtcp-meas-identity-02">
<t>The following are the major changes to
draft-ietf-xrblock-xr-rtcp-meas-identity-01: <list style="symbols">
<t>Relocating information that belong to SDES item and XR Block
respectively in the section 1.</t>
<t>Rephrasing the text that describes SDES packet composition.</t>
<t>Rephrasing identifier description.</t>
<t>Other Editorial changes.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-xr-rtcp-meas-identity-03">
<t>The following are the major changes to
draft-ietf-xrblock-xr-rtcp-meas-identity-02: <list style="symbols">
<t>The Editorial changes.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-xr-rtcp-meas-identity-04">
<t>The following are the major changes to
draft-ietf-xrblock-xr-rtcp-meas-identity-03: <list style="symbols">
<t>Change unit of measurement duration from ms to 1/65536
seconds.</t>
</list></t>
</section>
<section title="draft-ietf-xrblock-xr-rtcp-meas-identity-05">
<t>The following are the major changes to
draft-ietf-xrblock-xr-rtcp-meas-identity-04: <list style="symbols">
<t>Clarify the definition of extended sequence number.</t>
</list></t>
</section>
</section>
</back>
</rfc>
| PAFTECH AB 2003-2026 | 2026-04-24 06:37:24 |