draft-ietf-avt-post-repair-rtcp-xr-05.txt   draft-ietf-avt-post-repair-rtcp-xr-06.txt 
AVT A. Begen AVT A. Begen
Internet-Draft D. Hsu Internet-Draft D. Hsu
Intended status: Standards Track M. Lague Intended status: Standards Track M. Lague
Expires: December 18, 2009 Cisco Systems Expires: April 18, 2010 Cisco Systems
June 16, 2009 October 15, 2009
Post-Repair Loss RLE Report Block Type for RTCP XR Post-Repair Loss RLE Report Block Type for RTCP XR
draft-ietf-avt-post-repair-rtcp-xr-05 draft-ietf-avt-post-repair-rtcp-xr-06
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 December 18, 2009. This Internet-Draft will expire on April 18, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 7, line 33 skipping to change at page 7, line 33
to the primary source stream. to the primary source stream.
When using post-repair Loss RLE reports, the amount of bandwidth When using post-repair Loss RLE reports, the amount of bandwidth
consumed by the detailed reports should be considered carefully. The consumed by the detailed reports should be considered carefully. The
bandwidth usage rules as they are described in [RFC3611] apply to bandwidth usage rules as they are described in [RFC3611] apply to
post-repair Loss RLE reports as well. post-repair Loss RLE reports as well.
4. Session Description Protocol Signaling 4. Session Description Protocol Signaling
A new parameter is defined for the Post-repair Loss RLE Report Block A new parameter is defined for the Post-repair Loss RLE Report Block
to be used with Session Description Protocol (SDP) [RFC4566]. It has to be used with Session Description Protocol (SDP) [RFC4566] using
the following syntax within the "rtcp-xr" attribute: the Augmented Backus-Naur Form (ABNF) [RFC5234]. It has the
following syntax within the "rtcp-xr" attribute [RFC3611]:
rtcp-xr-attrib = "a=rtcp-xr:" [xr-format *(SP xr-format)] CRLF rtcp-xr-attrib = "a=rtcp-xr:" [xr-format *(SP xr-format)] CRLF
xr-format = "post-repair-loss-rle" ["=" max-size] xr-format =/ "post-repair-loss-rle" ["=" max-size]
max-size = 1*DIGIT ; maximum block size in octets max-size = 1*DIGIT ; maximum block size in octets
DIGIT = %x30-39
CRLF = %d13.10
Figure 2 Figure 2
Refer to Section 5.1 of [RFC3611] for a detailed description and the Refer to Section 5.1 of [RFC3611] for a detailed description and the
full syntax of the "rtcp-xr" attribute. full syntax of the "rtcp-xr" attribute.
5. Security Considerations 5. Security Considerations
The security considerations of [RFC3611] apply in this document as The security considerations of [RFC3611] apply in this document as
well. Additional security considerations are briefly mentioned well. Additional security considerations are briefly mentioned
skipping to change at page 9, line 36 skipping to change at page 9, line 36
Jacobson, "RTP: A Transport Protocol for Real-Time Jacobson, "RTP: A Transport Protocol for Real-Time
Applications", STD 64, RFC 3550, July 2003. Applications", STD 64, RFC 3550, July 2003.
[RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control [RFC3611] Friedman, T., Caceres, R., and A. Clark, "RTP Control
Protocol Extended Reports (RTCP XR)", RFC 3611, Protocol Extended Reports (RTCP XR)", RFC 3611,
November 2003. November 2003.
[RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session [RFC4566] Handley, M., Jacobson, V., and C. Perkins, "SDP: Session
Description Protocol", RFC 4566, July 2006. Description Protocol", RFC 4566, July 2006.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
8.2. Informative References 8.2. Informative References
[RFC5109] Li, A., "RTP Payload Format for Generic Forward Error [RFC5109] Li, A., "RTP Payload Format for Generic Forward Error
Correction", RFC 5109, December 2007. Correction", RFC 5109, December 2007.
[RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R. [RFC4588] Rey, J., Leon, D., Miyazaki, A., Varsa, V., and R.
Hakenberg, "RTP Retransmission Payload Format", RFC 4588, Hakenberg, "RTP Retransmission Payload Format", RFC 4588,
July 2006. July 2006.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
 End of changes. 8 change blocks. 
11 lines changed or deleted 13 lines changed or added

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