1 Media Latching draft-kaplan-mmusic-latching Documents Media Latching – Informational – Meant to provide a ref for latching (and HNT) Documentcommon practice.

Slides:

Advertisements

Similar presentations

Negotiation and Extensibility Cullen Jennings IETF 80.

Advertisements

Addressing Security Issues IT Expo East Addressing Security Issues Unified Communications SIP Communications in a UC Environment.

ICE Jonathan Rosenberg Cisco Systems. Changes Removed abstract protocol concept Relaxed requirements for ICE on servers and gateways – no address gathering.

1 © 2004 Cisco Systems, Inc. All rights reserved. Making NATs work for Online Gaming and VoIP Dr. Cullen Jennings

STUN Date: Speaker: Hui-Hsiung Chung 1.

SIP Traversal over NAT Problems and Solutions Mr. Ting-Yun Chi May 2,2006 (Taiwan,NICI IPv6 R&D Division)

NAT1 Network Address Translation Dr. Danny Tsang Department of Electronic & Computer Engineering Hong Kong University of Science and Technology.

January 23-26, 2007 Ft. Lauderdale, Florida An introduction to SIP Simon Millard Professional Services Manager Aculab.

Solutions for SIP The SIP enabler We enable SIP communication for business What the E-SBC can do for you.

Scope Discussion Seems to be a good deal of interest in moving this toward a working group If we want to work toward this, we need to have a clearly defined.

1 © 2004, Cisco Systems, Inc. All rights reserved IP Telephony Security Cisco Systems.

Voice over IP and IP telephony Network convergence – Telephone and IT – PoE (Power over Ethernet) Mobility and Roaming Telco – Switched -> Packet (IP)

September 19, 2006speermint interim1 VoIP Threats and Attacks Alan Johnston.

ICE Jonathan Rosenberg dynamicsoft. Issue 1: Port Restricted Flow This case does not work well with ICE right now Race condition –Works if message 13.

RTSP NAT Traversal Update Magnus Westlund (Ericsson) Thomas Zeng (PVNS, an Alcatel company) IETF-60 MMUSIC WG draft-ietf-mmusic-rtsp-nat-03.txt.

SIP, NAT, Firewall SIP NAT Firewall How to Traversal NAT/Firewall for SIP.

1 VOIP Network Threats Let the subscribers beware Gerard Wilkes October 24, 2006.

Secure Telephony Enabled Middle-box (STEM) Maggie Nguyen Dr. Mark Stamp SJSU - CS 265 Spring 2003 STEM is proposed as a solution to network vulnerabilities,

Security in IP telephony (VoIP) David Andersson Erik Martinsson.

SIP and NAT Dr. Jonathan Rosenberg Cisco Fellow. What is NAT? Network Address Translation (NAT) –Creates address binding between internal private and.

IT Expo SECURITY Scott Beer Director, Product Support Ingate

Common Misconceptions Alan D. Percy Director of Market Development The Truth of Enterprise SIP Security.

Session-ID Requirements for IETF84 draft-ietf-insipid-session-id-reqts-00 1 August 2012 Paul Jones, Gonzalo Salgueiro, James Polk, Laura Liess, Hadriel.

Copyright © 2006 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 draft-penno- message-flows-02 Reinaldo Penno, Daryl Malas, Adam Uzelac,

ECRIT interim meeting - May Security Threats and Requirements for Emergency Calling draft-tschofenig-ecrit-security-threats Hannes Tschofenig Henning.

RTCWEB WG draft-aboba-rtcweb-ecrit-00 Bernard Aboba Martin Thomson July 30, 2012 IETF 84, Vancouver Please join the Jabber room:

1 © 2002, Cisco Systems, Inc. All rights reserved. SIP and Jabber: Better together? Rohan Mahy

RTP Relay Support in Intelligent Gateway Author: Pieere Pi

1 RTCWEB interim Remote recording use case / requirements John Elwell.

DTLS-SRTP Handling in SIP B2BUAs draft-ram-straw-b2bua-dtls-srtp IETF-91 Hawaii, Nov 12, 2014 Presenter: Tirumaleswar Reddy Authors: Ram Mohan, Tirumaleswar.

Ingate & Dialogic Technical Presentation SIP Trunking Focused.

Towards a Scalable and Secure VoIP Infrastructure Towards a Scalable and Secure VoIP Infrastructure Lab for Advanced Networking Systems Director: David.

NAT (Network Address Translation) Natting means "Translation of private IP address into public IP address ". In order to communicate with internet we must.

July 10, 2006rtpsec BOF IETF-661 Best Effort SRTP Phil Zimmermann Alan Johnston.

NAT Traversal Speaker: Chin-Chang Chang Date:

1 A Path Forward on Identity Agreement on a problem space –We all agree that E.164 numbers don’t work well with RFC4474 –Less agreement about the requirements.

VoIP Security Assessment: Methods and Tools H. Abdelnur, V. Cridlig, R. State and O. Festor Madynes, LORIA-INRIA.

Secure phone for Vigor2820Vn-ZRTP DrayTek Corp 2010.

OUSPG [ Christian Wieser Implementation level vulnerabilities in VoIP systems c07-sip injRTP.

Gonzalo Camarillo Advanced Signalling Research Lab 48th IETF MMUSIC WG Gonzalo Camarillo draft-camarillo-sip-sdp-00.txt.

1 NAT & RTP Proxy Date: 2009/7/2 Speaker: Ni-Ya Li Advisor: Quincy Wu.

SIPPING IETF 57 Jonathan Rosenberg dynamicsoft.

Session Recording Protocol Requirements IETF 75, Stockholm (Leon Portman on behalf of the team)

ZRTP: Media Path Key Agreement for Unicast Secure RTP April 2011, RFC 6189 Author(s): P. Zimmermann, A. Johnston, J. Callas Speaker :Ted 1.

Draft-miniero-mediactrl-escs- 00.txt Alessandro Amirante Tobia Castaldi Lorenzo Miniero Simon Pietro Romano (University of Napoli Federico II)

Simon Millard Professional Services Manager Aculab – booth 402 The State of SIP.

Security, NATs and Firewalls Ingate Systems. Basics of SIP Security.

Design and implementation of SIP-aware DDoS attack detection system By: Arif Iqbal.

5 Firewalls in VoIP Selected Topics in Information Security – Bazara Barry.

IETF67 DIME WG Towards the specification of a Diameter Resource Control Application Dong Sun IETF 67, San Diego, Nov 2006 draft-sun-dime-diameter-resource-control-requirements-00.txt.

RTCWEB Considerations for NATs, Firewalls and HTTP proxies draft-hutton-rtcweb-nat-firewall- considerations A. Hutton, T. Stach, J. Uberti.

MWIF Confidential MWIF-Arch Security Task Force Task 5: Security for Signaling July 11, 2001 Baba, Shinichi Ready for MWIF Kansas.

Chapter 6: Securing the Local Area Network

March 22th, 2001 MMUSIC WG meeting 50th IETF MMUSIC WG meeting The fid attribute draft-ietf-mmusic-fid-00.txt

Multimedia Access Platforms Glen Freundlich Avaya, Inc.

Address Spoofing, DoS, and VoIP Groups 5 and 6. Spoofing, DoS, and VoIP MAC Address Spoofing MAC Address Spoofing IP Spoofing IP Spoofing DNS Spoofing.

© 2006 Intertex Data AB 1 Connect your LAN to the SIP world, while keeping your existing firewall*! The IX67 LAN SIParator (Part of the SIP Switch option.

SDP & RTP & NAT Christian Huitema. What NAT do Map ports –TCP connection –UDP stream (activity) Firewall variants –One port, any peer –One port, any “authorized”

jitsi. org advanced real-time communication.

1 Session Recording Protocol Requirements IETF 75, Stockholm (Leon Portman on behalf of the team) Draft authors: Rajnish Jain, Leon Portman, Vijay Gurbani,

1Security for Service Providers – Dave Gladwin – Newport Networks – SIP ’04 – 22-Jan-04 Security for Service Providers Protecting Service Infrastructure.

WebRTC enabled multimedia conferencing and collaboration solution

TCP for DNS security considerations

0x1A Great Papers in Computer Security

Hannes Tschofenig Henning Schulzrinne M. Shanmugam

Signal Conditioning.

Ingate & Dialogic Technical Presentation

An Architecture for Media Recording using the Session Initiation Protocol draft-ietf-siprec-architecture Andy Hutton

Presentation transcript:

1 Media Latching draft-kaplan-mmusic-latching Documents Media Latching – Informational – Meant to provide a ref for latching (and HNT) Documentcommon practice Please review!

2 Signalling Latching: Not a SIP exclusive – XEP-0177 – A SIP and XMPP example SIP / XMPP UASBC / XMPP Server RTP sent to /12345 NAT c= /12345 latch to source...

3 Security Considerations Resource exhaustion – prob: attacker could flood all relay ports to prevent calls from succeeding – sol: Restricted Latching i.e. assert Signalling.IP == RTP.IP Eavesdropping – prob: attacked floods in the hope of being latched upon – sol: restricted latching prob: attacker spoofs IP or shares NAT with UA sol: use SRTP

4 Question Interest in adopting this as a WG document?