draft-ietf-avtcore-rtp-topologies-update-09.txt   draft-ietf-avtcore-rtp-topologies-update-10.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: January 1, 2016 June 30, 2015 Expires: January 3, 2016 July 2, 2015
RTP Topologies RTP Topologies
draft-ietf-avtcore-rtp-topologies-update-09 draft-ietf-avtcore-rtp-topologies-update-10
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 January 1, 2016. This Internet-Draft will expire on January 3, 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
skipping to change at page 3, line 41 skipping to change at page 3, line 41
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), The new topologies are Point to Point via Middlebox (Section 3.2),
Source Specific Multicast (Section 3.3.2), SSM with Local Unicast Source Specific Multicast (Section 3.3.2), SSM with Local Unicast
Resources (Section 3.3.3), Point to Multipoint Using Mesh Resources (Section 3.3.3), Point to Multipoint Using Mesh
(Section 3.4), Selective Forwarding Middlebox (Section 3.7), and (Section 3.4), Selective Forwarding Middlebox (Section 3.7), and
Split Component Terminal (Section 3.10). The Point to Multipoint Split Component Terminal (Section 3.10). The Point to Multipoint
Using the RFC 3550 Mixer Model (Section 3.6) has been significantly Using the RFC 3550 Mixer Model (Section 3.6) has been significantly
expanded and cover two different versions namely Media Mixing Mixer expanded to cover two different versions namely Media Mixing Mixer
(Section 3.6.1), and Media Switching (Section 3.6.2). (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
 End of changes. 4 change blocks. 
4 lines changed or deleted 4 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/