User Application Control (Keypress Events) SIPPING WG - IETF 53 Robert Fairlie-Cuninghame, Bert Culpepper, Jean-François Mulé.

Slides:



Advertisements
Similar presentations
SIP and Instant Messaging. SIP Summit SIP and Instant Messaging What Does Presence Have to Do With SIP? How to Deliver.
Advertisements

IM May 24, 2000 Introduction to SIP Jonathan Rosenberg Chief Scientist.
H. 323 Chapter 4.
CCNA – Network Fundamentals
29.1 Chapter 29 Multimedia Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
RTP: A Transport Protocol for Real-Time Applications Provides end-to-end delivery services for data with real-time characteristics, such as interactive.
H. 323 and firewalls: Problem Statement and Solution Framework Author: Melinda Shore, Nokia Presenter: Shannon McCracken.
IPv4 and IPv6 Mobility Support Using MPLS and MP-BGP draft-berzin-malis-mpls-mobility-00 Oleg Berzin, Andy Malis {oleg.berzin,
UNCW UNCW SIGGRAPH 2002 Topic #3: Continuous Media in Wired and Wireless Environments Ronald J. Vetter Department of Computer Science University of North.
Jacob Boston Josh Pfeifer. Definition of HyperText Transfer Protocol How HTTP works How Websites work GoDaddy.com OSI Model Networking.
OSI Model.
EE 4272Spring, 2003 EE4272: Computer Networks Instructor: Tricia Chigan Dept.: Elec. & Comp. Eng. Spring, 2003.
SIP, Session Initiation Protocol Internet Draft, IETF, RFC 2543.
1 Extending SIP Speaker: Hsuan-Ming Chen Adviser: Ho-Ting Wu Date: 2005/04/26.
COE 342: Data & Computer Communications (T042) Dr. Marwan Abu-Amara Chapter 2: Protocols and Architecture.
Introduction to SIP Speaker: Min-Hua Yang Advisor: Ho-Ting Wu Date:2005/3/29.
 The Open Systems Interconnection model (OSI model) is a product of the Open Systems Interconnection effort at the International Organization for Standardization.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Communicating over the Network Network Fundamentals – Chapter 2.
Session Policy Framework using EAP draft-mccann-session-policy-framework-using-eap-00.doc IETF 76 – Hiroshima Stephen McCann, Mike Montemurro.
DTMF & Universal User Key Input Skip Cave InterVoice-Brite Inc.
Event-based Radio Communication Signaling using the Session Initiation Protocol Klaus Darilion.
WG RAQMON Internet-Drafts RMON MIB WG Meeting Washington, Nov. 11, 2004.
Jaringan Komputer Dasar OSI Transport Layer Aurelio Rahmadian.
All rights reserved © 1999, Alcatel, Paris. page n° 1 SIP for Xcast SIP for the establishment of xcast-based multiparty.
I-D: draft-rahman-mipshop-mih-transport-01.txt Transport of Media Independent Handover Messages Over IP 67 th IETF Annual Meeting MIPSHOP Working Group.
Department of Electronic Engineering City University of Hong Kong EE3900 Computer Networks Introduction Slide 1 A Communications Model Source: generates.
NENA Development Conference | October 2014 | Orlando, Florida Emergency Incident Data Document (EIDD) Transfer Protocols Jerry Schlesinger, PMP – City.
An Integrated QoS, Security and Mobility Framework for Delivering Ubiquitous Services Across All IP-based Networks Haitham Cruickshank University of Surrey.
03/09/2003Helsinki University of Technology1 Overview of Thesis Topic Presented By: Zhao Xuetao.
Session Initiation Protocol (SIP). What is SIP? An application-layer protocol A control (signaling) protocol.
Improving the Routing Efficiency of SIP Instant Message SIP 即時傳訊之繞送效能研究 adviser : Quincy Wu speaker : Wenping Zhang date :
Abierman-nanog-30may03 1 XML Router Configs BOF Operator Involvement Andy Bierman
The Transmission Control Protocol (TCP) Application Services (Telnet, FTP, , WWW) Reliable Stream Transport (TCP) Connectionless Packet Delivery.
Authentication Mechanism for Port Control Protocol (PCP) draft-wasserman-pcp-authentication-01.txt Margaret Wasserman Sam Hartman Painless Security Dacheng.
A Conference Gateway Supporting Interoperability Between SIP and H.323 Jiann-Min Ho (Presenter) Jia-Cheng Hu Information Networking Institute Peter Steenkiste.
Team Members Atcharawan Jansprasert Padmoja Roy Rana Almakabi Ehsan Eslamlouevan Manya Tarawalie.
VoN September ‘98 1 9/17/98 VoN Standards Update Jonathan Rosenberg Bell Laboratories September 17, 1998.
1 SIPREC draft-ietf-siprec-architecture-00 An Architecture for Media Recording using SIP IETF SIPREC INTERIM – Sept 28 th 2010 Andrew Hutton.
Mediactrl Framework draft-melanchuk-mediactrl-framework-00 Tim Melanchuk
Omar A. Abouabdalla Network Research Group (USM) SIP – Functionality and Structure of the Protocol SIP – Functionality and Structure of the Protocol By.
William Stallings Data and Computer Communications
Voice over IP B 林與絜.
Draft-johnston-sipping-rtcp-summary-01.txt RTCP Summary Report Delivery to SIP Third Parties draft-johnston-sipping-rtcp-summary-01.txt Alan Johnston –
Session Initiation Protocol (SIP) Chapter 5 speaker : Wenping Zhang data :
SIP And DTMF SIP WG 48th IETF July 31-August 4, 2000 Bert Culpepper, Skip Cave.
IETF-81, Quebec City, July 25-29, 2011
RFC3261 (Almost) Robert Sparks. SIPiT 10 2 Status of the New SIP RFC Passed IETF Last Call In the RFC Editor queue Author’s 48 hours review imminent IMPORTANT:
IMSX Protocol Evaluation for Session Based IM draft-barnes-simple-imsx-prot-eval-00.txt Mary Barnes IETF 54 SIMPLE WG.
SIP file directory draft-garcia-sipping-file-sharing-framework-00.txt draft-garcia-sipping-file-event-package-00.txt draft-garcia-sipping-file-desc-pidf-00.txt.
Voice Over Internet Protocol (VoIP) Copyright © 2006 Heathkit Company, Inc. All Rights Reserved Presentation 5 – VoIP and the OSI Model.
August 2, 2005 IETF 63 – Paris, France Media Independent Handover Services and Interoperability Ajay Rajkumar Chair, IEEE WG.
1 Internet Telephony: Architecture and Protocols an IETF Perspective Authors:Henning Schulzrinne, Jonathan Rosenberg. Presenter: Sambhrama Mundkur.
OPTIMIZATION OF SIGNALING TRAFFIC IN CENTRALIZED CONFERENCES USING SIP Submitted by D.NEHRU S.JAYABALAN B.Tech IT II Year.
March 20th, 2001 SIP WG meeting 50th IETF SIP WG meeting Overlap signalling handling
SIPPING Drafts Jonathan Rosenberg dynamicsoft. Conferencing Package Issues Only one – scope Depends on broader work in conferencing May include –Participant.
1 End-to-middle Security in SIP Kumiko Ono NTT Corporation March 1, 2004 draft-ietf-sipping-e2m-sec-reqs-01.txt draft-ono-sipping-end2middle-security-01.txt.
Week #8 OBJECTIVES Chapter #5. CHAPTER 5 Making Networks Work Two Networking Models –OSI OPEN SYSTEMS INTERCONNECTION PROPOSED BY ISO –INTERNATIONAL STANDARDS.
DOTS Requirements Andrew Mortensen November 2015 IETF 94 1.
7-May-02SIP/SIPPING Interim Meeting1 Application Interaction Requirements Draft-culpepper-app-interact-reqs-01.txt.
EAP Applicability IETF-86 Joe Salowey. Open Issues Open Issues with Retransmission and re- authentication Remove text about lack of differentiation in.
VoIP ALLPPT.com _ Free PowerPoint Templates, Diagrams and Charts.
Chapter 29 Multimedia Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Session-Independent Policies draft-ietf-sipping-session-indep-policy-02 Volker Hilt Jonathan Rosenberg Gonzalo.
End-to-middle Security in SIP
Session Initiation Protocol (SIP)
draft-ipdvb-sec-01.txt ULE Security Requirements
User to User Key Signaling Protocols
Computer Networks Protocols
Presentation transcript:

User Application Control (Keypress Events) SIPPING WG - IETF 53 Robert Fairlie-Cuninghame, Bert Culpepper, Jean-François Mulé

User Application Control Need: Application Servers need to receive user activity indications independently of the media path of established sessions and in some cases outside of the signaling path of established sessions as well. Observation: End-to-end (media path) user activity indications [UAI] are currently conveyed using RTP, for example, RFC2833. Question: Are RTP based solutions, suitable for transporting asynchronous user activity indications outside of the media plane? Conjecture: No. If the UAI’s are transported in the signaling plane then the number of messages and bandwidth is critical. Reliability through blind retransmission is not acceptable. Tight media synchronization is not a requirement for Async UAI and so reliability can be achieved by message delivery acknowledgement. Furthermore, Async UAI’s should only be generated when explicitly requested by application servers. Question: Is the transport of DTMF-derived user activity indications deemed sufficient for future user application interaction? Conjecture: No, it is not acceptable to limit future user application interaction to only using telephone keypad keys. At the very least generic keyboards and device-specific buttons must be supported.

User Application Control (Cont.) Conclusion: End-to-end and asynchronous user activity indications have different functional and performance requirements; as some of the requirements are at odds this suggests separate mechanisms are desirable. A new asynchronous user activity indication transport mechanism is needed to generate indications outside of the media plane such that activity indications are only generated on request and in a way that is sensitive to the bandwidth constraints outside of the media plane. What are the requirements for such a system?

Key Events Requirements Transport user indications to network elements participating in the session signaling and independent from the session media. Support for user indications via keys or buttons. A network entity desiring user indications must be able to request user indications from another network entity. The entity receiving a request must be able to respond with its intent/willingness to transmit user indications. The mechanism must support multiple network entities in the signaling path requesting and receiving indications independently from each other. Separation between the transport mechanism in the signaling plane (SUB/NOT or INFO) and the message syntax. The mechanism must support filtering so that only user indications of interest are transmitted. The mechanism must support reliable delivery at least as good as the session control protocol.

Key Events Requirements (Cont.) The mechanism must support collecting device input both within and outside of established sessions. The mechanism must support devices with richer user interfaces than simple keypads. A requestor must be able to determine the makeup/contents of the user interface possessed by a target device. The mechanism must support device and/or user-specific buttons. The mechanism must provide some form of indication of key press duration. The mechanism must provide some form of indication of relative key press start time (relative to other key presses). The mechanism must allow for end-to-end security/privacy between source and destination. Both entities must be able to authenticate each other.

Related Proposals: draft-mahy-sipping-signaled-digits-00.txt This proposal describes carrying the RFC 2833 defined audio/telephone-event MIME type in the message bodies in INFO. Also defines an Event Package for carrying the RFC 2833 defined audio/telephone-event MIME type in the NOTIFY message body. draft-culpepper-sip-key-events-01.txt This proposal defines a SIP Events package and defines a key/keypress protocol for placing in SUB/NOT message bodies. Open Issues: What should this new mechanism be? Is the SIP Events framework appropriate? If so, what should the payload format be? (Potential) Next Steps: 1.Prepare requirements I-D (include SIMPLE requirements) 2.Define an Events Package 3.Define a "key" representation