IMS, 3GPP and IETF: A standardization complexity
September 3, 2007
How do we get those specifications for IMS? In a complex way.
It started off as a set if requirements for a Next Generation Network (NGN). The 3GPP wanted an all-IP network for its mobile infrastructure, calling it IMS (IP Multimedia Subsystem). As there’s no need to reinvent the wheel, the 3GPP decided to select an existing standard to do the work, and SIP was there – all young and fresh. But SIP is an RFC. It is handled and standardized by the IETF. This need not be changed.
So what does an organization like the 3GPP does at this point in time? Use the IETF as a subcontractor.
Have you ever worked with a subcontractor? I have never heard of anyone who liked the experience… you provide requirements for a rocket to space, and you get a fire cracker. You want a match, and you get a rocket instead. Time is not time, effort estimations are far from true (sounds like regular development, but it is always harder with a subcontractor).
So we have the 3GPP providing the requirements, while the development of new RFCs (=standards for IMS) done by the IETF, including modifications to RFCs when needed.
The result?
- We have a whole lot of RFCs coming from the IETF. Some colliding each other, others solving the same problems, but a bit differently.
- We have a bunch of 3GPP specifications, which point to RFCs (and a lot of drafts!) that are used by the 3GPP’s IMS network – in a way, a selection of the RFCs that are needed.
- But then, it is not always understood which features from the IETF, or the 3GPP you really need to build an application. And as usual, I haven’t covered GSMA, GCF, OMTP and other organizations.
We at the IMTC IMS AG are actually facing these issue each day. We are currently unraveling the set of specifications required for the implementation and interoperability of the Video Sharing service that is gaining momentum.
Technorati Tags: IMS, IETF, SIP, SigComp, 3GPP, Standardization, Tsahi Levent-Levi
.
Why do we need marketers in standard bodies?
April 5, 2007
By Kfir Pravda
Ok, I am a marketer. I have engineering background, but I am certainly on the “let’s find the story” side than the “where to plug this router” side. And I can tell you, I think that standardization process needs more marketers around.
So now you ask yourself why, right?
The answer is simple – the current process takes too much time. As such, it makes standards irrelevant from business perspective. We are talking about SIP for ages. Skype has bigger market share. Why? Cause engineers and marketers set together and solved problems based on specific use cases. So, engineers should be happy to have marketers around – not for advice, but in order to sort out all the different issues on the table between companies.
Standards suppose to support services and products. Therefore, they are supposed to be based on some kind of requirements. These requirements should be, in my opinion, based on market needs. And market needs are represented by marketers, not by engineering functions.
So why in most standardization organizations we have almost no representation? Even IMTC, the organization publishing this blog have only one marketer on board (yours truly).
What is your opinion?
