draft-ietf-avt-rtcp-guidelines-00.txt   draft-ietf-avt-rtcp-guidelines-01.txt 
AVT Working Group J. Ott AVT Working Group J. Ott
Internet-Draft Helsinki University of Technology Internet-Draft Helsinki University of Technology
Intended status: Informational C. Perkins Intended status: Informational C. Perkins
Expires: January 8, 2009 University of Glasgow Expires: September 10, 2009 University of Glasgow
July 7, 2008 March 9, 2009
Guidelines for Extending the RTP Control Protocol (RTCP) Guidelines for Extending the RTP Control Protocol (RTCP)
draft-ietf-avt-rtcp-guidelines-00.txt draft-ietf-avt-rtcp-guidelines-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any This Internet-Draft is submitted to IETF in full conformance with the
applicable patent or other IPR claims of which he or she is aware provisions of BCP 78 and BCP 79.
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 Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 8, 2009. This Internet-Draft will expire on September 10, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract Abstract
The RTP Control Protocol (RTCP) is used along with the Real-time The RTP Control Protocol (RTCP) is used along with the Real-time
Transport Protocol (RTP) to provide a control channel between media Transport Protocol (RTP) to provide a control channel between media
senders and receivers. This allows constructing a feedback loop to senders and receivers. This allows constructing a feedback loop to
enable application adaptivity and monitoring, among other uses. The enable application adaptivity and monitoring, among other uses. The
basic reporting mechanisms offered by RTCP are generic, yet quite basic reporting mechanisms offered by RTCP are generic, yet quite
powerful and suffice to cover a range of uses. This document powerful and suffice to cover a range of uses. This document
provides guidelines on extending RTCP if those basic mechanisms prove provides guidelines on extending RTCP if those basic mechanisms prove
skipping to change at page 2, line 24 skipping to change at page 3, line 4
Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 8 Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . 8
4. Issues with RTCP Extensions . . . . . . . . . . . . . . . . . 8 4. Issues with RTCP Extensions . . . . . . . . . . . . . . . . . 8
5. Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5. Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
9.1. Normative References . . . . . . . . . . . . . . . . . . . 15 9.1. Normative References . . . . . . . . . . . . . . . . . . . 15
9.2. Informative References . . . . . . . . . . . . . . . . . . 16 9.2. Informative References . . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
Intellectual Property and Copyright Statements . . . . . . . . . . 18
1. Introduction 1. Introduction
The Real-time Transport Protocol (RTP) [RFC3550] is used to carry The Real-time Transport Protocol (RTP) [RFC3550] is used to carry
time-dependent (often continuous) media such as audio or video across time-dependent (often continuous) media such as audio or video across
a packet network in an RTP session. RTP usually runs on top of an a packet network in an RTP session. RTP usually runs on top of an
unreliable transport such as UDP, DTLS, or DCCP, so that RTP packets unreliable transport such as UDP, DTLS, or DCCP, so that RTP packets
are susceptible to loss, re-ordering, or duplication. Associated are susceptible to loss, re-ordering, or duplication. Associated
with RTP is the RTP Control Protocol (RTCP) which provides a control with RTP is the RTP Control Protocol (RTCP) which provides a control
channel for each session: media senders provide information about channel for each session: media senders provide information about
skipping to change at page 18, line 4 skipping to change at line 751
Email: jo@netlab.hut.fi Email: jo@netlab.hut.fi
Colin Perkins Colin Perkins
University of Glasgow University of Glasgow
Department of Computing Science Department of Computing Science
Lilybank Gardens Lilybank Gardens
Glasgow G12 8QQ Glasgow G12 8QQ
United Kingdom United Kingdom
Email: csp@csperkins.org Email: csp@csperkins.org
Full Copyright Statement
Copyright (C) The IETF Trust (2008).
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.
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, THE IETF TRUST 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.
Intellectual Property
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.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
 End of changes. 7 change blocks. 
10 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/