SIP development, evolution, …

In traditional IETF fashion development is based on running code

So in your projects you should make sure that what you propose is really feasible by implementing it!
- should have at least 2 interoperable implementations for each feature
See the SIP mailing list (listen until you have sufficient knowledge to contribute)
See the SIP Working Group for what is being worked on by others
See “Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP)” [RFC 4485]

Slide Notes

J. Rosenberg and H. Schulzrinne, “Guidelines for Authors of Extensions to the Session Initiation Protocol (SIP)”, IETF, Network Working Group, RFC 4485, May 2006, http://datatracker.ietf.org/doc/rfc4485/

Transcript

[slide179] So there are active mailing lists. There's bunches of people working on it, and there's even a guideline for authors of extensions to tell you how to go about doing extensions.