draft-ietf-avtcore-rtp-multi-stream-01.txt   draft-ietf-avtcore-rtp-multi-stream-02.txt 
AVTCORE J. Lennox AVTCORE J. Lennox
Internet-Draft Vidyo Internet-Draft Vidyo
Updates: 3550 (if approved) M. Westerlund Updates: 3550 (if approved) M. Westerlund
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: January 12, 2014 Q. Wu Expires: July 17, 2014 Q. Wu
Huawei Huawei
C. Perkins C. Perkins
University of Glasgow University of Glasgow
July 11, 2013 January 13, 2014
Sending Multiple Media Streams in a Single RTP Session Sending Multiple Media Streams in a Single RTP Session
draft-ietf-avtcore-rtp-multi-stream-01 draft-ietf-avtcore-rtp-multi-stream-02
Abstract Abstract
This document expands and clarifies the behavior of the Real-Time This document expands and clarifies the behavior of the Real-Time
Transport Protocol (RTP) endpoints when they are sending multiple Transport Protocol (RTP) endpoints when they are sending multiple
media streams in a single RTP session. In particular, issues media streams in a single RTP session. In particular, issues
involving Real-Time Transport Control Protocol (RTCP) messages are involving RTP Control Protocol (RTCP) messages are described.
described.
This document updates RFC 3550 in regards to handling of multiple This document updates RFC 3550 in regards to handling of multiple
SSRCs per endpoint in RTP sessions. SSRCs per endpoint in RTP sessions.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 January 12, 2014. This Internet-Draft will expire on July 17, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 28 skipping to change at page 2, line 25
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Use Cases For Multi-Stream Endpoints . . . . . . . . . . . . 3 3. Use Cases For Multi-Stream Endpoints . . . . . . . . . . . . 3
3.1. Multiple-Capturer Endpoints . . . . . . . . . . . . . . . 3 3.1. Multiple-Capturer Endpoints . . . . . . . . . . . . . . . 3
3.2. Multi-Media Sessions . . . . . . . . . . . . . . . . . . 3 3.2. Multi-Media Sessions . . . . . . . . . . . . . . . . . . 3
3.3. Multi-Stream Mixers . . . . . . . . . . . . . . . . . . . 4 3.3. Multi-Stream Mixers . . . . . . . . . . . . . . . . . . . 4
4. Multi-Stream Endpoint RTP Media Recommendations . . . . . . . 4 4. Multi-Stream Endpoint RTP Media Recommendations . . . . . . . 4
5. Multi-Stream Endpoint RTCP Recommendations . . . . . . . . . 4 5. Multi-Stream Endpoint RTCP Recommendations . . . . . . . . . 4
5.1. RTCP Reporting Requirement . . . . . . . . . . . . . . . 5 5.1. RTCP Reporting Requirement . . . . . . . . . . . . . . . 5
5.2. Initial Reporting Interval . . . . . . . . . . . . . . . 5 5.2. Initial Reporting Interval . . . . . . . . . . . . . . . 5
5.3. Compound RTCP Packets . . . . . . . . . . . . . . . . . . 5 5.3. Compound RTCP Packets . . . . . . . . . . . . . . . . . . 5
6. RTCP Considerations for Streams with Disparate Rates . . . . 7 6. RTCP Considerations for Streams with Disparate Rates . . . . 6
6.1. Timing out SSRCs . . . . . . . . . . . . . . . . . . . . 8 6.1. Timing out SSRCs . . . . . . . . . . . . . . . . . . . . 8
6.2. Tuning RTCP transmissions . . . . . . . . . . . . . . . . 9 6.2. Tuning RTCP transmissions . . . . . . . . . . . . . . . . 8
7. Security Considerations . . . . . . . . . . . . . . . . . . . 11 7. Security Considerations . . . . . . . . . . . . . . . . . . . 11
8. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 12 8. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
10.1. Normative References . . . . . . . . . . . . . . . . . . 12 10.1. Normative References . . . . . . . . . . . . . . . . . . 12
10.2. Informative References . . . . . . . . . . . . . . . . . 13 10.2. Informative References . . . . . . . . . . . . . . . . . 12
Appendix A. Changes From Earlier Versions . . . . . . . . . . . 14 Appendix A. Changes From Earlier Versions . . . . . . . . . . . 13
A.1. Changes From WG Draft -00 . . . . . . . . . . . . . . . . 14 A.1. Changes From WG Draft -00 . . . . . . . . . . . . . . . . 13
A.2. Changes From Individual Draft -02 . . . . . . . . . . . . 14 A.2. Changes From Individual Draft -02 . . . . . . . . . . . . 13
A.3. Changes From Individual Draft -01 . . . . . . . . . . . . 14 A.3. Changes From Individual Draft -01 . . . . . . . . . . . . 14
A.4. Changes From Individual Draft -00 . . . . . . . . . . . . 14 A.4. Changes From Individual Draft -00 . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
At the time The Real-Time Transport Protocol (RTP) [RFC3550] was At the time The Real-Time Transport Protocol (RTP) [RFC3550] was
originally written, and for quite some time after, endpoints in RTP originally written, and for quite some time after, endpoints in RTP
sessions typically only transmitted a single media stream per RTP sessions typically only transmitted a single media stream per RTP
session, where separate RTP sessions were typically used for each session, where separate RTP sessions were typically used for each
distinct media type. distinct media type.
Recently, however, a number of scenarios have emerged (discussed Recently, however, a number of scenarios have emerged (discussed
skipping to change at page 12, line 41 skipping to change at page 12, line 12
No IANA actions needed. No IANA actions needed.
10. References 10. References
10.1. Normative References 10.1. Normative References
[I-D.ietf-avtcore-6222bis] [I-D.ietf-avtcore-6222bis]
Begen, A., Perkins, C., Wing, D., and E. Rescorla, Begen, A., Perkins, C., Wing, D., and E. Rescorla,
"Guidelines for Choosing RTP Control Protocol (RTCP) "Guidelines for Choosing RTP Control Protocol (RTCP)
Canonical Names (CNAMEs)", draft-ietf-avtcore-6222bis-04 Canonical Names (CNAMEs)", draft-ietf-avtcore-6222bis-06
(work in progress), June 2013. (work in progress), July 2013.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V. [RFC3550] Schulzrinne, H., Casner, S., Frederick, R., and V.
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.
[RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K. [RFC3711] Baugher, M., McGrew, D., Naslund, M., Carrara, E., and K.
Norrman, "The Secure Real-time Transport Protocol (SRTP)", Norrman, "The Secure Real-time Transport Protocol (SRTP)",
skipping to change at page 13, line 25 skipping to change at page 12, line 42
Real-time Transport Control Protocol (RTCP)-Based Feedback Real-time Transport Control Protocol (RTCP)-Based Feedback
(RTP/SAVPF)", RFC 5124, February 2008. (RTP/SAVPF)", RFC 5124, February 2008.
[RFC5506] Johansson, I. and M. Westerlund, "Support for Reduced-Size [RFC5506] Johansson, I. and M. Westerlund, "Support for Reduced-Size
Real-Time Transport Control Protocol (RTCP): Opportunities Real-Time Transport Control Protocol (RTCP): Opportunities
and Consequences", RFC 5506, April 2009. and Consequences", RFC 5506, April 2009.
10.2. Informative References 10.2. Informative References
[I-D.ietf-avtcore-multi-media-rtp-session] [I-D.ietf-avtcore-multi-media-rtp-session]
Westerlund, M., Perkins, C., and J. Lennox, "Multiple Westerlund, M., Perkins, C., and J. Lennox, "Sending
Media Types in an RTP Session", draft-ietf-avtcore-multi- Multiple Types of Media in a Single RTP Session", draft-
media-rtp-session-02 (work in progress), February 2013. ietf-avtcore-multi-media-rtp-session-03 (work in
progress), July 2013.
[I-D.ietf-avtcore-rtp-multi-stream-optimisation] [I-D.ietf-avtcore-rtp-multi-stream-optimisation]
Lennox, J., Westerlund, M., Wu, Q., and C. Perkins, Lennox, J., Westerlund, M., Wu, Q., and C. Perkins,
"Sending Multiple Media Streams in a Single RTP Session: "Sending Multiple Media Streams in a Single RTP Session:
Grouping RTCP Reception Statistics and Other Feedback ", Grouping RTCP Reception Statistics and Other Feedback ",
draft-ietf-avtcore-rtp-multi-stream-optimisation-00 (work draft-ietf-avtcore-rtp-multi-stream-optimisation-00 (work
in progress), July 2013. in progress), July 2013.
[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-00 (work in progress), ietf-avtcore-rtp-topologies-update-01 (work in progress),
April 2013. October 2013.
[I-D.ietf-clue-framework] [I-D.ietf-clue-framework]
Duckworth, M., Pepperell, A., and S. Wenger, "Framework Duckworth, M., Pepperell, A., and S. Wenger, "Framework
for Telepresence Multi-Streams", draft-ietf-clue- for Telepresence Multi-Streams", draft-ietf-clue-
framework-10 (work in progress), May 2013. framework-12 (work in progress), October 2013.
[I-D.ietf-mmusic-sdp-bundle-negotiation] [I-D.ietf-mmusic-sdp-bundle-negotiation]
Holmberg, C., Alvestrand, H., and C. Jennings, Holmberg, C., Alvestrand, H., and C. Jennings,
"Multiplexing Negotiation Using Session Description "Multiplexing Negotiation Using Session Description
Protocol (SDP) Port Numbers", draft-ietf-mmusic-sdp- Protocol (SDP) Port Numbers", draft-ietf-mmusic-sdp-
bundle-negotiation-04 (work in progress), June 2013. bundle-negotiation-05 (work in progress), October 2013.
[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, November Protocol Extended Reports (RTCP XR)", RFC 3611, November
2003. 2003.
[RFC3830] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K. [RFC3830] Arkko, J., Carrara, E., Lindholm, F., Naslund, M., and K.
Norrman, "MIKEY: Multimedia Internet KEYing", RFC 3830, Norrman, "MIKEY: Multimedia Internet KEYing", RFC 3830,
August 2004. August 2004.
Appendix A. Changes From Earlier Versions Appendix A. Changes From Earlier Versions
 End of changes. 16 change blocks. 
25 lines changed or deleted 25 lines changed or added

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