Not a scholarly view, anyways... IMHO the reason new specs use elements from old ones - even cross protocol - is because any protocol is essentially trying to solve a communication problem. Therein, like in design patterns, some patterns start to emerge - we can coin the term "protocol patterns" - and these are the things that start to spring up in new protocols like you mentioned.(request-response is an example of what i call a protocol pattern). These are possibly what you term "re-use"
May be the authors of the specifications deemed it fit to use protocol patterns from older standards that addressed the same problem.Also they MAY have a factor bearing on their mind that since these protocols were time-tested (existing for a long time), and adaptation of an older standard to a new one with possible enhancements/reductions/tweaks might not throw any surprises :). May be they messed up too. Cheers Harsha On 27/03/2008, Michael Giagnocavo <[EMAIL PROTECTED]> wrote: > > > Honest curiosity: Why do the new specs keep using elements from old specs? > Not within the same protocol, but cross-protocol. You can trace the SIP > features Inaki is complaining about all the way back to the early 1970s. > There's gotta be a real compelling reason to keep moving these things > forwards (like dates having the day-of-week and using 3-letter English > abbreviations), right? > > -Michael > > _______________________________________________ > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
