FeatureSpec

This page and its children are a brainstorming sandbox capturing thinking on the level to characterize the requirements in the SIP specifications for use in, for example, an IESG interoperability statement for advancing each document.

We know we don't want to replicate each MUST/SHOULD/MAY, but instead want to capture "features" that encapsulate groups of those requirements.

For example, we would rather identify a feature like "A registrar successfully adds a binding against an AOR" rather than "A registrar returns a 200 OK to a REGISTER containing a contact not currently in the database and puts that contact int he 200 OK it returns". And we particularly don't want to repeat each of these with the combinitorial explosion of characterizing it with each possible knob you can turn ("Over UDP", "Using DIGEST authentication").

The short term goal will to be to capture a few such statements for

• A registrar
• A registering client
• A UA placing an invite
• A proxy forwarding a message