1 / 6

Draft-rosenber-sip-entfw-00.txt

Addressing the challenges of implementing SIP in enterprise networks due to ALGs and NAT/FW complexities for residential users. Proposed solutions aim to enable SIP functionality despite existing limitations. Drafts for ALGs, distributed app components, and conferencing models are outlined for discussion.

waynef
Download Presentation

Draft-rosenber-sip-entfw-00.txt

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. Problem Enterprise FW/NATS pervasive Residential NATS more common SIP provider has proxies outside User is inside SIP fails completely Long Term Solution SIP ALGs as described elsewhere But ALGs will take a while to come Existing NAT/FW won’t change when they do Can’t deploy SIP for years, as a result Draft-rosenber-sip-entfw-00.txt

  2. Chicken and Egg Problem Enterprise IT admins won’t deploy SIP ALGs until users ask Users won’t ask unless they’re using it Users can’t use it unless it passes firewall/NAT Won’t pass firewall/NAT without ALG Enterprise IT admins won’t deploy SIP ALGs until users ask…. Strategy Define a solution, no matter how ugly, that lets SIP work now Usage increases ALGs get deployed Abandon short term solution More Bad News

  3. Yes its horrible Send Technical comments on whether you think it will work Let me know if you are interested in supporting this in your products No action requested from SIP WG at this time From here

  4. Problem: How to build complex applications in a distributed way Why is it hard? IVR systems Conferencing TTS/STT messaging Want to split components into separate boxes Allow separate providers to run each box Simplify app creation Don’t need to know details of sub-components Draft-rosenberg-sip-app-components-00.txt

  5. Solution Proposed SIP is a mechanism for invoking session level services URI is service identifier Not an extension Next steps Is there interest? Comments welcome Informational RFC? Solution + Next Steps

  6. Problem Lots of confusion on multiparty conferencing in SIP Many ways to do it, not well documented Solution Draft outlines different models Overviews differences and applicability scenarios Next steps Technical comments Suggestions for more models SIP WG consider as an informational RFC draft-rosenberg-sip-conferencing-models-00.txt

More Related