As soon as you let a committee near any subject, you will invariably get complication. Every protocol I have worked on in standards bodies has invariably got more complicated. Two years after commencement someone comes in with a xxx-LITE version, which if it ever starts grows even more heavyweight that the original before being abandoned. The only programming language I have seen that pretty much managed to do away with all options was Pascal - designed by one person and then imposed on the world by force of personality. Dean would like to go to SIP 3.0 and do the same thing, but unfortunately the world is not listening, and are busy developing SIP 2.0 instead. Regards Keith > -----Original Message----- > From: sipping-bounces@xxxxxxxx > [mailto:sipping-bounces@xxxxxxxx] On Behalf Of Adrian Georgescu > Sent: Wednesday, October 22, 2008 7:09 PM > To: Paul Kyzivat > Cc: sipping@xxxxxxxx > Subject: Re: [RAI] Expert review of > draft-sinnreich-sip-tools-03 > > > On Oct 22, 2008, at 6:30 PM, Paul Kyzivat wrote: > > > Most who have worked on sip for awhile would probably agree > that if we > > could start over with a clean slate and all that we now > know we could > > create something simpler and better. But there is too much > investment > > in implementations of what we have, making a clean slate > infeasible. > > We are stuck with what we can do in an evolutionary way. > > I wish we do not have to be stuck in the infinite complexity > created by our past mistakes. Unless you are talking about > some terminal desease or the like you can always fix a bad > decision your took in the past with a good decision you take now. > > Or to quote from a book I read "Any mistakes you commit > through audacity are easily corrected with more audacity". > Don't know who wrote this. > > Adrian > > _______________________________________________ > Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping > This list is for NEW development of the application of SIP > Use sip-implementors@xxxxxxxxxxxxxxx for questions on current > sip Use sip@xxxxxxxx for new developments of core SIP > _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
