draft-ietf-avtcore-rtp-topologies-update-08.txt   draft-ietf-avtcore-rtp-topologies-update-09.txt 
Network Working Group M. Westerlund Network Working Group M. Westerlund
Internet-Draft Ericsson Internet-Draft Ericsson
Obsoletes: 5117 (if approved) S. Wenger Obsoletes: 5117 (if approved) S. Wenger
Intended status: Informational Vidyo Intended status: Informational Vidyo
Expires: December 19, 2015 June 17, 2015 Expires: January 1, 2016 June 30, 2015
RTP Topologies RTP Topologies
draft-ietf-avtcore-rtp-topologies-update-08 draft-ietf-avtcore-rtp-topologies-update-09
Abstract Abstract
This document discusses point to point and multi-endpoint topologies This document discusses point to point and multi-endpoint topologies
used in Real-time Transport Protocol (RTP)-based environments. In used in Real-time Transport Protocol (RTP)-based environments. In
particular, centralized topologies commonly employed in the video particular, centralized topologies commonly employed in the video
conferencing industry are mapped to the RTP terminology. conferencing industry are mapped to the RTP terminology.
This document is updated with additional topologies and replaces RFC This document is updated with additional topologies and replaces RFC
5117. 5117.
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 December 19, 2015. This Internet-Draft will expire on January 1, 2016.
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
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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.1. Glossary . . . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Glossary . . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Definitions related to RTP grouping taxonomy . . . . . . 4 2.2. Definitions related to RTP grouping taxonomy . . . . . . 4
3. Topologies . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Topologies . . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Point to Point . . . . . . . . . . . . . . . . . . . . . 5 3.1. Point to Point . . . . . . . . . . . . . . . . . . . . . 5
3.2. Point to Point via Middlebox . . . . . . . . . . . . . . 6 3.2. Point to Point via Middlebox . . . . . . . . . . . . . . 6
3.2.1. Translators . . . . . . . . . . . . . . . . . . . . . 6 3.2.1. Translators . . . . . . . . . . . . . . . . . . . . . 6
3.2.2. Back to Back RTP sessions . . . . . . . . . . . . . . 10 3.2.2. Back to Back RTP sessions . . . . . . . . . . . . . . 10
3.3. Point to Multipoint Using Multicast . . . . . . . . . . . 11 3.3. Point to Multipoint Using Multicast . . . . . . . . . . . 11
3.3.1. Any Source Multicast (ASM) . . . . . . . . . . . . . 11 3.3.1. Any Source Multicast (ASM) . . . . . . . . . . . . . 11
3.3.2. Source Specific Multicast (SSM) . . . . . . . . . . . 12 3.3.2. Source Specific Multicast (SSM) . . . . . . . . . . . 13
3.3.3. SSM with Local Unicast Resources . . . . . . . . . . 14 3.3.3. SSM with Local Unicast Resources . . . . . . . . . . 15
3.4. Point to Multipoint Using Mesh . . . . . . . . . . . . . 16 3.4. Point to Multipoint Using Mesh . . . . . . . . . . . . . 16
3.5. Point to Multipoint Using the RFC 3550 Translator . . . . 19 3.5. Point to Multipoint Using the RFC 3550 Translator . . . . 19
3.5.1. Relay - Transport Translator . . . . . . . . . . . . 19 3.5.1. Relay - Transport Translator . . . . . . . . . . . . 19
3.5.2. Media Translator . . . . . . . . . . . . . . . . . . 20 3.5.2. Media Translator . . . . . . . . . . . . . . . . . . 20
3.6. Point to Multipoint Using the RFC 3550 Mixer Model . . . 21 3.6. Point to Multipoint Using the RFC 3550 Mixer Model . . . 21
3.6.1. Media Mixing Mixer . . . . . . . . . . . . . . . . . 23 3.6.1. Media Mixing Mixer . . . . . . . . . . . . . . . . . 23
3.6.2. Media Switching . . . . . . . . . . . . . . . . . . . 26 3.6.2. Media Switching . . . . . . . . . . . . . . . . . . . 26
3.7. Selective Forwarding Middlebox . . . . . . . . . . . . . 28 3.7. Selective Forwarding Middlebox . . . . . . . . . . . . . 28
3.8. Point to Multipoint Using Video Switching MCUs . . . . . 32 3.8. Point to Multipoint Using Video Switching MCUs . . . . . 32
3.9. Point to Multipoint Using RTCP-Terminating MCU . . . . . 33 3.9. Point to Multipoint Using RTCP-Terminating MCU . . . . . 33
skipping to change at page 3, line 35 skipping to change at page 3, line 35
properties. properties.
This document also codifies new multipoint architectures that have This document also codifies new multipoint architectures that have
recently been introduced and which were not anticipated in RFC 5117, recently been introduced and which were not anticipated in RFC 5117,
thus this document replaces [RFC5117]. These architectures use thus this document replaces [RFC5117]. These architectures use
scalable video coding and simulcasting, and their associated scalable video coding and simulcasting, and their associated
centralized units are referred to as Selective Forwarding Units centralized units are referred to as Selective Forwarding Units
(SFU). This codification provides a common information basis for (SFU). This codification provides a common information basis for
future discussion and specification work. future discussion and specification work.
The new topologies are Point to Point via Middlebox (Section 3.2),
Source Specific Multicast (Section 3.3.2), SSM with Local Unicast
Resources (Section 3.3.3), Point to Multipoint Using Mesh
(Section 3.4), Selective Forwarding Middlebox (Section 3.7), and
Split Component Terminal (Section 3.10). The Point to Multipoint
Using the RFC 3550 Mixer Model (Section 3.6) has been significantly
expanded and cover two different versions namely Media Mixing Mixer
(Section 3.6.1), and Media Switching (Section 3.6.2).
The document's attempt to clarify and explain sections of the Real- The document's attempt to clarify and explain sections of the Real-
time Transport Protocol (RTP) spec [RFC3550] is informal. It is not time Transport Protocol (RTP) spec [RFC3550] is informal. It is not
intended to update or change what is normatively specified within RFC intended to update or change what is normatively specified within RFC
3550. 3550.
2. Definitions 2. Definitions
2.1. Glossary 2.1. Glossary
ASM: Any Source Multicast ASM: Any Source Multicast
skipping to change at page 44, line 33 skipping to change at page 44, line 33
7. IANA Considerations 7. IANA Considerations
This document makes no request of IANA. This document makes no request of IANA.
Note to RFC Editor: this section may be removed on publication as an Note to RFC Editor: this section may be removed on publication as an
RFC. RFC.
8. Acknowledgements 8. Acknowledgements
The authors would like to thank Mark Baugher, Bo Burman, Umesh The authors would like to thank Mark Baugher, Bo Burman, Ben
Chandra, Alex Eleftheriadis, Roni Even, Ladan Gharai, Geoff Hunt, Campbell, Umesh Chandra, Alex Eleftheriadis, Roni Even, Ladan Gharai,
Keith Lantz, Jonathan Lennox, Scarlet Liuyan, Suhas Nandakumar, Colin Geoff Hunt, Suresh Krishnan, Keith Lantz, Jonathan Lennox, Scarlet
Perkins, and Dan Wing for their help in reviewing and improving this Liuyan, Suhas Nandakumar, Colin Perkins, and Dan Wing for their help
document. in reviewing and improving this document.
9. References 9. References
9.1. Normative References 9.1. Normative References
[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.
[RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey, [RFC4585] Ott, J., Wenger, S., Sato, N., Burmeister, C., and J. Rey,
 End of changes. 7 change blocks. 
12 lines changed or deleted 21 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/