Virtual Interim CLUE Signalling discussion

Slides:



Advertisements
Similar presentations
Re-INVITE Handling draft-camarillo-sipping-reinvite-00.txt
Advertisements

SIP Interconnect Guidelines draft-hancock-sip-interconnect-guidelines-02 David Hancock, Daryl Malas.
Non-200 response to PRACK (Due to rejected SDP offer or other reasons) Christer Holmberg
CLUE protocol CLUE design team meeting 28/10/2014.
Encoding syntax alternatives Oct 8 th 2013, CLUE design team meeting.
Copyright 2004 Monash University IMS5401 Web-based Systems Development Topic 2: Elements of the Web (g) Interactivity.
Expressing encoding limitations in CLUE signalling Design team call 26/11/2013.
Early Media in SIP: Problem Statement, Requirements, and Analysis of Solutions draft-barnes-sip-em-ps-req-sol Richard Barnes BBN Technologies IETF 68,
Introduction to SDP Issues. Content Background Goals SDP Primer RTP Primer Use cases “New” Functionalities in SDP Multiple RTP Streams in SDP Decision.
DATA CHANNEL FOR CLUE CHRISTER HOLMBERG CLUE VIRUTAL INTERIM MEETING 27th January 2014.
July 10, 2006rtpsec BOF IETF-661 Best Effort SRTP Phil Zimmermann Alan Johnston.
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.
Session Initiation Protocol (SIP). What is SIP? An application-layer protocol A control (signaling) protocol.
CLUE Framework Issues CLUE virtual interim meeting Jan 27, 2014 Mark Duckworth draft-ietf-clue-framework-13 1.
SIP Performance Benchmarking draft-ietf-bmwg-sip-bench-term-02 draft-ietf-bmwg-sip-bench-meth-02 July 24, 2010 Prof. Carol Davids, Illinois Inst. of Tech.
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.
Session Recording (SIPREC) Protocol (draft-ietf-siprec-protocol-09) Leon Portman Henry Lum
1 SIPREC Recording Metadata Model for SRS (draft-ram-siprec-metadata-03) Jan 25-26, 2011 Virtual Interim meeting Ram Mohan R On behalf of the team Team:
Christian Groves Describing Captures in CLUE and relation to multipoint conferencing draft-groves-clue-multi-content-00 CLUE Interim meeting (09/13)
Allyn Romanow Flemming Andreasen Implementing CLUE encoding provider advertisements in.
BUNDLE Christer Holmberg, Ericsson Harald Alvestrand, Google IETF#84, Vancouver.
CLUE Overview and Architecture IETF 82 CLUE ad hoc meeting Allyn Romanow
CLUE datamodel & protocol IETF 90 Toronto, July 21 st 2014 Roberta Presta & Simon Romano.
1 SIPREC Recording Metadata format (draft-ram-siprec-metadata-format- 00) Jan 25-26th SIPREC INTERIM MEETING R Parthasarathi On behalf of the team Team:
CLUE Signaling (draft-kyzivat-clue-signaling-05) Sept 17, 2012 Editor: Paul Kyzivat.
1 SIPREC Recording Metadata Model for SRS (draft-ram-siprec-metadata-02) Dec 16, 2010 Virtual Interim meeting Ram Mohan R On behalf of the team Team: Paul.
Diameter Group Signaling Thursday, August 02 nd, 2013 draft-ietf-diameter-group-signaling-01 Mark Jones, Marco Liebsch, Lionel Morand IETF 87 Berlin, Germany.
draft-ivov-mmusic-trickle-ice E. Rescorla, J. Uberti, E. Ivov
RTP Usage for CLUE IETF 82 – 14 November 2011 Jonathan Lennox Allyn Romanow Paul Witty.
Page 1 IETF Speermint Working Group Speermint draft-ietf-speermint-requirements-04 IETF 71 - Wednesday March 12, 2008 Jean-François Mulé -
CLUE Framework 01 – comments and issues Interim meeting October 2011 Roni Even.
1 Coping with Early Media Brian Stucker Nortel Systems/Standards Architect November 6th, 2006.
Allyn Romanow Stephen Botzko Robert Hansen Signaling Requirements for implementing the.
CLUE protocol CLUE design team meeting 07/10/ /10/2013.
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.
Real-time aspects June 19, 2016
Codec Control for RTCWEB
CLUE WG Interim Meeting San Jose, CA Sept , 2012
CLUE Framework Interim Meeting Feb 15, 2012 Mark Duckworth
Next steps in Real Time Communications
IETF 80 MMUSIC WG draft-elwell-mmusic-ice-updated-offer
Use of “Latent Configurations" in CLUE
RTCP Feedback Message for Image Control
CLUE WG Interim Meeting San Jose, CA Sept , 2012
Session Recording (SIPREC) Protocol (draft-ietf-siprec-protocol-11)
CLUE WG Interim Meeting San Jose, CA Sept , 2012
CLUE design team meeting
draft-ietf-simple-message-sessions-00 Ben Campbell
IETF#67 – 5-10 November 2006 FECFRAME requirements (draft-ietf-fecframe-req-01) Mark Watson.
Options to Transport CLUE Messages draft-wenger-clue-transport-01
EEC 688/788 Secure and Dependable Computing
Session Initiation Protocol (SIP)
Issues from telemedical-callflows
GS2: Bridge between SASL and GSS-API
CLUE Use Cases 02 – comments and proposal
…….. PackML concept illustration Line Controller Unit #1 Unit #2
General ad hoc- LB115- Comment Resolutions – Jan 08
EEC 688/788 Secure and Dependable Computing
Proposal for IEEE 802.1CQ-LAAP
Post WG LC NMDA datastore architecture draft
AP Location Capability
EEC 688/788 Secure and Dependable Computing
TGu/TGv Joint Meeting Date: Authors: May 2008 Month Year
Relay User Machine (rum)
NFD Tunnel Authentication
SCTP in SDP draft-loreto-mmusic-sctp-sdp-07
Introduction Communication Modes Transmission Modes
Presentation transcript:

Virtual Interim CLUE Signalling discussion Robert Hansen 2014/05/29

-01 Document cleanup Revised terminology Calls are CLUE-enabled or not Devices are CLUE-capable or not (irrespective of whether call is CLUE-enabled) Moved encoding information outside of SDP initial offer section Given draft recommends initial offer does not contain encodings, was a strange place to define them

Syntax change Feature tag: ‘sip.telepresence’ changed to ‘sip.clue’ Group syntax: TELEPRESENCE changed to CLUE

CLUE group restrictions CLUE group must have one (and only one) mid related to a data channel Previously could a CLUE group with no data channel association Explicitly forbids multiple CLUE groups until someone publishes a way to do it

CLUE-controlled media Restriction on sending media on CLUE-controlled m-lines until negotiated in CLUE as well Is there a better term for what can’t be sent than ‘media’? Explicitly mandates that non-media exchanges like DTLS and ICE must be done as normal No text on RTCP yet – if channel is active should be sent as normal(?)

CLUE/SDP state machine interaction Some changes in call state require CLUE and SDP changes and hence are non-atomic CLUE and SDP state machines are independent Participant must cope with transitory states with inconsistent information CLUE-controlled media unless both CLUE and SDP information available

CLUE/SDP state machine interaction MUST NOT delay ongoing SDP exchange due to CLUE state MAY delay initiating new SDP exchange MUST NOT delay any mandatory CLUE transitions (for provider/consumer/participant state machines) due to SDP state MAY delay “CONF COMPLETED->PREPARING ADV” or “READY TO CONF->TRYING” (send new ADVERTISE or CONFIGURE) based on SDP state

CLUE/SDP state machine recommendations SHOULD ensure that any inconsistencies are transitory Make this a MUST? Recommends no ‘speculative’ requests are made Eg, don’t request anything until details are available in both CLUE and SDP May require more O/As Send changes in CLUE before SDP Minimises SDP O/As needed

CLUE/SDP state machine recommendations Adding stream Alice Bob CLUE ADVERISEMENT SDP Offer SDP Answer May be simultaneous CLUE CONFIGURE Media starts

CLUE/SDP state machine recommendations Removing stream Alice Bob CLUE ADVERISEMENT Media stops CLUE CONFIGURE No ordering recommendation SDP Offer SDP Answer