Mikhail Zabaluev
Email: <mikhail.zabaluev+telepathy@gmail.com>
Ideas and proposals on Telepathy API development
Add negotiations as sub-entities (zero, one or more) belonging to a MediaStreamHandler, move remote codecs, remote candidates, codec intersections and candidate pair selection there.
- Fix candidate data structures to accommodate ICE.
- Indication of call phases that would include "ringing".
- A channel authentication API that would encompass password- and certificate-based authentication.
- API to implement call transfer (SIP REFER, RFC 3515), both sending and receiving scenarios.
- OMA Presence SIMPLE accommodations:
- Contact Groups identifiable by handles with "technical" IDs; resolve the display name through Aliasing?
Representation of geolocation data in presence (see also RFC 4479); how to reconcile XEP-0080 for XMPP with PIDF-LO for SIP from the point of view of the client? Rely on GeoClue data formats?