[VOIPSEC] SIP complexity, was VPNs and VoIP

Simon Horne s.horne at packetizer.com
Mon Jul 31 09:37:15 CDT 2006


At 08:43 PM 31/07/2006, you wrote:
>All I am really saying is that SIP is a good start.  But in my mind
>something better might be needed.  Something designed from the ground up for
>security, and management, but not necessarily ease of use.  As an end user,
>how often are you expected to know what a SIP invite is?  As someone who
>deals with networks and VoIP of many varieties on a daily basis, I'd rather
>have a protocol that is more complex, but does everything we want it to
>versus something "the masses" can hack on.

The ITU are starting to drafting a new VoIP standard H.325 which seek to 
build a VoIP protocol from the ground up. Taking the best parts of H.323 
and SIP and include security, NAT traversal, management, extensibility and 
incorporating it to a homogeneous framework. Unfortunately there has been 
very little interest thus far from any major players in the VoIP market to 
help peruse the idea.

Information
http://www.packetizer.com/voip/h325/

Here is brief outline presentation of what is about
http://www.packetizer.com/voip/h325/papers/h325_third_generation_multimedia.pdf

Simon


> > -----Original Message-----
> > From: Voipsec-bounces at voipsa.org
> > [mailto:Voipsec-bounces at voipsa.org] On Behalf Of Geoff Devine
> > Sent: Monday, July 31, 2006 7:09 AM
> > To: Voipsec at voipsa.org
> > Subject: Re: [VOIPSEC] SIP complexity, was VPNs and VoIP
> >
> > Michael Slavitch writes:
> >
> > > "Given the incredible complexity of SIP"
> > >
> > > Buh?  SIP is simple. It's the bellheads who made it hard.
> >
> > Nope.  It's the protocol designers who invented a protocol
> > without first looking at the functional requirements who made
> > it hard.  Instead, we end up with hundreds of IETF RFCs with
> > hack workarounds to the deficiencies in the original RFC 3261
> > spec.  Anyone who has architected a telephone system can tell
> > you that an architecture that can make a simple line to line
> > phone call is trivial.  An architecture that can do all the
> > features and meet all the requirements is difficult.
> >
> > Geoff
> >
> > _______________________________________________
> > Voipsec mailing list
> > Voipsec at voipsa.org
> > http://voipsa.org/mailman/listinfo/voipsec_voipsa.org
>
>
>_______________________________________________
>Voipsec mailing list
>Voipsec at voipsa.org
>http://voipsa.org/mailman/listinfo/voipsec_voipsa.org






More information about the Voipsec mailing list