draft-ietf-avtcore-multiplex-guidelines-01.txt   draft-ietf-avtcore-multiplex-guidelines-02.txt 
Network Working Group M. Westerlund Network Working Group M. Westerlund
Internet-Draft B. Burman Internet-Draft B. Burman
Intended status: Informational Ericsson Intended status: Informational Ericsson
Expires: January 16, 2014 C. Perkins Expires: July 17, 2014 C. Perkins
University of Glasgow University of Glasgow
H. Alvestrand H. Alvestrand
Google Google
July 15, 2013 January 13, 2014
Guidelines for using the Multiplexing Features of RTP to Support Guidelines for using the Multiplexing Features of RTP to Support
Multiple Media Streams Multiple Media Streams
draft-ietf-avtcore-multiplex-guidelines-01 draft-ietf-avtcore-multiplex-guidelines-02
Abstract Abstract
The Real-time Transport Protocol (RTP) is a flexible protocol that The Real-time Transport Protocol (RTP) is a flexible protocol that
can be used in a wide range of applications, networks, and system can be used in a wide range of applications, networks, and system
topologies. That flexibility makes for wide applicability, but can topologies. That flexibility makes for wide applicability, but can
complicate the application design process. One particular design complicate the application design process. One particular design
question that has received much attention is how to support multiple question that has received much attention is how to support multiple
media streams in RTP. This memo discusses the available options and media streams in RTP. This memo discusses the available options and
design trade-offs, and provides guidelines on how to use the design trade-offs, and provides guidelines on how to use the
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 16, 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 3, line 24 skipping to change at page 3, line 24
8. Summary considerations and guidelines . . . . . . . . . . . . 35 8. Summary considerations and guidelines . . . . . . . . . . . . 35
8.1. Guidelines . . . . . . . . . . . . . . . . . . . . . . . 35 8.1. Guidelines . . . . . . . . . . . . . . . . . . . . . . . 35
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
10. Security Considerations . . . . . . . . . . . . . . . . . . . 37 10. Security Considerations . . . . . . . . . . . . . . . . . . . 37
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
11.1. Normative References . . . . . . . . . . . . . . . . . . 37 11.1. Normative References . . . . . . . . . . . . . . . . . . 37
11.2. Informative References . . . . . . . . . . . . . . . . . 37 11.2. Informative References . . . . . . . . . . . . . . . . . 37
Appendix A. Dismissing Payload Type Multiplexing . . . . . . . . 41 Appendix A. Dismissing Payload Type Multiplexing . . . . . . . . 41
Appendix B. Proposals for Future Work . . . . . . . . . . . . . 43 Appendix B. Proposals for Future Work . . . . . . . . . . . . . 43
Appendix C. Signalling considerations . . . . . . . . . . . . . 43 Appendix C. Signalling considerations . . . . . . . . . . . . . 43
C.1. Signalling Aspects . . . . . . . . . . . . . . . . . . . 43 C.1. Signalling Aspects . . . . . . . . . . . . . . . . . . . 44
C.1.1. Session Oriented Properties . . . . . . . . . . . . . 44 C.1.1. Session Oriented Properties . . . . . . . . . . . . . 44
C.1.2. SDP Prevents Multiple Media Types . . . . . . . . . . 45 C.1.2. SDP Prevents Multiple Media Types . . . . . . . . . . 44
C.1.3. Signalling Media Stream Usage . . . . . . . . . . . . 45 C.1.3. Signalling Media Stream Usage . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45
1. Introduction 1. Introduction
The Real-time Transport Protocol (RTP) [RFC3550] is a commonly used The Real-time Transport Protocol (RTP) [RFC3550] is a commonly used
protocol for real-time media transport. It is a protocol that protocol for real-time media transport. It is a protocol that
provides great flexibility and can support a large set of different provides great flexibility and can support a large set of different
applications. RTP has several multiplexing points designed for applications. RTP has several multiplexing points designed for
different purposes. These enable support of multiple media streams different purposes. These enable support of multiple media streams
skipping to change at page 38, line 7 skipping to change at page 38, line 7
(work in progress), July 2013. (work in progress), July 2013.
[I-D.ietf-avtcore-multi-media-rtp-session] [I-D.ietf-avtcore-multi-media-rtp-session]
Westerlund, M., Perkins, C., and J. Lennox, "Sending Westerlund, M., Perkins, C., and J. Lennox, "Sending
Multiple Types of Media in a Single RTP Session", draft- Multiple Types of Media in a Single RTP Session", draft-
ietf-avtcore-multi-media-rtp-session-03 (work in ietf-avtcore-multi-media-rtp-session-03 (work in
progress), July 2013. progress), July 2013.
[I-D.ietf-avtcore-rtp-security-options] [I-D.ietf-avtcore-rtp-security-options]
Westerlund, M. and C. Perkins, "Options for Securing RTP Westerlund, M. and C. Perkins, "Options for Securing RTP
Sessions", draft-ietf-avtcore-rtp-security-options-03 Sessions", draft-ietf-avtcore-rtp-security-options-09
(work in progress), May 2013. (work in progress), November 2013.
[I-D.ietf-avtext-multiple-clock-rates] [I-D.ietf-avtext-multiple-clock-rates]
Petit-Huguenin, M. and G. Zorn, "Support for Multiple Petit-Huguenin, M. and G. Zorn, "Support for Multiple
Clock Rates in an RTP Session", draft-ietf-avtext- Clock Rates in an RTP Session", draft-ietf-avtext-
multiple-clock-rates-09 (work in progress), April 2013. multiple-clock-rates-10 (work in progress), September
2013.
[I-D.ietf-mmusic-msid] [I-D.ietf-mmusic-msid]
Alvestrand, H., "Cross Session Stream Identification in Alvestrand, H., "Cross Session Stream Identification in
the Session Description Protocol", draft-ietf-mmusic- the Session Description Protocol", draft-ietf-mmusic-
msid-00 (work in progress), February 2013. msid-02 (work in progress), November 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.
[I-D.ietf-payload-rtp-howto] [I-D.ietf-payload-rtp-howto]
Westerlund, M., "How to Write an RTP Payload Format", Westerlund, M., "How to Write an RTP Payload Format",
draft-ietf-payload-rtp-howto-04 (work in progress), June draft-ietf-payload-rtp-howto-09 (work in progress),
2013. October 2013.
[I-D.lennox-avtcore-rtp-multi-stream] [I-D.lennox-avtcore-rtp-multi-stream]
Lennox, J., Westerlund, M., Wu, W., and C. Perkins, "RTP Lennox, J., Westerlund, M., Wu, W., and C. Perkins, "RTP
Considerations for Endpoints Sending Multiple Media Considerations for Endpoints Sending Multiple Media
Streams", draft-lennox-avtcore-rtp-multi-stream-02 (work Streams", draft-lennox-avtcore-rtp-multi-stream-02 (work
in progress), February 2013. in progress), February 2013.
[I-D.lennox-mmusic-sdp-source-selection] [I-D.lennox-mmusic-sdp-source-selection]
Lennox, J. and H. Schulzrinne, "Mechanisms for Media Lennox, J. and H. Schulzrinne, "Mechanisms for Media
Source Selection in the Session Description Protocol Source Selection in the Session Description Protocol
skipping to change at page 39, line 6 skipping to change at page 39, line 9
Synchronization sources (SSRC) in RTP Session Signaling", Synchronization sources (SSRC) in RTP Session Signaling",
draft-westerlund-avtcore-max-ssrc-02 (work in progress), draft-westerlund-avtcore-max-ssrc-02 (work in progress),
July 2012. July 2012.
[I-D.westerlund-avtcore-rtp-topologies-update] [I-D.westerlund-avtcore-rtp-topologies-update]
Westerlund, M. and S. Wenger, "RTP Topologies", draft- Westerlund, M. and S. Wenger, "RTP Topologies", draft-
westerlund-avtcore-rtp-topologies-update-02 (work in westerlund-avtcore-rtp-topologies-update-02 (work in
progress), February 2013. progress), February 2013.
[I-D.westerlund-avtcore-transport-multiplexing] [I-D.westerlund-avtcore-transport-multiplexing]
Westerlund, M. and C. Perkins, "Multiple RTP Sessions on a Westerlund, M. and C. Perkins, "Multiplexing Multiple RTP
Single Lower-Layer Transport", draft-westerlund-avtcore- Sessions onto a Single Lower-Layer Transport", draft-
transport-multiplexing-05 (work in progress), February westerlund-avtcore-transport-multiplexing-07 (work in
2013. progress), October 2013.
[I-D.westerlund-avtext-rtcp-sdes-srcname] [I-D.westerlund-avtext-rtcp-sdes-srcname]
Westerlund, M., Burman, B., and P. Sandgren, "RTCP SDES Westerlund, M., "RTCP Source Description Item SRCNAME to
Item SRCNAME to Label Individual Sources", draft- Label Individual Media Sources", draft-westerlund-avtext-
westerlund-avtext-rtcp-sdes-srcname-02 (work in progress), rtcp-sdes-srcname-03 (work in progress), October 2013.
October 2012.
[RFC2198] Perkins, C., Kouvelas, I., Hodson, O., Hardman, V., [RFC2198] Perkins, C., Kouvelas, I., Hodson, O., Hardman, V.,
Handley, M., Bolot, J., Vega-Garcia, A., and S. Fosse- Handley, M., Bolot, J., Vega-Garcia, A., and S. Fosse-
Parisis, "RTP Payload for Redundant Audio Data", RFC 2198, Parisis, "RTP Payload for Redundant Audio Data", RFC 2198,
September 1997. September 1997.
[RFC2205] Braden, B., Zhang, L., Berson, S., Herzog, S., and S. [RFC2205] Braden, B., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", RFC 2205, September 1997. Functional Specification", RFC 2205, September 1997.
 End of changes. 14 change blocks. 
22 lines changed or deleted 22 lines changed or added

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