<div>Hi Juha,</div>
<div> </div>
<div>Well, that is true, but what do you propose then? just present a host cert and nothing else? I would say that if the company trust the hosting for running the service, a mere certficate should not be the problem, should it?
</div>
<div> </div>
<div>Cesc<br><br> </div>
<div><span class="gmail_quote">On 10/13/05, <b class="gmail_sendername">Juha Heinanen</b> <<a href="mailto:jh@tutpro.com">jh@tutpro.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">cesc,<br><br>you made a good summary, but in multi-domain case, it is not just a<br>technical problem on how to present or offer a domain specific
<br>certificate. in order to be able to do that, the domains have to<br>surrender their private keying information to a provider that currently<br>happens to host their sip service, and to another provider that hosts<br>
their web service, and to third provider that hosts their e-commerce<br>service, etc.<br><br>in most cases, this is simply out of question. companies are not going<br>to do it.<br><br>-- juha<br></blockquote></div><br>