Draft-romanow-clue-call-flow-02 Allyn Romanow Rob Hansen Arun Krishna.

Slides:



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

NETW-250 Troubleshooting Last Update Copyright Kenneth M. Chipps Ph.D. 1.
July 20, 2000H.323/SIP1 Interworking Between SIP/SDP and H.323 Agenda Compare SIP/H.323 Problems in interworking Possible solutions Conclusion Q/A Kundan.
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.
1996/2/13Amy, Mei-Hsuan Lu CML/CSIE/NTU1 Implementation Issues (1/6) Usage of TSAP IDs Reliable or Unreliable Well known or dynamic Audio/RTPUnreliableDynamic.
RTP Payload Format for Multiple Flows FEC draft-peck-fecframe-rtp-mf-01 Orly Peck, RADVISION IETF 77 – March 2010.
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,
Signaling: SIP SIP is one of Many ITU H.323 Originally for video conferencing The first standard protocol for VoIP Still in wide usage, but negative.
SDP.  Session Description Protocol (SDP) an application-layer protocol intended to describe multimedia sessions a text-based protocol when describing.
Page 15/19/2015 CSE 40373/60373: Multimedia Systems Popular protocols for serving media  Network transmission control  RTP – Realtime Transmission Protocol.
Alternate Offers / Capabilities in SIP/SDP Alternate Offers / Capabilities in SIP/SDP draft-bhatia-mmusic-sdp-altcap-01.txt Authors: Medhavi Bhatia John.
SIP/RTP/RTCP Implementation by George Fu, UCCS CS 525 Semester Project Fall 2006.
VoIP Using SIP/RTP by George Fu, UCCS CS 522 Semester Project Fall 2004.
A Generic Event Notification System Using XML and SIP Knarig Arabshian and Henning Schulzrinne Department of Computer Science Columbia University
Fredrik Lindholm 52st IETF Meeting 1Key management extensions Key Management Extensions for SDP and RTSP.
SIP, Session Initiation Protocol Internet Draft, IETF, RFC 2543.
Roni Even CLUE protocol Call Flows draft-even-clue-call-flows-00.
RTP Multiplexing draft-rosenberg-rtcweb-rtpmux Jonathan + {Rosenberg, Lennox}
AARNet Copyright 2011 Network Operations SDP Deep Dive Bill Efthimiou APAN33 SIP workshop February 2012.
SIP and NAT Dr. Jonathan Rosenberg Cisco Fellow. What is NAT? Network Address Translation (NAT) –Creates address binding between internal private and.
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.
Allyn Romanow Mark Duckworth ) Andy Pepperell Brian Baldino
CLUE DATA CHANNEL CHRISTER HOLMBERG IETF#89 London, U.K.
DATA CHANNEL FOR CLUE CHRISTER HOLMBERG CLUE VIRUTAL INTERIM MEETING 27th January 2014.
T ELEPRESENCE T UTORI A L July 30, Introduction to Telepresence 1 Introduction to the IETF CLUE work 2 Telepresence scenarios 3 CLUE FrameworkCLUE.
July 10, 2006rtpsec BOF IETF-661 Best Effort SRTP Phil Zimmermann Alan Johnston.
All rights reserved © 1999, Alcatel, Paris. page n° 1 SIP for Xcast SIP for the establishment of xcast-based multiparty.
Roni Even Jonathan Lennox Mapping RTP streams to CLUE media captures draft-even-clue-rtp-mapping-03 IETF-84.
Gonzalo Camarillo Advanced Signalling Research Lab 48th IETF MMUSIC WG Gonzalo Camarillo draft-camarillo-sip-sdp-00.txt.
Real Time Protocol (RTP) 김 준
Presented By Team Netgeeks SIP Session Initiation Protocol.
SIP:Session Initiation Protocol Che-Yu Kuo Computer & Information Science Department University of Delaware May 11, 2010 CISC 856: TCP/IP and Upper Layer.
Security, NATs and Firewalls Ingate Systems. Basics of SIP Security.
4.1.4 multi-homing.
Session Recording (SIPREC) Protocol (draft-ietf-siprec-protocol-09) Leon Portman Henry Lum
SDP Security Descriptions for Media Streams Mark Baugher Dan Wing - Cisco Systems -
SIPPING - IETF 62 - Minneapolis (March 2005)1 Session Initiation Protocol (SIP) Session Mobility draft-shacham-sipping-session-mobility-00 Ron Shacham.
RTP Payload Format for DV Format Video draft-ietf-avt-dv-video-00.txt Akimichi ogawa Keio university.
Allyn Romanow Flemming Andreasen Implementing CLUE encoding provider advertisements in.
BUNDLE Christer Holmberg, Ericsson Harald Alvestrand, Google IETF#84, Vancouver.
CLUE RTP usage Andy Pepperell
SIP-H.323 Interworking Group RRR-1 IETF-48 SIP-H.323 Interworking Requirements draft-agrawal-sip-h323-interworking-reqs-00.txt Hemant.
March 22th, 2001 MMUSIC WG meeting 50th IETF MMUSIC WG meeting The fid attribute draft-ietf-mmusic-fid-00.txt
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.
SIP-SIP Video Delayed Offer-Delayed Offer
Session Description Protocol
1 Internet Telephony: Architecture and Protocols an IETF Perspective Authors:Henning Schulzrinne, Jonathan Rosenberg. Presenter: Sambhrama Mundkur.
The eXtensible Peer Protocol (XPP) Emil Ivov - Enrico Marocco –
draft-ivov-mmusic-trickle-ice E. Rescorla, J. Uberti, E. Ivov
The Session Initiation Protocol - SIP
RTP Usage for CLUE IETF 82 – 14 November 2011 Jonathan Lennox Allyn Romanow Paul Witty.
Allyn Romanow Stephen Botzko Robert Hansen Signaling Requirements for implementing the.
7: Multimedia Networking7-1 protocols for real-time interactive applications RTP, RTCP, SIP.
Telepresence Interoperability Protocol (TIP) Overview for IMTC SuperOp 2010 Workshop 1 Allyn Romanow Cisco Telepresence Systems Business Unit (TSBU) 15.
11 CS716 Advanced Computer Networks By Dr. Amir Qayyum.
CLUE Signaling draft-kyzivat-clue-signaling-02 Paul Kyzivat 11-mar-2013.
Klara Nahrstedt Spring 2012
Use of “Latent Configurations" in CLUE
SDP Offer/Answer mechanism to negotiate the usage of bundled media
Virtual Interim CLUE Signalling discussion
Options to Transport CLUE Messages draft-wenger-clue-transport-01
VOICE AND VIDEO OVER IP VOIP, RTP, RSVP.
Issues from telemedical-callflows
RTCWeb Data Channel Management
Ron Shacham Henning Schulzrinne Srisakul Thakolsri Wolfgang Kellerer
SIP Basics Workshop Dennis Baron July 20, 2005.
Overview of H.323-SIP Gateway
Presentation transcript:

draft-romanow-clue-call-flow-02 Allyn Romanow Rob Hansen Arun Krishna

Call Flow overview Alice Bob SIP: INVITE SIP: ACK SIP: 200 OK (optional) Single-stream media CLUE: Advertisement CLUE: Configure Multi-stream media Negotiate CLUE channel CLUE: Advertisment CLUE: Configure

Illustrative Transport: SCTP (over DTLS) over UDP Reliable, in-order delivery Can follow the same path as RTP – Can use ICE Can be encrypted/authenticated with DTLS – May wish to make this mandatory (null cipher for unencrypted) Negotiated in SDP

SDP Implementations may advertise one m-line per media type, or multiple if desired. Audio and video remain on separate m-lines SDP negotiates RTP session and codec limits – CLUE does not replace SDP; all media MUST remain within these limits

CLUE in SIP/SDP INVITE SIP/2.0 Supported: clue... v=0 o=alice IN IP4 client.atlanta.example.com s=- c=IN IP a=fingerprint: SHA-1 4B:AC:B7... a=extmap:1 urn:ietf:params:clue:mux t=0 0 b=AS:6064 m=audio RTP/AVP 0... m=video RTP/AVP m=application UDP/DTLS/SCTP/CLUE * a=setup:actpass a=connection:new

Post-SIP behaviour CLUE-specific SDP parameters will be ignored by non-CLUE devices – Will result in a conventional single-stream call Before CLUE is negotiated: – MUST be ready to receive single-stream media – MAY(SHOULD?) send single-stream media

CLUE Messages A call is made up of two independent, unidirectional CLUE negotiations Additional advertisement/configure messages may be sent at any point – Messages to include sequence numbers to identify the advertisement a configure message is referring to. XML encoding for messages

SCTP channel re-establishment and CLUE state Mid-call re-establishment of SCTP channel triggered by SDP may mean far end has no knowledge of previous state Hence on re-establishment CLUE MUST be renegotiated – Endpoints on hold should not deactivate the CLUE channel to avoid renegotiation.

SIP/CLUE mid-call interaction CLUE advertisements may also trigger SIP reINVITEs to make SDP changes Alice Bob SIP: INVITE (4M) SIP: ACK SIP: 200 OK

SIP/CLUE mid-call interaction CLUE advertisements may also trigger SIP reINVITEs (eg, to alter bandwidth) Alice Bob SIP: INVITE (4M) SIP: ACK SIP: 200 OK CLUE: Advertisement (3 1080p screens)

SIP/CLUE mid-call interaction CLUE advertisements may also trigger SIP reINVITEs (eg, to alter bandwidth) Alice Bob SIP: INVITE (4M) SIP: ACK SIP: 200 OK CLUE: Advertisement (3 1080p screens) SIP: INVITE (12M) SIP: ACK SIP: 200 OK CLUE: Configure (3 1080p screens)

RTP multiplexing Consensus not yet reached on method – draft-lennox-clue-rtp-usage-04 – draft-even-clue-rtp-mapping-03 Demultiplex by SSRC or RTP extension header – Format for RTP extension header: | ID=1 | L=3 | capture id | | capture id |

Questions