SIGNAL Magazine
[email protected] (John D. Ramsdell)
| Newsgroups | gmane.ietf.impp |
|---|---|
| Message-ID | <[email protected]> |
In case you've seen the SIGNAL Magazine article on SIMP at http://www.us.net/signal/CurrentIssue/May02/collaborative-may.html let me explain the IETF IMPP reference. The article states that the SIMP protocol was given to the IMPP working group, but, of course, that was long ago in Internet time, and the SIMP protocol used in the exercise, http://simp.mitre.org/download/simp.txt, has not been modified to reflect recent decisions taken by this group. Had I seen the article before it went out, I would have requested that this paragraph be reworded. Our team is committed to IMPP standards. We are designing and implementing a new SIMP protocol. The goal of the new protocol is to make it easy to exchange messages with other IMPP standards compliant systems through gateways, while maintaining the security features of the original SIMP protocol. In particular, the protocol supports the authentication of all requests using digital signatures, and allows server side access control decisions using those signatures. This is the reason I have recently been asking how to sign SUBSCRIBE requests. There are problems with signing NOTIFY requests too, but that's another story. John [reminder: [email protected] for non-technical discussions, please]