Draft: draft-sinnreich-sip-tools-04
Reviewer: Paul Kyzivat
Review Date: 8 January 2009
Review Deadline: 31 December 2009
Status: Expert (re-)Review

Review Summary: 

Henry's past summary of intent of document: 
--------------------------------------------
This version is a best effort to make SIP attractive to the web industry.

Paul's comments:
----------------

It feels to me like this is only part of the story if that is your goal. 
I think maybe you need something like an architecture document that talks specifically about the network topologies you are advocating, and how the standards are used to achieve certain things. Thats not a suggestion to redesign this document - rather it might be something additional.

I think there is still ambiguity about the relation to the pstn. On one hand you seem to want to exclude it entirely. But then you waffle and suggest that it could be available via gateways that deal with all the ugly parts. If so, I don't think you are talking about the existing sorts of gateways, which don't hide the ugly parts you don't want to deal with.

It would be simpler if you just narrowed scope to exclude any consideration of the pstn. You just need to make a case that when you do that there is still something useful left.

I *think* you have in mind that it should be possible to have a sip url on a web page as a hot link, just as you can have an http url. And when
*anybody* clicks on it in any browser, something good happens and you get a connection. So maybe you are looking for something that can be implemented as a browser addon package that does that.