Roni Even Jonathan Lennox Mapping RTP streams to CLUE media captures draft-even-clue-rtp-mapping-03 IETF-84.

Slides:



Advertisements
Similar presentations
CLUE REQUIREMENTS IETF 80 Allyn Romanow
Advertisements

RTP/RTCP multimedia protocols for the Internet Center for Software Development CSD, BITS - Pilani CopyRight:
H. 323 Chapter 4.
© 2004, NexTone Communications. All rights reserved. Introduction to H.323.
24/08/2005 IP Telephony1 Guided by: Presented by: Dr.S.K.Ghosh Nitesh Jain 05IT6008 M.Tech 1 st year.
RTP Payload Format for Multiple Flows FEC draft-peck-fecframe-rtp-mf-00 Orly Peck, RADVISION IETF 76 – November 2009.
Multimedia Streaming Protocols. signalling and control protocols protocols conveying session setup information and VCR-like commands (play, pause, mute,
RTP: A Transport Protocol for Real-Time Applications Provides end-to-end delivery services for data with real-time characteristics, such as interactive.
SIPREC MSRP Recording ( draft-yan-siprec-msrp-recording-01 ) IETF 90, July 25, 2014 Authors: Michael Yan, Paul Kyzivat.
1 SIPREC Protocol (draft-ietf-siprec-protocol-06) August 3, 2012 IETF 84 Authors: L. Portman, H. Lum, A. Johnston, A. Hutton, C. Eckel.
Real-time Transport Protocol (RTP) Recommendations for SIPREC (draft-eckel-siprec-rtp-rec-01) Charles Eckel IETF-81, Quebec City, July.
Internet Telephony Helen J. Wang Network Reading Group, Jan 27, 99 Acknowledgement: Jimmy, Bhaskar.
CSc 461/561 CSc 461/561 Multimedia Systems Part C: 1. RTP/RTCP.
Martin Dolly, Gary Munson AT&T Labs James Rafferty Cantata Roni Even Polycom draft-dolly-xcon-mediacntrlframe-03.txt draft-even-media-server-req-02.txt.
RTP/RTCP(RFC 1889) Real-time transport protocol (RTP) is the de facto standard media transport protocol in the Internet Media transport: audio, vedio,
RTP Multiplexing draft-rosenberg-rtcweb-rtpmux Jonathan + {Rosenberg, Lennox}
Introduction to SDP Issues. Content Background Goals SDP Primer RTP Primer Use cases “New” Functionalities in SDP Multiple RTP Streams in SDP Decision.
Allyn Romanow Mark Duckworth ) Andy Pepperell Brian Baldino
Slide title 70 pt CAPITALS Slide subtitle minimum 30 pt RTP usage in WebRTC Part 1: API and Topologies draft-ietf-rtcweb-rtp-usage-03 RTCWEB Interim June.
T ELEPRESENCE T UTORI A L July 30, Introduction to Telepresence 1 Introduction to the IETF CLUE work 2 Telepresence scenarios 3 CLUE FrameworkCLUE.
CS 218 F 2003 Nov 3 lecture:  Streaming video/audio  Adaptive encoding (eg, layered encoding)  TCP friendliness References: r J. Padhye, V.Firoiu, D.
CIS679: RTP and RTCP r Review of Last Lecture r Streaming from Web Server r RTP and RTCP.
Draft-rosenberg-mmusic-sdp-offer-answer-00.txt Jonathan Rosenberg dynamicsoft IETF 52.
Protocols Suite By: Aleksandr Gidenko. What is H.323? H.323 is a multimedia conferencing protocol for voice, video and data over IP-based networks that.
Draft-romanow-clue-call-flow-02 Allyn Romanow Rob Hansen Arun Krishna.
CLUE Framework Status and Issues IETF89 - London March 5, 2014 Mark Duckworth draft-ietf-clue-framework-14 1.
Computer Networks: Multimedia Applications Ivan Marsic Rutgers University Chapter 3 – Multimedia & Real-time Applications.
Audio/Video Transport Extensions (AVTEXT). Administrivia Notetakers? Jabber scribe? Jabber Chat Room
Foreleser: Carsten Griwodz
Slide title minimum 48 pt Slide subtitle minimum 30 pt RTP Multiple Stream Sessions and Simulcast draft-westerlund-avtcore-multistream-and-simulcast-00.
CLUE Framework Issues CLUE virtual interim meeting Jan 27, 2014 Mark Duckworth draft-ietf-clue-framework-13 1.
CLUE MCU use cases Espen Berger February. 15 – 16, 2012.
Real Time Protocol (RTP) 김 준
Streaming Media Control n The protocol components of the streaming n RTP/RTCP n RVSP n Real-Time Streaming Protocol (RTSP)
Slide title minimum 48 pt Slide subtitle minimum 30 pt RTCWEB Terminology A Discussion of relation between RTCWEB Media Protocol Terminology and the PeerConnection.
Real-time Transport Protocol (RTP) Recommendations for SIPREC (draft-eckel-siprec-rtp-rec-02) Charles Eckel SIPREC Virtual Interim.
Session Recording (SIPREC) Protocol (draft-ietf-siprec-protocol-09) Leon Portman Henry Lum
VAD in CLUE Andy Pepperell. Need for VAD Want middle boxes to be able to switch video / audio without having to decode all audio – Not all MCUs are fully.
RTP – Real-time Transport Protocol Elbert Tsay, Brad Bargabus, Patrick Lim, Henry Quach The Five Packeteers (minus 1  )
SIP and SIPPING WGsMay, IETF Interim Meeting Orit levin Conferencing Requirements for SIP Based Applications.
Christian Groves Describing Captures in CLUE and relation to multipoint conferencing draft-groves-clue-multi-content-00 CLUE Interim meeting (09/13)
CLUE RTP usage Andy Pepperell
PTCL Training & Development1 H.323 Terminals Client end points on the network IP phones, PCs having own OS Terminals running an H.323 protocols and the.
New stuff People were interested in more detailed spatial information about media captures Added area of capture and point of capture attributes Also addresses.
CLUE Overview and Architecture IETF 82 CLUE ad hoc meeting Allyn Romanow
A RTCP-based Retransmission Protocol for Unicast RTP Streaming Multimedia draft-podolsky-avt-rtprx-00.txt Matthew Podolsky, Koichi Yano, and Steven McCanne.
1 Internet Telephony: Architecture and Protocols an IETF Perspective Authors:Henning Schulzrinne, Jonathan Rosenberg. Presenter: Sambhrama Mundkur.
RTP Usage for CLUE draft-lennox-clue-rtp-usage-02 Clue WG, IETF 83, 27 March 2012 Jonathan Lennox Allyn Romanow
The Session Initiation Protocol - SIP
RTP Functionalities for RTCWEB A combined view from the authors of draft-cbran-rtcweb-media-00 draft-cbran-rtcweb-media-00 draft-perkins-rtcweb-rtp-usage-02.
RTP Usage for CLUE IETF 82 – 14 November 2011 Jonathan Lennox Allyn Romanow Paul Witty.
CLUE Framework 01 – comments and issues Interim meeting October 2011 Roni Even.
SIPREC Conference Recording (draft-kyzivat-siprec-conference-use-cases-00) IETF 87, November 4, 2013 Authors: Michael Yan, Paul Kyzivat, Simon Romano.
Allyn Romanow Stephen Botzko Robert Hansen Signaling Requirements for implementing the.
Telepresence Interoperability Protocol (TIP) Overview for IMTC SuperOp 2010 Workshop 1 Allyn Romanow Cisco Telepresence Systems Business Unit (TSBU) 15.
CLUE Framework IETF 88 – Nov 8, 2013 Mark Duckworth draft-ietf-clue-framework-12 draft-groves-clue-multi-content-00 draft-duckworth-clue-switching-example-01.
RTP Taxonomy & draft-lennox-raiarea-rtp-grouping-taxonomy-03 IETF 88 1.
Codec Control for RTCWEB
VoIP ALLPPT.com _ Free PowerPoint Templates, Diagrams and Charts.
Klara Nahrstedt Spring 2012
RTCP Feedback Message for Image Control
CLUE WG Interim Meeting San Jose, CA Sept , 2012
Klara Nahrstedt Spring 2009
RTP: A Transport Protocol for Real-Time Applications
Audio/Video Transport Working Group
VOICE AND VIDEO OVER IP VOIP, RTP, RSVP.
CLUE definitions Stephan Wenger.
RTP – Real-time Transport Protocol
Design and Implementation of Audio/Video Collaboration System Based on Publish/subscribe Event Middleware CTS04 San Diego 19 January 2004 PTLIU Laboratory.
SDP Media Loopback draft-hedayat-media-loopback-01.txt
Presentation transcript:

Roni Even Jonathan Lennox Mapping RTP streams to CLUE media captures draft-even-clue-rtp-mapping-03 IETF-84

Introduction CLUE framework Defines Media Captures that provide information about the semantics of streams, like spatial relation Allows consumers to request specific Captures RTP is used to transmit the requested streams SDP is used to negotiate the characteristics of codecs and connections over which streams are sent Need to map between media captures and actual streams sent over RTP Try to avoid duplication of information between SDP and CLUE 2

Assumptions CLUE systems support different topologies Point to point Sender source is one to one mapped to RTP streams Media mixers Senders’ sources are visible as Contributing sources (CSRCs). Media switching mixers Sender’s source is visible as a Contributing source (CSRC). Source projection mixers Each media source is one to one mapped to a SSRC in Participant’s RTP session. 3

RTP/RTCP behavior Topologies show two major behaviors: Mixer either uses source SSRC or uses its own SSRC when forwarding RTP packets. One RTP session and source information is in SSRC or CSRC. Mixer terminates RTCP from source, creating separate RTP sessions with peers. The source information is not available in RTCP but may be available using out of band means, e.g. SIP conference event package (RFC4575). 4

SSRC behavior Topologies show two major SSRC behaviors: Static SSRCs SSRCs assigned by MCU/mixer. A static SSRC can be used for each CLUE media Capture. Source information may be conveyed in CSRC. Dynamic SSRCs SSRCs of the original source relayed by the Mixer/MCU to participants. Mapping between SSRCs and Media Captures changes with every source switch. 5

Examples Video switching MCU Media Mixer behavior for audio. Media switching Mixer or a Source-Projection Mixer for video. The audio will be static source, whereas the video could be dynamic. Endpoint may send the same sources both for static and dynamic captures. Endpoint can provide both three cameras (VC0, VC1, and VC2) for left, center, and right views, as well as a switched view (VC3) of the loudest panel. Using Source-Projection Mixer topology for VC3 VC0, VC1, VC2 have static mapping. 6

Mapping options (1) Advertisements are created by the next peer MCU / Mixer in multipoint TP endpoint in point to point call Use a “capture ID” SDP source attribute. For each SSRC and media capture. This is a static mapping. Use RTP Header extension as in draft-lennox-rtp-usage | ID=1 | length=4 | Capture ID : : |

Mapping options (2) RTP header extension sent with every packet (or with selected packets) of a dynamic mapped RTP stream. The RTP header extension is provided by the source for point to point calls and by the middle box in Multipoint case. The same Capture-ID value can be used when using static mapping in SDP and for dynamic mapping in the RTP header extension. 8

Proposal Media mixers and Media Switching mixers are common in products Source projection mixers are also used in products. Allow more flexibility for switched captures Products may have mixed behavior for static and dynamic SSRC support Mapping static SSRCs to CLUE Media Captures - adding the RTP header extension for each packet is not necessary. Endpoints MUST support, as receivers, both the static declaration of capture encoding SSRCs, and the RTP header extension method of sharing capture IDs, with the extension in every media packet. An RFC3264 offer can specify a static mapping to a CaptureID for a given SSRC and later an RTP header extension can use the same CaptureID for a different SSRC. This will be a media switch for the specified CLUE media Capture. 9