The Experts below are selected from a list of 6342 Experts worldwide ranked by ideXlab platform
Jonathan Rosenberg - One of the best experts on this subject based on the ideXlab platform.
-
identification of communications services in the session initiation protocol sip
RFC, 2010Co-Authors: Jonathan RosenbergAbstract:This document considers the problem of service identification in the session initiation protocol (SIP). Service identification is the process of determining the user-level use case that is driving the signaling being utilized by the user agent. This document discusses the uses of service identification, and outlines several architectural principles behind the process. It identifies several perils associated with service identification, including fraud, interoperability failures and stifling of innovation.
-
indicating support for interactive connectivity establishment ice in the session initiation protocol sip
RFC, 2010Co-Authors: Jonathan RosenbergAbstract:This specification defines a media feature tag and an option tag for use with the session initiation protocol (SIP). The media feature tag allows a UA to communicate to its registrar that it supports ICE. The option tag allows a User Agent (UA) to require support for ICE in order for a call to proceed.
-
obtaining and using globally routable user agent uris gruus in the session initiation protocol sip
RFC, 2009Co-Authors: Jonathan RosenbergAbstract:Several applications of the session initiation protocol (SIP) require a user agent (UA) to construct and distribute a URI that can be used by anyone on the Internet to route a call to that specific UA instance. A URI that routes to a specific UA instance is called a Globally Routable UA URI (GRUU). This document describes an extension to SIP for obtaining a GRUU from a registrar and for communicating a GRUU to a peer within a dialog.
-
guidelines for usage of interactive connectivity establishment ice by non session initiation protocol sip protocols
2008Co-Authors: Jonathan RosenbergAbstract:Interative Connectivity Establishment (ICE) has been specified as a NAT traversal mechanism for protocols based on the offer/answer exchange model. In practice, only the session initiation protocol (SIP) has been based on the offer/answer model. This document defines a SIP independent subset of ICE, called NICE, which can be used with any protocol wishing to establish a direct host-to-host relationship through NAT. protocol specifications need only reference this document, and include the object defined here in their messages, in order to achieve NAT traversal.
-
construction of the route header field in the session initiation protocol sip
2006Co-Authors: Jonathan RosenbergAbstract:The Route header field in the session initiation protocol (SIP) is used to cause a request to visit a set of hops on its way towards the final destination. Several specifications have defined rules for how a user agent obtains and then uses a set of Route header fields in the transmission of a request. These include the SIP specification itself, the Service-Route header field specification, the SIP server option in the Dynamic Host Configuration protocol (DHCP), and others. Unfortunately, these specifications are not consistent and the resulting behavior at clients and servers is not clear or complete. This document resolves this problem by defining a consistent set of logic, and in the process, serves as an update to the Service-Route specification.
Gonzalo Camarillo - One of the best experts on this subject based on the ideXlab platform.
-
requirements from session initiation protocol sip session border control sbc deployments
RFC, 2010Co-Authors: Medhavi Bhatia, Gonzalo Camarillo, Alan Hawrylyshen, Robert F Penfield, Jani HautakorpiAbstract:This document describes functions implemented in session initiation protocol (SIP) intermediaries known as session Border Controllers (SBCs). The goal of this document is to describe the commonly provided functions of SBCs. A special focus is given to those practices that are viewed to be in conflict with SIP architectural principles. This document also explores the underlying requirements of network operators that have led to the use of these functions and practices in order to identify protocol requirements and determine whether those requirements are satisfied by existing specifications or additional standards work is required.
-
study on maintenance operations in a chord based peer to peer session initiation protocol overlay network
International Parallel and Distributed Processing Symposium, 2009Co-Authors: Jouni Maenpaa, Gonzalo CamarilloAbstract:Peer-to-Peer session initiation protocol (P2PSIP) is a new technology being standardized in the Internet Engineering Task Force. A P2PSIP network consists of a collection of nodes organized in a peer-to-peer fashion for the purpose of enabling real-time communication using the session initiation protocol (SIP). In this paper, we present experimental results obtained by running a P2PSIP prototype in PlanetLab. Our prototype uses the Chord Distributed Hash Table (DHT) to organize the P2PSIP overlay and Peer-to-Peer protocol (P2PP) as the protocol spoken between the peers. In the experiments, the performance of the system is studied under different churn rates and using different DHT maintenance intervals.
-
requirements from sip session initiation protocol session border control deployments
2006Co-Authors: Gonzalo CamarilloAbstract:This documents describes functions implemented in session initiation protocol (SIP) intermediaries known as session Border Controllers (SBCs). Although the goal of this document is to describe all the functions of SBCs, a special focus is given to those practices that are viewed to be in conflict with SIP architectural principles. It also explores the underlying requirements of network operators that have led to the use of these functions and practices in order to identify protocol requirements and determine whether those requirements are satisfied by existing specifications or additional standards work is required.
-
the session initiation protocol sip p user database private header p header
RFC, 2006Co-Authors: Gonzalo Camarillo, G BlancoAbstract:This document specifies the session initiation protocol (SIP) P-User- Database Private-Header (P-header). This header field is used in the 3rd-Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) to provide SIP registrars and SIP proxy servers with the address of the database that contains the user profile of the user that generated a particular request. This memo provides information for the Internet community.
-
the stream control transmission protocol sctp as a transport for the session initiation protocol sip
RFC, 2005Co-Authors: Gonzalo Camarillo, Jonathan Rosenberg, Henning SchulzrinneAbstract:This document specifies a mechanism for usage of SCTP (the Stream Control Transmission protocol) as the transport mechanism between SIP (session initiation protocol) entities. SCTP is a new protocol that provides several features that may prove beneficial for transport between SIP entities that exchange a large amount of messages, including gateways and proxies. As SIP is transport-independent, support of SCTP is a relatively straightforward process, nearly identical to support for TCP. [STANDARDS-TRACK]
Vijay K Gurbani - One of the best experts on this subject based on the ideXlab platform.
-
A Survey and Analysis of Media Keying Techniques in the session initiation protocol (SIP)
2016Co-Authors: Vijay K Gurbani, Vladimir KolesnikovAbstract:Abstract—Exchanging cryptographic keys to encrypt the me-dia stream in the session initiation protocol (SIP) has proven difficult. The challenge is to effectively exchange keys while preserving the features of the protocol (e.g., forking, re-targeting, request recursion, etc.), minimizing key exposure to unintended parties, eliminating voice clipping, maintaining end-to-end key privacy, interfacing with PSTN, etc. In this paper, we survey three key management protocols — SDES, ZRTP and DTLS-SRTP — that have been proposed for media keying, and evaluate them for use with SIP. To aid in the evaluation, we first extract (and justify) a core feature set from SIP. We then survey each key management protocol in detail and proceed to analyze the cores of the three protocols against this feature set to annotate their weaknesses and strengths
-
The session initiation protocol (SIP): An Evolutionary Study
2013Co-Authors: Salman Abdul Baset, Vijay K Gurbani, Alan B Johnston, Hadriel Kaplan, Brian Rosen, Jonathan D RosenbergAbstract:Abstract — The session initiation protocol (SIP) was developed to control multi-media sessions on the Internet. Shortly after its debut as a standard in 1999, SIP was adopted by the 3rd Generation Partnership Project (3GPP) as the preferred signaling protocol for the Internet Multimedia Subsystem (IMS). This adoption provided a boost to the nascent protocol as traditional telecommunication services were interpreted in the context of the new protocol and as SIP introduced richer services in the form of instant messaging and rich presence to traditional telephony. In this paper, we study the evolution of the protocol from its roots to its use in operational networks today and the issues it faces in such networks. We also provide a glimpse to the continued progression of SIP in Peer-to-Peer (P2P) networks and take a critical look at where SIP has succeeded, and more importantly, where it has failed to meet expectations
-
The Common Log Format (CLF) for the session initiation protocol (SIP): Framework and Information Model
2013Co-Authors: Tricha Anjali, Vijay K Gurbani, Olivier Festor, Humberto Abdelnur, Eric W. BurgerAbstract:Well-known web servers such as Apache and web proxies like Squid support event logging using a common log format. The logs produced using these de facto standard formats are invaluable to system administrators for troubleshooting a server and tool writers to craft tools that mine the log files and produce reports and trends. Furthermore, these log files can also be used to train anomaly detection systems and feed events into a security event management system. The session initiation protocol (SIP) does not have a common log format, and, as a result, each server supports a distinct log format that makes it unnecessarily complex to produce tools to do trend analysis and security detection. This document describes a framework, including requirements and analysis of existing approaches, and specifies an information model for development of a SIP common log file format that can be used uniformly by user agents, proxies, registrars, and redirect servers as well as back-to-back user agents.
-
on using multiple classifier systems for session initiation protocol sip anomaly detection
International Conference on Communications, 2012Co-Authors: Anil Mehta, Vijay K Gurbani, Neda Hantehzadeh, Flavia SanderAbstract:The session initiation protocol (SIP) is an important multimedia session establishment protocol used on the Internet. It is a text-based protocol, which is complex to parse due to the wide variability in representing the information elements. Building a parser for SIP may appear straight-forward; however, writing an efficient, robust, and scalable parser that is immune to low-effort attacks using malformed messages is surprisingly difficult. To mitigate this, self-learning systems based on Euclidean distance classifiers have been proposed to determine whether a message is well-formed or not. The efficacy of such machine learning algorithms must be studied on varied data sets before they can be successfully used. Our previous work has shown that Euclidean distance-based classifiers and standard classifiers used for self-learning problems are unable to detect malformed self-similar SIP messages (i.e., invalid SIP messages that differ by only a few bytes from normal SIP messages). This paper proposes using multiple classifier systems to detect malformed self-similar SIP messages. Our results show that a judiciously constructed multiple classifier system yields classification performance as high as 97.56% of the messages being classified correctly. We further show that for self-similar SIP messages, feature reduction measures based on the first moment are insufficient for improving classification accuracy.
-
statistical analysis of self similar session initiation protocol sip messages for anomaly detection
New Technologies Mobility and Security, 2011Co-Authors: Neda Hentehzadeh, Vijay K Gurbani, Anil Mehta, Lalit Gupta, Gayan WilathgamuwaAbstract:The session initiation protocol (SIP) is an important multimedia session establishment protocol used on the Internet. Due to the nature and deployment realities of the protocol (ASCII message representation, widespread usage over UDP, limited use of encryption), it becomes relatively easy to attack the protocol at the message level to launch denial of service attacks. To mitigate this, self- learning systems have been proposed to detect anomalous SIP messages and filter them. However, previous works use datasets with large differences between the normal and anomalous message. This gives high performance for existing classification systems, including those based on Euclidean distances. We present our analysis on a new dataset that has minimal difference between normal and anomalous messages. Our findings indicate that existing classification schemes behave unsatisfactorily on our dataset. We demonstrate why this is the case by statistical analysis of our dataset, and furthermore, present feature reduction techniques to enhance the classification performance of existing classification schemes on our dataset.
Olivier Festor - One of the best experts on this subject based on the ideXlab platform.
-
The Common Log Format (CLF) for the session initiation protocol (SIP): Framework and Information Model
2013Co-Authors: Tricha Anjali, Vijay K Gurbani, Olivier Festor, Humberto Abdelnur, Eric W. BurgerAbstract:Well-known web servers such as Apache and web proxies like Squid support event logging using a common log format. The logs produced using these de facto standard formats are invaluable to system administrators for troubleshooting a server and tool writers to craft tools that mine the log files and produce reports and trends. Furthermore, these log files can also be used to train anomaly detection systems and feed events into a security event management system. The session initiation protocol (SIP) does not have a common log format, and, as a result, each server supports a distinct log format that makes it unnecessarily complex to produce tools to do trend analysis and security detection. This document describes a framework, including requirements and analysis of existing approaches, and specifies an information model for development of a SIP common log file format that can be used uniformly by user agents, proxies, registrars, and redirect servers as well as back-to-back user agents.
-
The Common Log File (CLF) format for the session initiation protocol (SIP)
2009Co-Authors: Olivier Festor, Vijay K Gurbani, Tricha Anjali, Humberto Abdelnur, Eric W. BurgerAbstract:Well-known web servers such as Apache and web proxies like Squid support event logging using a common log format. The logs produced using these de-facto standard formats are invaluable to system administrators for trouble-shooting a server and tool writers to craft tools that mine the log files and produce reports and trends. Furthermore, these log files can also be used to train anomaly detection systems and feed events into a security event management system. The session initiation protocol does not have a common log format, and as a result, each server supports a distinct log format that makes it unnecessarily complex to produce tools to do trend analysis and security detection. We propose a common log file format for SIP servers that can be used uniformly for proxies, registrars, redirect servers as well as back-to-back user agents.
-
The Common Log File (CLF) format for the session initiation protocol (SIP) - draft-gurbani-sipping-clf-01
2009Co-Authors: Gurbani Vijay, Humberto Abdelnur, Tricha Anjali, Burger Eric, Olivier FestorAbstract:Well-known web servers such as Apache and web proxies like Squid support event logging using a common log format. The logs produced using these de-facto standard formats are invaluable to system administrators for trouble-shooting a server and tool writers to craft tools that mine the log files and produce reports and trends. Furthermore, these log files can also be used to train anomaly detection systems and feed events into a security event management system. The session initiation protocol does not have a common log format, and as a result, each server supports a distinct log format that makes it unnecessarily complex to produce tools to do trend analysis and security detection. We propose a common log file format for SIP servers that can be used uniformly for proxies, registrars, redirect servers as well as back-to-back user agents.
Henning Schulzrinne - One of the best experts on this subject based on the ideXlab platform.
-
a session initiation protocol sip load control event package
RFC, 2014Co-Authors: Henning Schulzrinne, Charles Shen, Arata KoikeAbstract:This specification defines a load-control event package for the session initiation protocol (SIP). It allows SIP entities to distribute load-filtering policies to other SIP entities in the network. The load-filtering policies contain rules to throttle calls from a specific user or based on their source or destination domain, telephone number prefix. The mechanism helps to prevent signaling overload and complements feedback-based SIP overload control efforts.
-
session initiation protocol (SIP) session Mobility
2009Co-Authors: Srisakul Thakolsri, Henning Schulzrinne, Ron Shacham, Wolfgang KellererAbstract:session mobility is the transfer of media of an ongoing communication session from one device to another. This document describes the general methods and specifies the signaling and media flows for providing this service using the session initiation protocol (SIP). Service discovery is essential to locate targets for session transfer and is discussed using the Service Location protocol (SLP) as an example.
-
session initiation protocol sip server overload control design and evaluation
arXiv: Networking and Internet Architecture, 2008Co-Authors: Charles Shen, Henning Schulzrinne, Erich M NahumAbstract:A session initiation protocol (SIP) server may be overloaded by emergency-induced call volume, ``American Idol'' style flash crowd effects or denial of service attacks. The SIP server overload problem is interesting especially because the costs of serving or rejecting a SIP session can be similar. For this reason, the built-in SIP overload control mechanism based on generating rejection messages cannot prevent the server from entering congestion collapse under heavy load. The SIP overload problem calls for a pushback control solution in which the potentially overloaded receiving server may notify its upstream sending servers to have them send only the amount of load within the receiving server's processing capacity. The pushback framework can be achieved by either a rate-based feedback or a window-based feedback. The centerpiece of the feedback mechanism is the algorithm used to generate load regulation information. We propose three new window-based feedback algorithms and evaluate them together with two existing rate-based feedback algorithms. We compare the different algorithms in terms of the number of tuning parameters and performance under both steady and variable load. Furthermore, we identify two categories of fairness requirements for SIP overload control, namely, user-centric and provider-centric fairness. With the introduction of a new double-feed SIP overload control architecture, we show how the algorithms can meet those fairness criteria.
-
a session initiation protocol sip event package for conference state
RFC, 2006Co-Authors: Jonathan Rosenberg, Henning Schulzrinne, Orit LevinAbstract:This document defines a conference event package for tightly coupled conferences using the session initiation protocol (SIP) events framework, along with a data format used in notifications for this package. The conference package allows users to subscribe to a conference Uniform Resource Identifier (URI). Notifications are sent about changes in the membership of this conference and optionally about changes in the state of additional conference components. [STANDARDS-TRACK]
-
the stream control transmission protocol sctp as a transport for the session initiation protocol sip
RFC, 2005Co-Authors: Gonzalo Camarillo, Jonathan Rosenberg, Henning SchulzrinneAbstract:This document specifies a mechanism for usage of SCTP (the Stream Control Transmission protocol) as the transport mechanism between SIP (session initiation protocol) entities. SCTP is a new protocol that provides several features that may prove beneficial for transport between SIP entities that exchange a large amount of messages, including gateways and proxies. As SIP is transport-independent, support of SCTP is a relatively straightforward process, nearly identical to support for TCP. [STANDARDS-TRACK]
