1 / 9

App Interaction

This document, authored by Jonathan Rosenberg in July 2001, explores the utilization of dynamicsoft context parameters in SIP interactions, covering important aspects such as Call-ID, From, To, Refer, Require, and more. It delves into the use of Refer/SUB, identity authorization, and informative references, providing insights on Reg.Event and device capabilities. The evolution of the draft, from its creation to subsequent revisions, is detailed, alongside the historical background and goals of the project. Recommendations, ICE scenarios, and NAT issues are addressed, emphasizing the need for a coherent and standardized solution for SIP deployments.

charlotteh
Download Presentation

App Interaction

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. App Interaction Jonathan Rosenberg dynamicsoft

  2. Context Param GET http://foo.com INVITE Call-ID:A From:caller;tag=B To:callee;tag=C Supported: context INVITE/200 2 4 1 3 REFER sip:gruu Refer-To: http://foo.com; context=“B,C,A” Require: context

  3. Added motivation text from KPML SIP Identity Informative Reference Usage of Reg Event to learn capabilities of device Authorizing REFER/SUB – cannot be automatic w/o sips Softened wording about app in dialog path Updated examples to use TLS, crypto-random identifiers IANA registries for context parameters Other Changes

  4. Next Steps • No open issues • Ready for WGLC

  5. NAT Scenarios Jonathan Rosenberg dynamicsoft

  6. Individual draft, July 2001 Team effort between myself, Rohan Mahy, Sanjoy Sen of Nortel Contains lots of flows, lots of different solutions, no recommendations Made working item, June 2002 Abandoned October 2003 Gave the message that we didn’t have a solution that coherently works ICE Scenarios October 2003 Reverted to individual draft with ICE example flows Told the community that this is how to make it work Concerns from the community about scope Kept on life support with two revisions since then Minor additions, such as v4 to v6 transition scenarios History

  7. Proposed Goals • Make it clear to the community that we have a solution for the problem that works consistently across deployment scenarios • Make use of approved and standards tracked IETF specifications • Scope is SIP and offer/answer • RFC 3581 (rport), connect-reuse, STUN, TURN, ICE, GRUU

  8. Problem Statement and Motivation Overview of IETF Solution References to specifications Unstated wisdom Call flows with different types of NAT Call flows with different topologies Third Party Call Control V6/V4 Cases High Level Outline

  9. Path Forward • Chris Boulton recruited to take over primary editorship as part of mentor program • Will work out outline and distribute on list • Resubmit existing document as draft-ietf • Submit revised document based on outline • Submit document after all input specs are done

More Related