If there is a group that has been working on making XCAP useful for everyone it is OMA for sure, with the XDM specification, not IETF or even 3GPP, which I think is the big issue of almost none adoption in SIP clients.
Btw, I wonder what is the problem with a auid name, that actually follows the XCAP rfc guidelines for 3rd parties app usages. The real good change would be for IETF, OMA and 3GPP to actually work together before RFCs get out... -- Eduardo On Wed, Jun 17, 2009 at 5:34 PM, Paul Kyzivat<pkyzi...@cisco.com> wrote: > > > Iñaki Baz Castillo wrote: > >> Thanks for so great explanation. >> >> However, I wonder why so many new features are needed when most of the >> devices >> don't implement XCAP yet. The fact I don't consider useful all the new >> features described above. Is it really implemented "somewhere"? > > I suspect the simple answer is that they don't care what you want. > They are designing for 3gpp/IMS, to build a closed system that supports > the features they want. I imagine they don't need or want to talk to > your systems or devices. > > Thanks, > Paul > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
