Re: Comment on draft-roach-sipcore-rfc3265bis-00
Bob Penfield <[email protected]>
| Newsgroups | gmane.ietf.sip |
|---|---|
| Message-ID | <E6C2E8958BA59A4FB960963D475F7AC314F9762869@mail> |
>GRUU is not what one would call a wildly successful mechanism, yet, and we don't yet >know what all of its deployment issues will be using it in INVITEs. And the most >popular implementation we've seen using gruu doesn't even use the right param name >(it uses an older gruu draft's param name). I think its way too early to make any judgment on the success of GRUU since it is not even an RFC yet. Many vendors have made the smart decision to not implement things in their core products until there is an RFC. When folks start implementing it, INVITE will likely be the first place they do. Mainly for call transfer use cases as well as subscriptions related to the INVITE usage. _______________________________________________ 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