Debian real-time communication (RTC) project - SIP
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Developers,
The Debian Project now has a SIP service available to all Debian
Developers. Your Debian.org email identity becomes your SIP address.
SIP enables a whole new world of real-time multimedia communications
possibilities: video/webcam, audio, chat, desktop sharing and
distributed, federated messaging are the most common use cases.
Details about how to get started and get support are explained in the
User Guide[1] in the Debian wiki. As it is a wiki, you are completely
welcome to help it evolve.
I will be at the Paris mini-DebConf this weekend (18-19 January)[2] and
would be delighted to discuss this project with you in person and
understand the first experiences people have using it.
The password for this real time communication service can be set via
the https://db.debian.org webfrontend. Please note that this password
needs to be different to any of your other existing debian.org
passwords. Please use a strong password and please keep it secure.
XMPP/Jabber is also a very compelling technology and there are plans to
offer that in parallel with the SIP service. Some of the
infrastructure, like the TURN server, will be shared by clients of both
protocols. The release of the SIP service ahead of XMPP should not be
taken as a sign that Debian prefers one standard over the other.
A key feature of this SIP deployment is that it supports federated
inter-connectivity with other SIP domains from the outset. Please try
it. For details of how it works and how we establish trust between
domains, please see RFC 5922[3]. Please reach out to other communities
you are involved with and help them consider enabling SIP federation of
their own communities/domains: as Metcalfe's law[4] suggests, each extra
person or community that embraces open standards like SIP and XMPP has
more than just an incremental impact on the value of these standards and
makes them more pervasive. To find out more about enabling another
domain for federated RTC, see the RTC quick-start guide[5]
This service has been made possible by a significant effort by the DSA
team over the last few weeks. Real-time communications systems are
particularly demanding on network latency, connectivity, authentication
schemes and various other things that do not always overlap with the
profiles of other resources that DSA are supporting. Therefore, it is a
great endorsement of the caliber of the team and the quality of the
systems they have in place that they have been able to get this running
so quickly.
Regards,
Daniel
1.
https://wiki.debian.org/UnifiedCommunications/DebianDevelopers/UserGuide
2. http://france.debian.net/events/minidebconf2014/
3. http://tools.ietf.org/html/rfc5922
4. http://en.wikipedia.org/wiki/Metcalfe%27s_law
5. http://www.rtcquickstart.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBCAAGBQJS2jdHAAoJEOm1uwJp1aqD9acP/AyleioiUwOKR0iMRd/iO8Gx
0ufLqsHArrNcXAeDu+0J6NbBGnrV86dBLHz+1oSPzO99feJKKNIYbI7f+e2nUMEZ
DPLcsJnA9otXu0ck1K6Je45ZnhIK/RqVfuAFjqsPeckbI3CaF6MS2Tbrczsc1UGg
hfNU3edZc64oLn84BTShVQsnd0AWMps4r0TLviAcBPmpNrSMUi73kJOWY2i4mNJr
R6Kmj6Ys9f1q6tQS4wwTOHQCpzZXlH2u3cWcnmLa+GwwgkUeOB0ytMcRO1vRmgEg
SckSnS+9UPRe2RpTebcoBxDKJemNBRPJqLD2u9IVoBrOURkaSnnDCFFvf6qgR1q/
36eqbC1RoswPsta7SyJKwHiwRFJj5qd8fHupj9sPruMArorDz5T0myJTFh/OZJmq
MQLiycBJC24POGshwcj/3/+T6a+N9+jvz5ethYXFmjEIyOMjFilJDuGJWkHF4Yx2
X9rP3shSdDoCE6qY6YXhf5XtPCjCMrfzIGqHsO1EYqQQj4c61YyMZfWr31EddkhQ
XPcd226Y9GU5VEY5kD82qlirMKbvU18+LfRz9ROrKfgwJ+hLpm//AnTIaOJF5kvY
5mFKQ+kobs5Xoq7F1Ngi2bJYEqlveTwxqtT6h5OFuHz4WdkBpqb2U7bqS0n+vpT7
avlq5BQxrYQF9rD8+ZA6
=eKBQ
-----END PGP SIGNATURE-----
Reply to: