draft-ietf-straw-b2bua-rtcp-05.txt   draft-ietf-straw-b2bua-rtcp-06.txt 
STRAW Working Group L. Miniero STRAW Working Group L. Miniero
Internet-Draft Meetecho Internet-Draft Meetecho
Intended status: Standards Track S. Garcia Murillo Intended status: Standards Track S. Garcia Murillo
Expires: September 25, 2015 Medooze Expires: October 18, 2015 Medooze
V. Pascual V. Pascual
Quobis Quobis
March 24, 2015 April 16, 2015
Guidelines to support RTCP end-to-end in Back-to-Back User Agents Guidelines to support RTCP end-to-end in Back-to-Back User Agents
(B2BUAs) (B2BUAs)
draft-ietf-straw-b2bua-rtcp-05 draft-ietf-straw-b2bua-rtcp-06
Abstract Abstract
SIP Back-to-Back User Agents (B2BUAs) are often envisaged to also be SIP Back-to-Back User Agents (B2BUAs) are often envisaged to also be
on the media path, rather than just intercepting signalling. This on the media path, rather than just intercepting signalling. This
means that B2BUAs often implement an RTP/RTCP stack as well, whether means that B2BUAs often implement an RTP/RTCP stack as well, whether
to act as media transcoders or to just passthrough the media to act as media transcoders or to just passthrough the media
themselves, thus leading to separate multimedia sessions that the themselves, thus leading to separate multimedia sessions that the
B2BUA correlates and bridges together. If not disciplined, though, B2BUA correlates and bridges together. If not disciplined, though,
this behaviour can severely impact the communication experience, this behaviour can severely impact the communication experience,
skipping to change at page 1, line 46 skipping to change at page 1, line 46
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on September 25, 2015. This Internet-Draft will expire on October 18, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 7, line 39 skipping to change at page 7, line 39
the base RTP sequence number when forwarding RTP packets, then the base RTP sequence number when forwarding RTP packets, then
this change needs to be properly addressed in the 'extended this change needs to be properly addressed in the 'extended
highest sequence number received' field in the Report Blocks. highest sequence number received' field in the Report Blocks.
RR: [RFC3550] RR: [RFC3550]
The same guidelines given for SR apply for RR as well. The same guidelines given for SR apply for RR as well.
SDES: [RFC3550] SDES: [RFC3550]
If the B2BUA has changed any SSRC in any direction, it MUST update If the B2BUA has changed any SSRC in any direction, it MUST update
the SSRC-related information in all the chunks in the incoming the SSRC-related information in all the chunks in the incoming
SDES packet before forwarding it. SDES packet before forwarding it. In case the SSRC in any of the
chunks is changed, the related CNAME item SHOULD be updated as
well in order to avoid potential CNAME collisions, especially if
the RFC 3550 CNAME algorithm is used.
BYE: [RFC3550] BYE: [RFC3550]
If the B2BUA has changed any SSRC in any direction, it MUST update If the B2BUA has changed any SSRC in any direction, it MUST update
the SSRC in the BYE message. the SSRC in the BYE message.
APP: [RFC3550] APP: [RFC3550]
If the B2BUA has changed any SSRC in any direction, it MUST update If the B2BUA has changed any SSRC in any direction, it MUST update
the SSRC in the APP message. Should the B2BUA be aware of any the SSRC in the APP message. Should the B2BUA be aware of any
specific APP message format that contains additional information specific APP message format that contains additional information
related to SSRCs, it SHOULD update them as well. related to SSRCs, it SHOULD update them as well.
skipping to change at page 12, line 43 skipping to change at page 12, line 46
for a user, may lead to missing information to its peer, who may end for a user, may lead to missing information to its peer, who may end
up increasing the encoder bitrate up to a point where the user with up increasing the encoder bitrate up to a point where the user with
poor connectivity will inevitably be choked by an amount of data it poor connectivity will inevitably be choked by an amount of data it
cannot process. This scenario may as such result in what looks like cannot process. This scenario may as such result in what looks like
a Denial of Service (DOS) attack towards the user. a Denial of Service (DOS) attack towards the user.
7. Change Summary 7. Change Summary
Note to RFC Editor: Please remove this whole section. Note to RFC Editor: Please remove this whole section.
The following are the major changes between the 05 and the 06
versions of the draft:
o Addressed comment by Colin Perkins on the management of CNAME
items in SDES.
The following are the major changes between the 04 and the 05 The following are the major changes between the 04 and the 05
versions of the draft: versions of the draft:
o Clarified behaviour when SSRC is zero. o Clarified behaviour when SSRC is zero.
o Fixed a couple of nits found by the Idnits tool. o Fixed a couple of nits found by the Idnits tool.
The following are the major changes between the 03 and the 04 The following are the major changes between the 03 and the 04
versions of the draft: versions of the draft:
skipping to change at page 14, line 49 skipping to change at page 15, line 10
[RFC7092] Kaplan, H. and V. Pascual, "A Taxonomy of Session [RFC7092] Kaplan, H. and V. Pascual, "A Taxonomy of Session
Initiation Protocol (SIP) Back-to-Back User Agents", RFC Initiation Protocol (SIP) Back-to-Back User Agents", RFC
7092, December 2013. 7092, December 2013.
[RFC5117] Westerlund, M. and S. Wenger, "RTP Topologies", RFC 5117, [RFC5117] Westerlund, M. and S. Wenger, "RTP Topologies", RFC 5117,
January 2008. January 2008.
[I-D.ietf-avtcore-rtp-topologies-update] [I-D.ietf-avtcore-rtp-topologies-update]
Westerlund, M. and S. Wenger, "RTP Topologies", draft- Westerlund, M. and S. Wenger, "RTP Topologies", draft-
ietf-avtcore-rtp-topologies-update-06 (work in progress), ietf-avtcore-rtp-topologies-update-07 (work in progress),
March 2015. April 2015.
[I-D.ietf-avtext-rtp-grouping-taxonomy] [I-D.ietf-avtext-rtp-grouping-taxonomy]
Lennox, J., Gross, K., Nandakumar, S., and G. Salgueiro, Lennox, J., Gross, K., Nandakumar, S., and G. Salgueiro,
"A Taxonomy of Grouping Semantics and Mechanisms for Real- "A Taxonomy of Grouping Semantics and Mechanisms for Real-
Time Transport Protocol (RTP) Sources", draft-ietf-avtext- Time Transport Protocol (RTP) Sources", draft-ietf-avtext-
rtp-grouping-taxonomy-06 (work in progress), March 2015. rtp-grouping-taxonomy-06 (work in progress), March 2015.
[I-D.alvestrand-rmcat-remb] [I-D.alvestrand-rmcat-remb]
Alvestrand, H., "RTCP message for Receiver Estimated Alvestrand, H., "RTCP message for Receiver Estimated
Maximum Bitrate", draft-alvestrand-rmcat-remb-03 (work in Maximum Bitrate", draft-alvestrand-rmcat-remb-03 (work in
 End of changes. 7 change blocks. 
7 lines changed or deleted 16 lines changed or added

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