CLUE definitions Stephan Wenger.

Slides:



Advertisements
Similar presentations
DISPATCH WG RTCWEB Adhoc IETF-80. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft.
Advertisements

CLUE REQUIREMENTS IETF 80 Allyn Romanow
Presentation and Multimedia
Lesson 15 Presentation Programs.
H. 323 Chapter 4.
Packet Based Multimedia Communication Systems H.323 & Voice Over IP Outline 1. H.323 Components 2. H.323 Zone 3. Protocols specified by H Terminal.
Options to Transport CLUE Messages Stephan Wenger Roni Even Gonzalo Caramillo Marshall Eubanks 1.
The Real Time Streaming Protocol (RTSP)
Communicating Information : Multimedia. Sights and sounds Combine all or some together and you get… multimedia.
Palpatine: a P2PM IMS Video Share Architecture and Implementation Second International Conference and Exhibition on Next Generations Mobile Applications.
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.
A Web Services Based Streaming Gateway for Heterogeneous A/V Collaboration Hasan Bulut Computer Science Department Indiana University.
XCON Framework Overview & Issues Editors: Mary Barnes Chris Boulton
Allyn Romanow Mark Duckworth ) Andy Pepperell Brian Baldino
CLUE Framework Status and Issues IETF89 - London March 5, 2014 Mark Duckworth draft-ietf-clue-framework-14 1.
MGCP Megaco H.248 by Bob Young. MGCP - Megaco - H.248 "It's all one."
CLUE WG IETF-89 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
SIPREC Conference Recording (draft-kyzivat-siprec-conference-use-cases-01) IETF 89, March 7, 2014 Authors: Michael Yan, Paul Kyzivat, Simon Romano.
MULTIMEDIA Is the presentation of information by a computer system using graphics, animation, sound and text.
Roni Even Jonathan Lennox Mapping RTP streams to CLUE media captures draft-even-clue-rtp-mapping-03 IETF-84.
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.
Clue data model Design team meeting 30/09/2014 Roberta Presta, Simon Romano.
Slide 1 Standard Grade Computing Multimedia and Presentation.
An Overlay Network Providing Application-Aware Multimedia Services Maarten Wijnants Bart Cornelissen Wim Lamotte Bart De Vleeschauwer.
Slide title minimum 48 pt Slide subtitle minimum 30 pt RTCWEB Terminology A Discussion of relation between RTCWEB Media Protocol Terminology and the PeerConnection.
CLUE framework updates IETF 85, Atlanta. “Capture encoding” “Capture encoding” was term agreed by the list to define a specific instantiation of a media.
MULTIMEDIA Hardware 4/24/2017.
Use-Cases draft-romanow-clue-telepresence- use-cases-01 IETF 80 Prague March 2011.
Real-time Transport Protocol (RTP) Recommendations for SIPREC (draft-eckel-siprec-rtp-rec-02) Charles Eckel SIPREC Virtual Interim.
XRBLOCK IETF 84 Vancouver RTCP XR Report Block for QoE metric Reporting draft-ietf-xrblock-rtcp-xr-qoe-02 Geoff Hunt Alan Clark Roland Scott.
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 WG IETF-83 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
CLUE datamodel & protocol IETF 90 Toronto, July 21 st 2014 Roberta Presta & Simon Romano.
Mixer Control Package for Media Control Channel Framework Tim Melanchuk, Scott McGlashan, Chris Boulton draft-ietf-mediactrl-mixer-control-package-00 IETF.
CLUE WG chair: Mary Barnes RTCWEB WG chair: Ted Hardie CLUE & RTCWEB WGs Adhoc Common (SDP/RTP) building blocks IETF-82.
RTP Usage for CLUE draft-lennox-clue-rtp-usage-02 Clue WG, IETF 83, 27 March 2012 Jonathan Lennox Allyn Romanow
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.
© 2008 Cisco Systems, Inc. All rights reserved. 1 Cisco TelePresence Interoperability Technical Overview TSBU Technical Marketing October 2008.
Present Day Telepresence Solutions Patrick Luthi, TANDBERG IMTC Requirements WG Chair.
SIPREC Conference Recording (draft-kyzivat-siprec-conference-use-cases-00) IETF 87, November 4, 2013 Authors: Michael Yan, Paul Kyzivat, Simon Romano.
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.
CLUE WG IETF-85 Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
RTP Taxonomy & draft-lennox-raiarea-rtp-grouping-taxonomy-03 IETF 88 1.
CLUE WG Interim Meeting San Jose, CA Sept , 2012
VoIP ALLPPT.com _ Free PowerPoint Templates, Diagrams and Charts.
CLUE Framework Interim Meeting Feb 15, 2012 Mark Duckworth
CLUE WG Interim Meeting San Jose, CA Sept , 2012
CLUE WG Interim Meeting San Jose, CA Sept , 2012
Virtual Interim CLUE Signalling discussion
Options to Transport CLUE Messages draft-wenger-clue-transport-01
Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made.
Mary Barnes (WG co-chair) Paul Kyzivat (WG co-chair)
IMTC Telepresence AG Overview
CLUE Use Cases 02 – comments and proposal
Design and Implementation of Audio/Video Collaboration System Based on Publish/subscribe Event Middleware CTS04 San Diego 19 January 2004 PTLIU Laboratory.
Prepare Cisco with Valid Dumps Dumps4download.co.in
MODERN Working Group IETF 97 November 14, 2016.
IETF 57 Vienna, Austria July 15, 2003
So you were told to make a video
lemonade Eric Burger Glenn Parsons November 10, 2003
SIPBRANDY Chair Slides
Guidelines for using the Multiplexing Features of RTP to Support Multiple Media Streams draft-ietf-avtcore-multiplex-guidelines-06 Magnus.
Audio/Video Transport Extensions (avtext) Working Group
Presentation transcript:

CLUE definitions Stephan Wenger

Document Usefulness Clue definitions was intended as working tool to align various CLUE drafts Alignment more or less reached Doc never intended for publication Is there a point in maintaining the doc beyond IETF81? Suggestion: only one more update cycle right after this meeting.

Open issue #1: left/right Definitions-00 used “stage-left” and “stage right” Was too confusing for some, to restricting for others, and generally unintuitive Definitions-01 says “to be interpreted in context” No one objected so far, but I note that neither requirements nor framework provide sufficient context in all cases Suggestion Leave definition as in 01 Beat up document editors to be less sloppy

Open issue #2: “Layout” Layout: How rendered media streams are spatially arranged with respect to each other on a single screen/mono audio telepresence endpoint, and how rendered media streams are arranged with respect to each other on a multiple screen/loudspeaker telepresence endpoint. Note that audio as well as video is encompassed by the term layout--in other words, included is the placement of audio streams on loudspeakers as well as video streams on video screens. Edit. note: this is on the RENDERER side ONLY. Could encompass stuff like binaural Is renderer-only definition agreeable

Open Issue #3: “MCU” MCU: Multipoint Control Unit (MCU) - a device that connects two or more endpoints together into one single multimedia conference [RFC5117]. An MCU includes an [RFC4353] Mixer. RFC4353 is tardy in requiring that media from the mixer be sent to EACH participant. I think we have practical use cases where this is not the case. Is this an issue? Suggestion: non-issue, leave “as is”

Open Issue #4: “Media” Media: Any data that, after suitable encoding, can be conveyed over RTP, including audio, video or timed text. Edt. note: does Media include far end camera control (which can be conveyed over RTP)? Suggestion: abstract definition is good enough, FECC is a special case (not architecturally sound anyway), so leave definition as is, and don’t mention FECC