Problem Statement and Possible Best Practices for Authentication of SIP+ XMPP Clients
draft-ivov-sipxmpp-auth-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Emil Ivov , Enrico Marocco | ||
| Last updated | 2010-03-02 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ivov-sipxmpp-auth-01.txt
Abstract
This document discusses several mechanisms for simplifying authentication of dual-stack SIP+XMPP clients against the corresponding SIP and XMPP services. The text is not attempt to define a complex credential sharing protocol but rather to determine and eventually encourage use of a simple mechanism that would allow service providers to host a SIP+XMPP solution appearing as a single service to their users. In other words, the goal here is to agree on a set of recommendations that would encourage client developers to implement simple UIs that would only require users to provide an ID and a password when configuring their SIP+XMPP account for the first time (as opposed to having to do so separately for SIP and XMPP).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)