Re: using third-party infrastructure for SIP and XMPP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 13/11/15 18:56, Kevin Fenzi wrote:
> On Fri, 13 Nov 2015 09:09:49 +0100 Daniel Pocock
> <daniel@xxxxxxxxxx> wrote:
> 
>> I'm starting this as a separate thread to offer an alternative 
>> solution for hosting SIP and XMPP.
>> 
>> Basically, I would be happy to continue running the services on
>> my own infrastructure with the fedoraproject.org domain.  I'm
>> running Xen Cloud Platform in a data center with plenty of
>> bandwidth (both IPv4 and IPv6).
>> 
>> There are two things that the Fedora infrastructure team would
>> still need to assist with though:
>> 
>> a) creating the DNS SRV and NAPTR records under fedoraproject.org
>> to direct all SIP and XMPP activity to the servers
>> 
>> b) providing TLS certificates for fedoraproject.org 
>> sip-ws.fedoraproject.org turn.fedoraproject.org to be installed
>> on the servers.  Wildcard certificates are not valid for SIP.
>> 
>> Running the services with the fedoraproject.org domain will
>> engage more people and allow me to launch an XMPP service, which
>> isn't running at all on fedrtc.org due to the potential
>> inconvenience if people had to move buddy lists to
>> fedoraproject.org in future.
> 
> I don't like this plan at all I'm afraid. ;)
> 
> I would be much more likely to want to stand up an instance and see
> how much use it gets and if it doesn't get enough, retire it.
> 

I suspected this would be the response, especially considering the
requirement for certificates/key pairs.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJWRiTvAAoJEOm1uwJp1aqDqHoP/iSSI/54TG+6pHjA7JXFFk/Y
fQMmatqnhTe1ArS5HrxRVmKbigPuz9htRlwNSlhYaAauA/25GLlMO+51R4jpyD0v
R+18u2+ZR3KPOvbCYSpfTRDcMDcNBdgLu6c+y434d2YW+rvtVffw5d8xJ7TojZIL
El2aP3eQvFBRYOpLh7IlGipJ+o5xAwUQu/OJHdKNgBk4Dw1bBbevwl9ynLAYQ+8r
f+4Gpk0/qD8Ts3hy7AqMf2Jc87KCGbOVnXHPvbw08RQ68UUdM+ytfOaaW6z5rKyh
J9TRSK4qgAUDFkqxUne+8Pw1r0nKu48tdenDeSV5twB0P00L1/22ZcSbda4Jv0Mn
+AfyKtClbf80Uf1K3EpoJ8bmEQjNFG3sm4pTqKMBP2vdiKc2uYQ0lLZDB6CBtLm0
ZfywSp/N/oaomrOCVctgi2Sdkn35QofohJi2OrL5Nenyhg83ddAe6TuWmgj875GP
/NW6QSEhorHVDhgd4grMWp4tAtsC3Cgtrj9MttKvVZHlPYq/JNrCMGtwp7MDes5v
1a+5gqUtIl38UOkXB4iEu7EmvbI7V/XoBcLQcHRrU6YicZXCbjpgM8tTksZknezr
w74IHLQyG61p9RbH/UF97oy+BBhqxwGSchlmib+mxUdKO9D6ZL9wVgD2vxhUYRQn
z/pzgf3yxy1txXu+oZC5
=MAiK
-----END PGP SIGNATURE-----
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux