Re: Fwd: I-D ACTION:draft-rosenberg-sip-target-uri-delivery-01.txt
"Spencer Dawkins" <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <[email protected]> |
> I think most everyone in the SIP Forum knows how the mechanism could work > using HI. The question was if we wanted to solve the issue using HI for > the SIP-Connect profile. I think the rationale for "no" was the feeling > we had on whether PBX's would actually support HI anytime soon, or whether > in practice we would actually be doing something different in deployment > to actually make calls work. (though I can't really speak for others - I > could be totally wrong on that, this was just the sense I got) > Speaking only for myself, I thought that the obstacle for SIPconnect was that there was already a history-info-bis effort underway - we just weren't excited about requiring support for a mechanism that was being revised. It wasn't clear to me that we would be equally unexcited if 4244bis was approved for publication. But as Hadriel says, I could also be totally wrong about that. And other people don't have to be shy about explaining things to me. Thanks, Spencer > Personally, I look at it from a motivation perspective: who has the > motivation to change to make something work? In the SIP-Connect case, the > Service Provider is the one selling the SIP-Trunk service, so to win the > deal and satisfy customers they've got more of the motivation/burden to > make it work. The SP's also have a large motivation to support as many > IP-PBX vendors as possible. Any changes we mandate of IP-PBX vendors will > reduce the pool of them that are "SIP-Connect compliant", which is not > good. Especially when what we're proposing basically works *now* in > SIP-Trunk deployments - i.e., there's running code. It doesn't quite work > that way today within the SP's domain on the wire, but as I said they have > the motivation (and the ability) to change their side. > > -hadriel > > _______________________________________________ > Sip mailing list https://www.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use [email protected] for questions on current sip > Use [email protected] for new developments on the application of sip > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [email protected] for questions on current sip Use [email protected] for new developments on the application of sip