 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
Hi Art, ~snip~ # What we're really talking about here seems to be how to apply SIP to urgent one-to-many notifications. Maybe if it were explicit that narrower, more technical goal would be more tractable. For me the scope of the work is quite narrow. I re-wrote the requirements, terminology and framework document http://tools.ietf.org/id/draft-norreys-ecrit-authority2individuals-requireme nts-03.txt based also on your feedback to re-scope the work. Then, there is the SIP CAP document http://tools.ietf.org/html/draft-rosen-sipping-cap-04 (It needs to get re-written a bit to better incorporate the new terminology. Maybe requesting specific warning categories is a bad idea and needs to be deleted.) There is also a document http://tools.ietf.org/id/draft-rosen-ecrit-lost-early-warning-01.txt that may be needed to discover servers dynamically. But this is clearly more into the future. Looking at the XMPP work http://xmpp.org/extensions/xep-0127.html we could get away with only a single document, namely the SIP CAP stuff. I would scope the initial work in that way. Ciao Hannes - Art