1 RFC 3486 Compressing the Session Initiation Protocol (SIP) 曾朝弘 電機系 系統組 碩士班一年級.

Slides:



Advertisements
Similar presentations
TLS Introduction 14.2 TLS Record Protocol 14.3 TLS Handshake Protocol 14.4 Summary.
Advertisements

Camarillo / Schulzrinne / Kantola November 26th, 2001 SIP over SCTP performance analysis
CCNA – Network Fundamentals
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 7: Transport Layer Introduction to Networking.
January 23-26, 2007 Ft. Lauderdale, Florida An introduction to SIP Simon Millard Professional Services Manager Aculab.
1 Kommunikatsiooniteenuste arendus IRT0080 Loeng 5 Avo Ots telekommunikatsiooni õppetool, TTÜ raadio- ja sidetehnika inst.
1 Reading Log Files. 2 Segment Format
SIP Security Issues: The SIP Authentication Procedure and its Processing Load Stefano Salsano, DIE — Universit à di Roma “ Tor Vergata ” Luca Veltri, and.
Session Initiation Protocol (SIP) By: Zhixin Chen.
12/05/2000CS590F, Purdue University1 Sip Implementation Protocol Presented By: Sanjay Agrawal Sambhrama Mundkur.
CSc 461/561 CSc 461/561 Multimedia Systems Part C: 2. SIP.
SIP, Session Initiation Protocol Internet Draft, IETF, RFC 2543.
SIP 逄愛君 SIP&SDP2 Industrial Technology Research Institute Computer & Communication Research Laboratories Elgin Pang Outline.
1 CCNA 2 v3.1 Module Intermediate TCP/IP CCNA 2 Module 10.
DNS: Revising the Current Protocol Matt Gustafson Matt Weaver CS522 Computer Communications University of Colorado, Colorado Springs.
Agenda Introduction to 3GPP Introduction to SIP IP Multimedia Subsystem Service Routing in IMS Implementation Conclusions.
AARNet Copyright 2011 Network Operations SIP Deep Dive Bill Efthimiou APAN33 SIP workshop February 2012.
SIP Greg Nelson Duc Pham. SIP Introduction Application-layer (signaling) control protocol for initiating a session among users Application-layer (signaling)
Session Initialization Protocol (SIP)
Via contains the address at which the originator is expecting to receive responses to this request. Mandatory To contains a display name and a SIP URI.
SIP Session Initiation Protocol Short Introduction Artur Hecker, ENST.
December 2007IETF 70 - SIPPING1 SIP URI Service Discovery using DNS-SD draft-lee-sip-dns-sd-uri-02 Presented by Henning Schulzrinne Jae Woo Lee & Henning.
Signaling & Network Control 7th Semester
DNS.
Session Initiation Protocol Team Members: Manjiri Ayyar Pallavi Murudkar Sriusha Kottalanka Vamsi Ambati Girish Satya LeeAnn Tam.
Microsoft Windows Server 2003 TCP/IP Protocols and Services Technical Reference Slide: 1 Lesson 17 Domain Name System (DNS)
NAT Traversal Speaker: Chin-Chang Chang Date:
1 Semester 2 Module 10 Intermediate TCP/IP Yuda college of business James Chen
Module 2: Implementing DNS to Support Active Directory
RFC 3361: DHCP Option for SIP Servers Speaker: Chung yu Wu Teacher: Quincy Wu.
PACKET ANALYSIS WITH WIRESHARK DHCP, DNS, HTTP Chanhyun park.
Jaringan Komputer Dasar OSI Transport Layer Aurelio Rahmadian.
Chapter 1: Introduction to Web Applications. This chapter gives an overview of the Internet, and where the World Wide Web fits in. It then outlines the.
1 © NOKIA 1999 FILENAMs.PPT/ DATE / NN SIP Service Architecture Markus Isomäki Nokia Research Center.
Call Control with SIP Brian Elliott, Director of Engineering, NMS.
Session Initiation Protocol (SIP). What is SIP? An application-layer protocol A control (signaling) protocol.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 OSI Transport Layer Network Fundamentals – Chapter 4.
CCNA 1 v3.0 Module 11 TCP/IP Transport and Application Layers.
Presented By Team Netgeeks SIP Session Initiation Protocol.
TCP/IP Honolulu Community College Cisco Academy Training Center Semester 2 Version 2.1.
DNS SRV and NAPTR Use for SPEERMINT - Tom Creighton, Gaurav Khandpur Comcast SPEERMINT Intermin Meeting Philadelphia Sept
7/6/20061 Speermint Use Case for Cable IETF 66 Yiu L. Lee JULY 2006.
Rhodes University 29 October 2002,Robert V MasangoCopyright 2002, Rhodes University, SIP User SIP User Agent The IRT is the oldest of the New York City.
1 SPEERMINT Use Cases for Cable IETF 66 Montreal 11 JULY 2006 Presented by Yiu L. Lee.
SIP:Session Initiation Protocol Che-Yu Kuo Computer & Information Science Department University of Delaware May 11, 2010 CISC 856: TCP/IP and Upper Layer.
Simon Millard Professional Services Manager Aculab – booth 402 The State of SIP.
Draft-elwell-sipping- redirection-reason-00 Author: John Elwell
March 2007IETF68 - SIP1 SIP URI Service Discovery using DNS-SD draft-lee-sip-dns-sd-uri-00 Henning Schulzrinne Jae Woo Lee Columbia University.
SIP working group IETF#70 Essential corrections Keith Drage.
©Stephen Kingham SIP Protocol overview SIP Workshop APAN Taipei Taiwan 23rd Aug 2005 By Stephen Kingham
SIP Performance Benchmarking draft-ietf-bmwg-sip-bench-term-01 draft-ietf-bmwg-sip-bench-meth-01 March 22, 2010 Prof. Carol Davids, Illinois Inst. of Tech.
Teacher:Quincy Wu Presented by: Ying-Neng Hseih
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:
1 RFC4028 Session Timer in the Session Initiation Protocol Speaker : Ying Shun Lin Adviser : Quincy Wu.
Slide #1 Nov 6 -11, 2005SIP WG IETF64 Feature Tags with SIP REFER draft-ietf-sip-refer-feature-param-00 Orit
The Session Initiation Protocol - SIP
© 2002, Cisco Systems, Inc. All rights reserved..
Postech DP&NM Lab Session Initiation Protocol (SIP) Date: Seongcheol Hong DP&NM Lab., Dept. of CSE, POSTECH Date: Seongcheol.
Chapter 7: Transport Layer
Chapter 9: Transport Layer
SIP Protocol overview SIP Workshop APAN Taipei Taiwan 23rd Aug 2005
Instructor Materials Chapter 9: Transport Layer
ECRIT Interim: SIP Location Conveyance
Location SIP Servers –RFC 3261
Session Initiation Protocol (SIP)
An introduction to Transactions & Dialogs
Real Time Streaming Protocol
SIP Basics Workshop Dennis Baron July 20, 2005.
網際網路電話系統 期中考重點整理.
Presentation transcript:

1 RFC 3486 Compressing the Session Initiation Protocol (SIP) 曾朝弘 電機系 系統組 碩士班一年級

2 Outline Introduction Overview of operation Sending a Request to a Server Sending a Response to a Client Error Situations Example Security Considerations References Summary

3 Introduction

4 Introduction (cont) When NAPTR or SRV records are available for the server, the client can specify the type of service it wants. A SIP server that supports, for instance, three different transport protocols, will have three different DNS entries.

5 Introduction (cont) DNS RR(DNS resource records) 擁有者 (Owner) ex:ncnu.edu.tw 存留時間 (TTL) 類別 (Class) ex:IN(Internet) 類型 (Type) ex:SRV 、 NAPTR 記錄特定的資料 (RDATA) 語法 service.protocol.name ttl class SRV priority weight port target ex: _foo._tcp IN SRV ncnu.edu.tw _boo._udp IN SRV ncnu.edu.tw SRV RFC 2782 、 NAPTR RFC 2915 、 DNS RR RFC 1183

6 Introduction (cont) A server that, for example, supported TCP and SCTP as transports, TLS for transport security and SigComp for signaling compression, would need the 8 DNS entries listed below: 1. TCP, no security, no compression 2. TCP, no security, SigComp 3. TCP, TLS, no compression 4. TCP, TLS, SigComp 5. SCTP, no security, no compression 6. SCTP, no security, SigComp 7. SCTP, TLS, no compression 8. SCTP, TLS, SigComp

7 Overview of operation There are two types of SIP messages : SIP request SIP response Clients send SIP requests to the host part of a URI and servers send responses to the host in the sent-by parameter of the Via header field.

8 Overview of operation (cont) We define two parameters, one for SIP URIs and the other for the Via header field. The format of both parameters is the same, as shown in the examples below: Via: SIP/2.0/UDP alice.ncnu.edu.tw:5060; branch=z9hG4bK87a7;comp=sigcomp

9 Overview of operation (cont) The presence of this parameter (comp=sigcomp) in a URI indicates that the request has to be compressed using SigComp. The presence of comp=sigcomp in a Via header field indicates that the response has to be compressed using SigComp. Signaling Compression (SigComp) RFC 3320

10 Sending a Request to a Server If a user agent client sends a compressed request, it SHOULD add the parameter comp=sigcomp to the URI in the Contact header field. If a client sends a compressed request, it SHOULD add the parameter comp=sigcomp to the topmost entry of the Via header field. If a proxy that Record-Routes sends a compressed request, it SHOULD add comp=sigcomp to its URI in the Record-Route header field.

11 Sending a Request to a Server A client MUST NOT send a compressed request to a server if it does not know whether or not the server supports SigComp. If a client does not know whether or not the server supports SigComp, but in case the server supported it, it would like to receive compressed responses, this client SHOULD add the parameter comp=sigcomp to the topmost entry of the Via header field.

12 Sending a Response to a Client If the topmost Via header field contains the parameter comp=sigcomp, the response SHOULD be compressed. Otherwise, the response MUST NOT be compressed. If this URI contains the parameter comp=sigcomp, the proxy SHOULD add comp=sigcomp to its entry in the Record- Route header field.

13 Error Situations If a compressed SIP request arrives to a SIP server that does not understand SigComp, the server will not have any means to indicate the error to the client. The message will be impossible to parse, and there will be no Via header field indicating an address to send an error response.

14 Error Situations(cont) If a SIP client sends a compressed request and the client transaction times out without having received any response, the client SHOULD retry the same request without using compression. If the compressed request was sent over a TCP connection, the client SHOULD close that connection and open a new one to send the uncompressed request.

15 Example The call flow of Figure shows an INVITE-200 OK-ACK handshake between a UAC and a UAS through two proxies. Proxy Server1 does not Record-Route but proxy Server2 does. Both proxies support compression, but they do not use it by default. Only some parts of each message are shown, namely the Method name, the Request-URI and the Via, Route, Record-Route and Contact header fields.

16 Example (cont) 1. INVITE UAS Via: UAC;comp=sigcomp Route: P1;comp=sigcomp Contact: UAC;comp=sigcomp 2. INVITE UAS Via: P1 Via: UAC;comp=sigcomp Route: P2 Contact: UAC;comp=sigcomp 3. INVITE UAS Via: P2 Via: P1 Via: UAC;comp=sigcomp Record-Route: P2 Contact: UAC;comp=sigcomp OK Via: P2 Via: P1 Via: UAC;comp=sigcomp Record-Route: P2 Contact: UAS OK Via: P1 Via: UAC;comp=sigcomp Record-Route: P2;comp=sigcomp Contact: UAS OK Via: UAC;comp=sigcomp Record-Route: P2;comp=sigcomp Contact: UAS 7. ACK UAS Via: UAC;comp=sigcomp Route: P2;comp=sigcomp Contact: UAC;comp=sigcomp 8. ACK UAS Via: P2 Via: UAC;comp=sigcomp Contact: UAC;comp=sigcomp

17 Security Considerations A SIP entity receiving a compressed message has to decompress it and to parse it. This requires slightly more processing power than only parsing a message. This implies that a denial of service attack using compressed messages would be slightly worse than an attack with uncompressed messages.

18 References "SIP: Session Initiation Protocol", RFC 3261 "Signaling Compression (SigComp)", RFC 3320 "Key words for use in RFCs to indicate requirement levels", BCP 14, RFC 2119 "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403 "A DNS RR for specifying the location of services (DNS SRV)", RFC 2782 "DHCP option for SIP servers", RFC 3361

19 Summary This document describes a mechanism to signal that compression is desired for one or more Session Initiation Protocol (SIP) messages. When it is appropriate to send compressed SIP messages to a SIP entity. Effect header: Request-URI and the Via, Route, Record-Route and Contact.