[Operators] debian.org SIP and XMPP

Daniel Pocock daniel at pocock.com.au
Sun Jan 19 21:28:36 UTC 2014


On 19/01/14 10:46, Dave Cridland wrote:
> On Sun, Jan 19, 2014 at 8:43 AM, Daniel Pocock <daniel at pocock.com.au
> <mailto:daniel at pocock.com.au>> wrote:
>
>     As mentioned in the other email, FOSDEM is coming up, maybe that
>     will be
>     an opportunity to discuss in person?  (Please don't let my .au domain
>     deceive you, I'm based in central Europe)
>
>
> Sadly, I don't think Matt is joining us this time around; perhaps this
> might change his mind, though. There'll certainly be other Prosody
> developers present, though, I'd hope.
>
> We've a two day "summit" meeting beforehand, as well; I imagine that
> begging an hour or so from our chair, Kev, on Friday afternoon would
> be easy enough, if you'd like a marginally less distracting setting.
> We're out in Cisco's offices, in Diegem, near the airport.

I arrive a little bit early for FOSDEM so I may be able to come and
gatecrash the summit or we could rendez vous on the way to the opening
ceremony at Delirium

Just some initial discussion points for the Debian implementation, if
anybody could comment on any of these areas we could start building up a
wiki about it and that will evolve into the project plan:

a) the DSA team always prefer to use packages from the stable
distribution (or the stable backports), is there any compelling reason
we should not use those versions for this project?  Here they are:
http://packages.qa.debian.org/p/prosody.html
- stable= 0.8.2
- backports = 0.9.1
I see 0.9.2 is on the Prosody web site - to get that into backports
probably takes at least three weeks anyway

b) Debian Developers have been given RTC passwords for TURN and SIP and
hopefully XMPP.  They are hashed using HA1 for DIGEST/HMAC algorithms
such as SIP and TURN.  Can XMPP use these password hashes or do we need
to hash them in some other format?

c) the user passwords are available in two ways: we can supply a text
file directly to the server (see the format used by reTurn, link below)
or via a FreeRADIUS server with the rlm_digest module - can Prosody use
either of these solutions or do we need to come up with something else?

reTurn users.txt sample (we use HA1 in the third column now):
https://github.com/resiprocate/resiprocate/blob/master/reTurn/users.txt

FreeRADIUS rlm_digest: http://freeradius.org/radiusd/man/rlm_digest.txt

d) IPv6 - any new stuff we do in Debian has to be dual stack, should
this be fine with Prosody?

e) other dependencies, e.g. databases.  Debian infrastructure currently
uses PostgreSQL (no MySQL) but if possible, using no database at all,
keeping each process somewhat self-contained.  Looking at the package
dependencies, I see that several databases are suggested.  Could anybody
comment on just how compelling it is to use a full SQL database, can we
happily use the sqlite3 driver, etc?

f) collaboration with the SIP infrastructure: is there any practical way
to share presence services, chat messages or anything else just yet?  We
don't have any presence server for SIP right now, it would be nice to
plan the strategy for that alongside the XMPP planning


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/operators/attachments/20140119/61d174aa/attachment.html>


More information about the Operators mailing list