Skip Links

Network World

  • Social Web 
  • Email 
  • Close

The mandate for SIP to be interoperable

SIP is a good example of a technology that is very slowly being standardized
Wide Area Networking Alert By Steve Taylor and Jim Metzler , Network World , 07/24/2008
Steve Taylor
Sign up for this newsletter now!

WAN experts Steve Taylor and Jim Metzler analyze and share best practices on WAN issues from optimization to management.

  • Share/Email
  • Comment
  • Print

This is the sixth and last in a series of newsletters devoted to the standards process. We will use this newsletter to wrap up the discussion of standards by looking at Session Initiation Protocol. We look at SIP as being a good example of a technology that is very slowly being standardized. According to Wikipedia, SIP was originally designed by Henning Schulzrinne (Columbia University) and Mark Handley (University College of London) starting in 1996. The latest version of the specification is RFC 3261 from the IETF SIP Working Group.

SIP is a signaling protocol, widely used for setting up and tearing down multimedia communication sessions such as voice and video calls over the Internet. Other feasible application examples include video conferencing, streaming multimedia distribution, instant messaging, presence information and online games. The protocol can be used for creating, modifying and terminating two-party (unicast) or multiparty (multicast) sessions consisting of one or several media streams. We believe strongly that in order for SIP to have an impact, it has to be interoperable so that IT organizations use it to set up multimedia communication sessions and not worry about which vendor created which end point device.

However, to date, most IP implementations have not provided the necessary interoperability.

For example, at the Spring VoiceCon conference the results of a SIP survey was presented. This was the fourth year that the survey was given and as before, it was given only to vendors who are supporting or implementing SIP in new or re-engineered products.

The vendors were asked to rate the state of current SIP specifications from all sources on a scale of 1 to 5 with 5 meaning 'complete, clear, stable and unambiguous' and 1 meaning 'minimal to no standardization yet; or incomplete or ambiguous; needs a lot of work.' Our interpretation of this scale is that if a vendor rated a given SIP specification a 3, that the vendor believes that there is a moderate amount of standardization associated with that particular SIP specification.

The good news is that 'Basic dozen telephony features' was rated 4.7, up from last year’s rating of 4.4. The bad news is that relatively few other SIP specs rated a 4 or higher. SIP specifications that rated between 3 and 4 included SIP trunking, NAT/firewall traversal, audio-conference scheduling, unified messaging and find-me`/follow me. In addition, a handful of specifications rated below 3.

Steve Taylor is president of Distributed Networking Associates and publisher/editor-in-chief of Webtorials. Jim Metzler is vice president of Ashton, Metzler & Associates.

  • Share/Email
  • Comment
  • Print
Partner Content

Simplify Your Branch Infrastructure

Learn how to simplify your branch infrastructure while dramatically increasing app performance with Citrix Branch Repeater.

Download the Free Info Kit

Next-Gen Load Balancing

Free Guide: "Next Gen Load Balancing: 8 Things You Need to Handle Today's Network Traffic" shows you the functionality needed in your next load balancer.

Download the Free Guide

Accelerate Your Web Apps by up to 5x

Free Guide: "The Secret to Getting Maximum Speed from your Web Applications." Learn how you can deliver Web apps up to 5x faster.

Download the Free Guide

Comments (2)
Login
Forgot your account info?

do the survey results exist on the webBy Anonymous on July 24, 2008, 3:11 pmI went looking but could not find the survey results - is there a link- thanks

Reply | Read entire comment

The mandate for SIP to be interoperableBy Anonymous on July 24, 2008, 8:57 amThe Session Initiation Protocol (SIP) was truly a wondrous idea and noble concept. Unfortunately, the IETF is "Design by Committee". That is what happened to SIP....

Reply | Read entire comment

View all comments

Add comment
Anonymous comments subject to approval. Register here for member benefits.
Have a NetworkWorld account? Log in here. Register now for a free account.

Videos

rssRss Feed