From nobody Wed Nov 4 06:39:20 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C583F1B30B9 for ; Wed, 4 Nov 2015 06:39:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.551 X-Spam-Level: X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K31FOPrC8A7a for ; Wed, 4 Nov 2015 06:39:16 -0800 (PST) Received: from duva.sjd.se (duva.sjd.se [IPv6:2001:9b0:1:1702::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43F511B30B7 for ; Wed, 4 Nov 2015 06:39:16 -0800 (PST) Received: from latte.josefsson.org ([155.4.17.2]) (authenticated bits=0) by duva.sjd.se (8.14.4/8.14.4/Debian-4) with ESMTP id tA4EdBVR011126 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 4 Nov 2015 15:39:12 +0100 From: Simon Josefsson To: Martin Thomson References: <562AA40E.40407@nostrum.com> <562E5F53.9060104@geekplace.eu> <5630C2C7.6030907@geekplace.eu> OpenPGP: id=54265E8C; url=http://josefsson.org/54265e8c.txt X-Hashcash: 1:22:151104:flo@geekplace.eu::P5a3m1DrvfxjXWxR:4Mcf X-Hashcash: 1:22:151104:xmpp@ietf.org::DDL4lgZIUtMDGUag:mjEf X-Hashcash: 1:22:151104:martin.thomson@gmail.com::JWxCzM7EG2dJSP8C:fWD2 Date: Wed, 04 Nov 2015 15:39:10 +0100 In-Reply-To: (Martin Thomson's message of "Thu, 29 Oct 2015 16:08:30 +0900") Message-ID: <878u6dn81d.fsf@latte.josefsson.org> User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.4 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-Virus-Scanned: clamav-milter 0.98.7 at duva.sjd.se X-Virus-Status: Clean Archived-At: Cc: XMPP Group Subject: Re: [xmpp] New(ish) draft: Secure Messaging in XMPP X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2015 14:39:18 -0000 --=-=-= Content-Type: text/plain Martin Thomson writes: > On 29 October 2015 at 09:02, Martin Thomson wrote: >> I don't think that Axolotl is a good model >> for the general use case. > > > Since Florian asked nicely, here's the text I wrote about a year ago > regarding PFS: > >>>> > For a system where the messages are stored, this is largely a > pointless exercise. Destroying the messages is also necessary to > ensure that they cannot be recovered. > > We value function over perfect security and consider logging to be a > critical part of a functional chat system. I believe there is a logical mistake here -- supporting logging does not mean you cannot support forward security. I'm firmly on the side that logging is an essential property of a chat system that I would use, however I acknowledge that NOT logging is an essential property of a chat system some other people would use. While forward security is less critical to the first category (something I'm not sure I would agree with fully), it appears essential to the second category. A system that supports forward security appears more general to me than one that doesn't. I would welcome a detailed analysis of pro's and con's between this proposal and OMEMO, to identify if there is anything the OMEMO approach could learn and pick up from this approach. /Simon > Furthermore, forward secrecy requires that a round trip between two > parties occurs to establish a properly ephemeral key. This means that > any initial message to any other device either cannot have forward > secrecy, or it cannot include any content. In the latter case, content > could only be carried once the receiving device has replied with their > ephemeral share. (Other systems address this in part by provisioning a > public store with shares ahead of any need for others to use them, but > these systems work poorly in multi-party scenarios.) > > In the case where there are multiple agents in a chat - a scenario we > consider to be critical for usability reasons - if any one user agent > is offline, any message encrypted for that agent has to use a key that > can only be unilaterally updated. Messages destined for the offline > agent will necessarily depend on the private keying material on that > agent, which cannot be updated. > <<< > > I think that there was a separate note about the value of PFS for some > exchanges. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBCAAGBQJWOhiOAAoJEIYLf7sy+BGdCc8H/1Tr5IFb0XDmvirrgqtIGCxI IcGzATHAUd/nX5xMxbjDbjUItxK3BL/PROsagB8IHAu87mMvw76zyACjan6F1d4m APahdMTSifN/mBR2KA/TPPDpfNjajnbgCLiNCNaFPy0OQq97HAKhSslv9cHcVenl CV88XxJOuZY8FIm3Wyhfvhw0RVff45T06LdQahg6jSKzoHy1EoLeEkAaP3fJ8CCK RsCzIoBrereSqCeO7UfsGYQ/KK1+/8qSIw+DTMFhlwp31G4YJeDwgQ6sqzMkLxYP OU0xey6Iayawm5jMIAppmUStJK0eEvf6ABCh1TRswd4zmSPsyPC1uN4rSu+hHo4= =3doO -----END PGP SIGNATURE----- --=-=-=-- From nobody Thu Nov 5 00:42:35 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4883D1A8A6E for ; Thu, 5 Nov 2015 00:42:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.1 X-Spam-Level: * X-Spam-Status: No, score=1.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MIME_8BIT_HEADER=0.3] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id THpkezIbIhiQ for ; Thu, 5 Nov 2015 00:42:31 -0800 (PST) Received: from mg0.tigase.org (mg0.tigase.org [192.99.18.159]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1101A8A6D for ; Thu, 5 Nov 2015 00:42:31 -0800 (PST) Received: from mail.tigase.org (mail.tigase.org [198.27.120.209]) by mg0.tigase.org (Postfix) with ESMTP id 12DAC12700E for ; Thu, 5 Nov 2015 03:42:31 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.tigase.org (Postfix) with ESMTP id 06D25140922 for ; Thu, 5 Nov 2015 03:42:31 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at mail.tigase.org Received: from mail.tigase.org ([198.27.120.209]) by localhost (t2.tigase.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h0tGwwOydA0J for ; Thu, 5 Nov 2015 03:42:10 -0500 (EST) Received: from [192.168.3.171] (host-86-111-123-175.tvk.torun.pl [86.111.123.175]) (Authenticated sender: bmalkow) by mail.tigase.org (Postfix) with ESMTPSA id 71AE3140698 for ; Thu, 5 Nov 2015 03:42:10 -0500 (EST) Content-Type: multipart/signed; boundary="Apple-Mail=_1E0F6102-C156-4AEF-954D-E11C55FF699D"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) X-Pgp-Agent: GPGMail 2.6b2 From: =?utf-8?Q?Bartosz_Ma=C5=82kowski?= In-Reply-To: <562AAAB1.9060906@andyet.net> Date: Thu, 5 Nov 2015 09:42:04 +0100 Message-Id: <72AA7469-6C93-4C52-BAD8-99A3933FE7AC@tigase.pl> References: <562AA40E.40407@nostrum.com> <562AAAB1.9060906@andyet.net> To: xmpp@ietf.org X-Mailer: Apple Mail (2.3096.5) Archived-At: Subject: Re: [xmpp] New(ish) draft: Secure Messaging in XMPP X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2015 08:42:32 -0000 --Apple-Mail=_1E0F6102-C156-4AEF-954D-E11C55FF699D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi! I=E2=80=99m curious why IQ stanzas should be encapsulated into IQ = stanzas instead of Message stanza. I think that any kind of stanza what should be protected by e2e = encryption should be encrypted and encapsulated with Message stanza. = Then this Message is only transport layer. -- Bartosz Ma=C5=82kowski Tigase Polska xmpp:bmalkow@malkowscy.net --Apple-Mail=_1E0F6102-C156-4AEF-954D-E11C55FF699D Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iQF8BAEBCgBmBQJWOxZdXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNjBEQjY2NTU3RTQ0RjQ4NUI4Rjg2OERB ODAxRDY5QkQwRUNDNkUzAAoJEKgB1pvQ7MbjCS8H/3MlCvy7F8QvWDgQ/dJG1WaG c9b7vwhL+aCFel3U/af9649BlE66OQiUndTBmNiBfWtzXN5L5pxgYKkU1JrG0bKb OQau4DBt9PkJVv4MBNC60LZ2NWKoGFVVC5CsDK7gjmZKNZefyv8MKeDfGh4s0KkG FJkzOkB4syZ1yjzl5W2635HmNWcHEF6ICRJ5+vxBigBrUQxhYqgGrk5OTM/yuoyx bT1GijaWL+QaK98pgeNG9p2cB5azqbzliU94tiYU1Xsu88mfhCnNt2/K9kN8Ncet oFFFeoFJDb6AecRGx5aQ3ePhH5BmdQtmufB6ufsBsy5cVM2/Uk7UIrWPqYfRSoQ= =eWhX -----END PGP SIGNATURE----- --Apple-Mail=_1E0F6102-C156-4AEF-954D-E11C55FF699D-- From nobody Thu Nov 5 01:46:45 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E63BA1A6F56 for ; Thu, 5 Nov 2015 01:46:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.078 X-Spam-Level: X-Spam-Status: No, score=-1.078 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ns_3Ak7yCNUf for ; Thu, 5 Nov 2015 01:46:42 -0800 (PST) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2D291A1B29 for ; Thu, 5 Nov 2015 01:46:42 -0800 (PST) Received: by oies6 with SMTP id s6so1621072oie.1 for ; Thu, 05 Nov 2015 01:46:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=mdrgDHyOW2Qdy6ZeqqqEfocBoDSRxzw6KswnM+A9TeY=; b=ekTw4lGDzwsP1LKBk//5twtz6qMoUsUY0x3AUzmF73bauIbSsVqMmUjy2tpy+Iwddu VI1O35Fz3I4zcmABblhJVpmm/HYJz/pjQ7jNJHfoHgNK5Cat6HVcOmHn7PobiwW8ZE2T HmbpAza1r7ejwb5PPviZaX7xWWTuBpv0j2CBk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mdrgDHyOW2Qdy6ZeqqqEfocBoDSRxzw6KswnM+A9TeY=; b=jTBnfQZJqBJDnOjaSgSltck1CdZXyE7hP6QhhychczZS+4VflfylshuGA36wHxE0Le 9ZHkQs9cWiV13k7sij99mIxDXnn37JYsMB5Tq8znosi1tvZtJFP0Tg/5Rf9Zd3N1Netn XFTS3bXx0a2w4XnPJW9Kla9zb9dHPPDiKri5KaNJqjYD7oPIbhI0Z7PxfP0DbgP5bC+1 miDH49AIU2SfFis8uuOQk6EwOKvzxCT6kfuO0Sxm28gWkasF+u5WOS+G3fvePOCwQEVi P5QG4Ls5H9ou6Ake6gkw1i6MykNxI4HyBnQSTFFSDCrmB6ql1HX1mCj0jOt7JeId8EJ2 EdoQ== X-Gm-Message-State: ALoCoQksNOHO3AuT28K30avSJYHBDWAEVme5J1LkH4v458cOJtcz5sBf2mP8OuxJUQ7KygCpM1r/ MIME-Version: 1.0 X-Received: by 10.202.197.82 with SMTP id v79mr3681115oif.31.1446716802214; Thu, 05 Nov 2015 01:46:42 -0800 (PST) Received: by 10.60.27.33 with HTTP; Thu, 5 Nov 2015 01:46:42 -0800 (PST) In-Reply-To: <72AA7469-6C93-4C52-BAD8-99A3933FE7AC@tigase.pl> References: <562AA40E.40407@nostrum.com> <562AAAB1.9060906@andyet.net> <72AA7469-6C93-4C52-BAD8-99A3933FE7AC@tigase.pl> Date: Thu, 5 Nov 2015 09:46:42 +0000 Message-ID: From: Dave Cridland To: =?UTF-8?Q?Bartosz_Ma=C5=82kowski?= Content-Type: multipart/alternative; boundary=001a113e23ca1645890523c801b6 Archived-At: Cc: XMPP Working Group Subject: Re: [xmpp] New(ish) draft: Secure Messaging in XMPP X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2015 09:46:44 -0000 --001a113e23ca1645890523c801b6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 5 November 2015 at 08:42, Bartosz Ma=C5=82kowski = wrote: > Hi! > > I=E2=80=99m curious why IQ stanzas should be encapsulated into IQ stanzas= instead > of Message stanza. > I think that any kind of stanza what should be protected by e2e encryptio= n > should be encrypted and encapsulated with Message stanza. Then this Messa= ge > is only transport layer. > > I think you want stanzas to be encapsulated as the same stanza in order to maintain the same semantics on, for example, routing, error handling, etc. > -- > Bartosz Ma=C5=82kowski > Tigase Polska > xmpp:bmalkow@malkowscy.net > > > _______________________________________________ > xmpp mailing list > xmpp@ietf.org > https://www.ietf.org/mailman/listinfo/xmpp > > --001a113e23ca1645890523c801b6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 5 November 2015 at 08:42, Bartosz Ma=C5=82kowski <<= a href=3D"mailto:bmalkowski@tigase.pl" target=3D"_blank">bmalkowski@tigase.= pl> wrote:
Hi!

I=E2=80=99m curious why IQ stanzas should be encapsulated into IQ stanzas i= nstead of Message stanza.
I think that any kind of stanza what should be protected by e2e encryption = should be encrypted and encapsulated with Message stanza. Then this Message= is only transport layer.


I think you want stanzas to be encapsu= lated as the same stanza in order to maintain the same semantics on, for ex= ample, routing, error handling, etc.
=C2=A0
--
Bartosz Ma=C5=82kowski
Tigase Polska
xmpp:bmalkow@malkowscy.net<= /a>


_______________________________________________
xmpp mailing list
xmpp@ietf.org
https://www.ietf.org/mailman/listinfo/xmpp


--001a113e23ca1645890523c801b6-- From nobody Thu Nov 5 02:12:12 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1DD1AC3E3 for ; Thu, 5 Nov 2015 02:12:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.6 X-Spam-Level: X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ooF18MScMFSe for ; Thu, 5 Nov 2015 02:12:09 -0800 (PST) Received: from mg0.tigase.org (mg0.tigase.org [192.99.18.159]) by ietfa.amsl.com (Postfix) with ESMTP id E90871AC3E4 for ; Thu, 5 Nov 2015 02:12:04 -0800 (PST) Received: from mail.tigase.org (mail.tigase.org [198.27.120.209]) by mg0.tigase.org (Postfix) with ESMTP id 3BC50127010; Thu, 5 Nov 2015 05:12:04 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by mail.tigase.org (Postfix) with ESMTP id 3249A140922; Thu, 5 Nov 2015 05:12:04 -0500 (EST) X-Virus-Scanned: Debian amavisd-new at mail.tigase.org Received: from mail.tigase.org ([198.27.120.209]) by localhost (t2.tigase.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3i6A1Zxly0k4; Thu, 5 Nov 2015 05:11:43 -0500 (EST) Received: from [192.168.3.171] (host-86-111-123-175.tvk.torun.pl [86.111.123.175]) (Authenticated sender: bmalkow) by mail.tigase.org (Postfix) with ESMTPSA id 30CCE14049A; Thu, 5 Nov 2015 05:11:43 -0500 (EST) Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Content-Type: multipart/signed; boundary="Apple-Mail=_CCCF85A3-7ADB-4960-AB3F-0E6E32AC8B5B"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.6b2 From: =?utf-8?Q?Bartosz_Ma=C5=82kowski?= In-Reply-To: Date: Thu, 5 Nov 2015 11:11:38 +0100 Message-Id: <5F9E4182-7149-479C-AD76-2B1E3B126E67@tigase.pl> References: <562AA40E.40407@nostrum.com> <562AAAB1.9060906@andyet.net> <72AA7469-6C93-4C52-BAD8-99A3933FE7AC@tigase.pl> To: Dave Cridland X-Mailer: Apple Mail (2.3096.5) Archived-At: Cc: XMPP Working Group Subject: Re: [xmpp] New(ish) draft: Secure Messaging in XMPP X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2015 10:12:11 -0000 --Apple-Mail=_CCCF85A3-7ADB-4960-AB3F-0E6E32AC8B5B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > Wiadomo=C5=9B=C4=87 napisana przez Dave Cridland w = dniu 05.11.2015, o godz. 10:46: >=20 > I think you want stanzas to be encapsulated as the same stanza in = order to maintain the same semantics on, for example, routing, error = handling, etc. My point of view is, that envelope is just an envelope and shouldn=E2=80=99= t be related to content. If I want to send = then I just send: enc() and in response I will receive enc() In case of using IQ envelope for IQ stanzas: what type of stanza should = have envelope if response type is error? Also error? enc() I think that envelope should be independent from content. Let it be IQ = stanza or Message stanza, but the same type of envelope for all type of = contents. -- Bartosz Ma=C5=82kowski Tigase Polska xmpp:bmalkow@malkowscy.net --Apple-Mail=_CCCF85A3-7ADB-4960-AB3F-0E6E32AC8B5B Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iQF8BAEBCgBmBQJWOytaXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNjBEQjY2NTU3RTQ0RjQ4NUI4Rjg2OERB ODAxRDY5QkQwRUNDNkUzAAoJEKgB1pvQ7MbjsQEH+wV+xSSpGqnbop1tiUraEsxx MKQLaAWRVTpkQfvrb1qeY6HF9XY4fRYvhJkPG2EF6LUFf3IlN9DyawMqwn/kQVzD mfSv+kbzQwD8KaT5cv+Ljenx6s8fOtGpmczi8zpKLUdOpjaiEaLsaMMnwPbomxvV 16E5oSf85rR1KE2deJYC/NxNm5lpEsb76StmwSm6JKPn9iuI0UZdSM5p9/tmVzOe DI5nMtpELRSwd+v62LPOThi5/I4gAz7SNIVrUYjs2+aK3rvUdgF/R9ebUbyhuTr+ 9MjIE3sIL9dcnS4TJhvrLQ27XQPu51kyPmDAQLyi8QsipTHeDNm375w8zWrwE5U= =2kZN -----END PGP SIGNATURE----- --Apple-Mail=_CCCF85A3-7ADB-4960-AB3F-0E6E32AC8B5B-- From nobody Sun Nov 8 22:33:24 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 244CB1A2119 for ; Sun, 8 Nov 2015 22:33:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.7 X-Spam-Level: X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cA7efQB0DAIe for ; Sun, 8 Nov 2015 22:33:22 -0800 (PST) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 479311A1F73 for ; Sun, 8 Nov 2015 22:33:22 -0800 (PST) Received: by ioc74 with SMTP id 74so110723280ioc.2 for ; Sun, 08 Nov 2015 22:33:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=zlefO/4k7sexCslC2YPBJulE4AAO0acIXp9nLh78SIk=; b=kZTxwwb9EdsYFwhaNi2yfMz6+Mwil1Af8nUZl2a6DQlcg9wc6qWYB0Zh44BON5ZNqC g1y6gFnD7GH1XdYKTq5rJ9/Nc1jrpZ8kzKV/jt0pFpy57uPa0aGn9eTeJB++3NBPkevb IcYbYro25cboKi8mSVl1qvpw2PWvPU5GJKt2Fe+oIEl73Doude0So3ZPGZe5GnlzICD/ d8//9ajUMab1C0+g12GtOB5flwqd/FR1VEJQCIDqlkeWQAXEe/GXrt5mT+KKNcPOIrdV EyWLY5NAIG2GGWjvMr7xgvIrr57LCCiGmBoUpVtvcjQgFsuMR6TxjhfBLg6xhN9zZhe9 b1rg== MIME-Version: 1.0 X-Received: by 10.107.33.211 with SMTP id h202mr22978060ioh.108.1447050801627; Sun, 08 Nov 2015 22:33:21 -0800 (PST) Received: by 10.36.155.7 with HTTP; Sun, 8 Nov 2015 22:33:21 -0800 (PST) In-Reply-To: <5F9E4182-7149-479C-AD76-2B1E3B126E67@tigase.pl> References: <562AA40E.40407@nostrum.com> <562AAAB1.9060906@andyet.net> <72AA7469-6C93-4C52-BAD8-99A3933FE7AC@tigase.pl> <5F9E4182-7149-479C-AD76-2B1E3B126E67@tigase.pl> Date: Sun, 8 Nov 2015 22:33:21 -0800 Message-ID: From: Martin Thomson To: =?UTF-8?Q?Bartosz_Ma=C5=82kowski?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Archived-At: Cc: XMPP Working Group Subject: Re: [xmpp] New(ish) draft: Secure Messaging in XMPP X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Nov 2015 06:33:23 -0000 On 5 November 2015 at 02:11, Bartosz Ma=C5=82kowski = wrote: > My point of view is, that envelope is just an envelope and shouldn=E2=80= =99t be related to content. I would have suggested that if it weren't for the reason Dave identified. Routing rules in XMPP are a little more complicated than might be ideal. message and iq are not routed consistently, nor do they receive the same store-and-forward treatment. From nobody Sat Nov 14 11:12:05 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72B911AD0B2 for ; Sat, 14 Nov 2015 11:12:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.912 X-Spam-Level: X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U9Yx9B6GkVuN for ; Sat, 14 Nov 2015 11:12:03 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 29C271AD0B1 for ; Sat, 14 Nov 2015 11:12:03 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id D4696180006; Sat, 14 Nov 2015 11:10:31 -0800 (PST) To: peter@andyet.com, ben@nostrum.com, alissa@cooperw.in, barryleiba@computer.org, jhildebr@cisco.com X-PHP-Originating-Script: 30:errata_mail_lib.php From: RFC Errata System Message-Id: <20151114191031.D4696180006@rfc-editor.org> Date: Sat, 14 Nov 2015 11:10:31 -0800 (PST) Archived-At: Cc: xmpp@ietf.org, swhited@atlassian.com, rfc-editor@rfc-editor.org Subject: [xmpp] [Editorial Errata Reported] RFC7622 (4534) X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Nov 2015 19:12:04 -0000 The following errata report has been submitted for RFC7622, "Extensible Messaging and Presence Protocol (XMPP): Address Format". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7622&eid=4534 -------------------------------------- Type: Editorial Reported by: Sam Whited Section: 3.2.2 Original Text ------------- An entity that performs enforcement in XMPP domainpart slots MUST prepare a string as described in Section 3.2.1 and MUST also apply the normalization, case-mapping, and width-mapping rules defined in [RFC5892]. Corrected Text -------------- An entity that performs enforcement in XMPP domainpart slots MUST prepare a string as described in Section 3.2.1 and MUST also apply the normalization, case-mapping, and width-mapping rules defined in [RFC5890]. Notes ----- RFC5892 is just a list of codepoints; the rules which it is referring too (and which are referred too in the ABNF and othe places in the document) are in RFC5890 Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC7622 (draft-ietf-xmpp-6122bis-24) -------------------------------------- Title : Extensible Messaging and Presence Protocol (XMPP): Address Format Publication Date : September 2015 Author(s) : P. Saint-Andre Category : PROPOSED STANDARD Source : Extensible Messaging and Presence Protocol Area : Applications and Real-Time Stream : IETF Verifying Party : IESG From nobody Thu Nov 19 15:55:20 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A0701B37D5; Thu, 19 Nov 2015 15:55:17 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.487 X-Spam-Level: X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qVL2t56BfE28; Thu, 19 Nov 2015 15:55:16 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id EA0581B37A2; Thu, 19 Nov 2015 15:55:15 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 79E32180014; Thu, 19 Nov 2015 15:53:53 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20151119235353.79E32180014@rfc-editor.org> Date: Thu, 19 Nov 2015 15:53:53 -0800 (PST) Archived-At: Cc: drafts-update-ref@iana.org, xmpp@ietf.org, rfc-editor@rfc-editor.org Subject: [xmpp] RFC 7711 on PKIX over Secure HTTP (POSH) X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 23:55:17 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7711 Title: PKIX over Secure HTTP (POSH) Author: M. Miller, P. Saint-Andre Status: Standards Track Stream: IETF Date: November 2015 Mailbox: mamille2@cisco.com, peter@andyet.com Pages: 18 Characters: 41302 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-xmpp-posh-06.txt URL: https://www.rfc-editor.org/info/rfc7711 DOI: http://dx.doi.org/10.17487/RFC7711 Experience has shown that it is difficult to deploy proper PKIX certificates for Transport Layer Security (TLS) in multi-tenanted environments. As a result, domains hosted in such environments often deploy applications using certificates that identify the hosting service, not the hosted domain. Such deployments force end users and peer services to accept a certificate with an improper identifier, resulting in degraded security. This document defines methods that make it easier to deploy certificates for proper server identity checking in non-HTTP application protocols. Although these methods were developed for use in the Extensible Messaging and Presence Protocol (XMPP) as a Domain Name Association (DNA) prooftype, they might also be usable in other non-HTTP application protocols. This document is a product of the Extensible Messaging and Presence Protocol Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Thu Nov 19 15:55:34 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 516761B37E5; Thu, 19 Nov 2015 15:55:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.487 X-Spam-Level: X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7h_vd007MITb; Thu, 19 Nov 2015 15:55:27 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id CC3561B37A2; Thu, 19 Nov 2015 15:55:27 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 5B7FE180011; Thu, 19 Nov 2015 15:54:05 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org X-PHP-Originating-Script: 1005:ams_util_lib.php From: rfc-editor@rfc-editor.org Message-Id: <20151119235405.5B7FE180011@rfc-editor.org> Date: Thu, 19 Nov 2015 15:54:05 -0800 (PST) Archived-At: Cc: drafts-update-ref@iana.org, xmpp@ietf.org, rfc-editor@rfc-editor.org Subject: [xmpp] RFC 7712 on Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP) X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 23:55:29 -0000 A new Request for Comments is now available in online RFC libraries. RFC 7712 Title: Domain Name Associations (DNA) in the Extensible Messaging and Presence Protocol (XMPP) Author: P. Saint-Andre, M. Miller, P. Hancke Status: Standards Track Stream: IETF Date: November 2015 Mailbox: peter@andyet.com, mamille2@cisco.com, fippo@andyet.com Pages: 24 Characters: 49879 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-xmpp-dna-11.txt URL: https://www.rfc-editor.org/info/rfc7712 DOI: http://dx.doi.org/10.17487/RFC7712 This document improves the security of the Extensible Messaging and Presence Protocol (XMPP) in two ways. First, it specifies how to establish a strong association between a domain name and an XML stream, using the concept of "prooftypes". Second, it describes how to securely delegate a service domain name (e.g., example.com) to a target server hostname (e.g., hosting.example.net); this is especially important in multi-tenanted environments where the same target server hosts a large number of domains. This document is a product of the Extensible Messaging and Presence Protocol Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/rfc.html Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From nobody Fri Nov 20 12:31:24 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D4931B3D5D for ; Fri, 20 Nov 2015 12:31:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.987 X-Spam-Level: X-Spam-Status: No, score=-1.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rrm9fQ1VIe8a for ; Fri, 20 Nov 2015 12:31:20 -0800 (PST) Received: from mag.ik.nu (mag.ik.nu [IPv6:2001:16f8:4::61]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CA5E1B3D5A for ; Fri, 20 Nov 2015 12:31:18 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mag.ik.nu (Postfix) with ESMTP id A9F031600A0; Fri, 20 Nov 2015 21:31:16 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mag.ik.nu Received: from mag.ik.nu ([127.0.0.1]) by localhost (mag.ik.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3J0PtTi1wXMJ; Fri, 20 Nov 2015 21:31:14 +0100 (CET) Received: from [192.168.1.77] (s53751670.adsl.online.nl [83.117.22.112]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ralphm) by mag.ik.nu (Postfix) with ESMTPSA id DB66C160092; Fri, 20 Nov 2015 21:31:13 +0100 (CET) References: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> To: XMPP Summit , XSF Members , XMPP Standards , xmpp@ietf.org From: Ralph Meijer X-Enigmail-Draft-Status: N1110 X-Forwarded-Message-Id: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> Message-ID: <564F8311.5010709@ik.nu> Date: Fri, 20 Nov 2015 21:31:13 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> Content-Type: multipart/mixed; boundary="------------050500050208090107050302" Archived-At: Cc: Jabber/XMPP software development list Subject: [xmpp] Fwd: [jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 20:31:23 -0000 This is a multi-part message in MIME format. --------------050500050208090107050302 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear all, Daniel Pocock sent out the attached Call for Participation for the FOSDEM 2016 Realtime Devroom, a devroom co-organised by the XSF and the telephony crowd. Unfortunately, we haven't gotten any XMPP-related talk proposals so far. I just noticed that the CfP never ended up in these other mailing lists, so maybe we messed this up or they got dropped in moderation. Please send in your proposals as soon as possible, by using the FOSDEM Pentabarf system, so we have some more great talks to promote XMPP in its many of its facets. XMPP Rocks! -- Cheers, ralphm --------------050500050208090107050302 Content-Type: message/rfc822; name="[jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded.eml" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename*0="[jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers "; filename*1="neeeded.eml" Return-Path: X-Original-To: ralphm@mag.ik.nu Delivered-To: ralphm@mag.ik.nu Received: from localhost (localhost [127.0.0.1]) by mag.ik.nu (Postfix) with ESMTP id 020161600D6 for ; Fri, 30 Oct 2015 21:16:39 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mag.ik.nu Authentication-Results: mag.ik.nu (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=pocock.pro header.b=jnK+X46h; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=pocock.pro header.b=evXFnjB2 Received: from mag.ik.nu ([127.0.0.1]) by localhost (mag.ik.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFowKGFG06OR for ; Fri, 30 Oct 2015 21:16:36 +0100 (CET) Received: from atlas.jabber.org (atlas.jabber.org [208.68.163.215]) by mag.ik.nu (Postfix) with ESMTP id 6561F1600D1 for ; Fri, 30 Oct 2015 21:16:36 +0100 (CET) Received: from [127.0.0.1] (atlas [127.0.0.1]) by atlas.jabber.org (Postfix) with ESMTP id 6880221B08A; Fri, 30 Oct 2015 20:15:32 +0000 (UTC) X-Original-To: JDev@jabber.org Delivered-To: JDev@jabber.org Received: from mail1.trendhosting.net (mail1.trendhosting.net [195.8.117.5]) by atlas.jabber.org (Postfix) with ESMTPS id 63E9E21B03B for ; Fri, 30 Oct 2015 20:13:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail1.trendhosting.net (Postfix) with ESMTP id 1583F15105 for ; Fri, 30 Oct 2015 20:13:13 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1446235993; bh=aZz4y4vECY+HBp5h2wlEPw6OihnMlNAw52eN5+Vvw3w=; h=To:Subject:From:Date:From; b=jnK+X46hN+e1zMEtmtK/IX8PaUUHQIZBYkGsIKMhIpEZn45Zq3T3V5qZGicxvHiNW svwisBanp2CXtoGmtIqNKAYLhlelLQeGjo0W8YIpLusOrdOgz4wXnSnsAZpsRU1b+s R9S87puiQfTEkqYAGcoVtsWhnwXraFdrtB1itUYs= Received: from mail1.trendhosting.net ([127.0.0.1]) by localhost (thp003.trendhosting.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tM79ks7g5i5c for ; Fri, 30 Oct 2015 20:13:08 +0000 (GMT) Received: from srv1.office.readytechnology.co.uk (unknown [192.168.1.2]) by mail1.trendhosting.net (Postfix) with ESMTP id 64F9E150B9 for ; Fri, 30 Oct 2015 20:13:08 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1446235988; bh=aZz4y4vECY+HBp5h2wlEPw6OihnMlNAw52eN5+Vvw3w=; h=To:Subject:From:Date:From; b=evXFnjB2v7S7FGY46FsBuI623V5iQ8PgJ4OjRNQX1xGjqgU4NdNzQC/D0SX6aBTBX fWvPl/fIL0TKWLDaBAcgGWUwVcakiGv2t68VzOSOSOnLXPTH0iPqWpj7jLfiUZ0JPL LMbAHzX/lsdtKKxoG/GA0+sID72sQJcCb3w8LQ0E= Received: from daniel1.office.readytechnology.co.uk (unknown [IPv6:2001:1620:b22::2042]) by srv1.office.readytechnology.co.uk (Postfix) with ESMTP id F1091C8EE for ; Fri, 30 Oct 2015 21:13:07 +0100 (CET) Received: by daniel1.office.readytechnology.co.uk (Postfix, from userid 1000) id 2F2AB321F8; Fri, 30 Oct 2015 21:13:06 +0100 (CET) To: JDev@jabber.org From: Daniel Pocock Message-Id: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> Date: Fri, 30 Oct 2015 21:13:06 +0100 (CET) Subject: [jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded X-BeenThere: jdev@jabber.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Jabber/XMPP software development list List-Id: Jabber/XMPP software development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0310488302==" Errors-To: jdev-bounces@jabber.org Sender: "JDev" --===============0310488302== Content-Type: text/plain FOSDEM is one of the world's premier meetings of free software developers, with over five thousand people attending each year. FOSDEM 2016 takes place 30-31 January 2016 in Brussels, Belgium. http://fosdem.org This email contains information about: - Real-Time communications dev-room and lounge, - speaking opportunities, - volunteering in the dev-room and lounge, - related events around FOSDEM, including the XMPP summit, - social events (including the Saturday night dinner), - the Planet aggregation sites for RTC blogs Call for participation - Real Time Communications (RTC) ======================================================= The Real-Time dev-room and Real-Time lounge is about all things involving real-time communication, including: XMPP, SIP, WebRTC, telephony, mobile VoIP, codecs, privacy and encryption. The dev-room is a successor to the previous XMPP and telephony dev-rooms. We are looking for speakers for the dev-room and volunteers and participants for the tables in the Real-Time lounge. The dev-room is only on Saturday, 30 January 2016. The lounge will be present for both days. To discuss the dev-room and lounge, please join the FSFE-sponsored Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc Speaking opportunities ---------------------- Note: if you used Pentabarf before, please use the same account/username Main track: the deadline for main track presentations is midnight today, 30 October. Leading developers in the Real-Time Communications field are encouraged to consider submitting a presentation to the main track at https://fosdem.org/submit Real-Time Communications dev-room: deadline 27 November Please also use the Pentabarf system to submit a talk proposal for the dev-room. On the "General" tab, please look for the "Track" option and choose "Real-Time devroom". https://penta.fosdem.org/submission/FOSDEM16/ Other dev-rooms: some speakers may find their topic is in the scope of more than one dev-room. It is permitted to apply to more than one dev-room but please be kind enough to tell us if you do this. You can find the full list of dev-rooms at https://www.fosdem.org/2016/schedule/tracks/ Lightning talks: deadline 27 November The lightning talks are an excellent opportunity to introduce a wider audience to your project. Given that dev-rooms are becoming increasingly busy, all speakers are encouraged to consider applying for a lightning talk as well as a slot in the dev-room. On the "General" tab, please look for the "Track" option and choose "Lightning Talks". https://fosdem.org/submit First-time speaking? -------------------- FOSDEM dev-rooms are a welcoming environment for people who have never given a talk before. Please feel free to contact the dev-room administrators personally if you would like to ask any questions about it. Submission guidelines --------------------- The Pentabarf system will ask for many of the essential details. Please remember to re-use your account from previous years if you have one. In the "Submission notes", please tell us about: - the purpose of your talk - any other talk applications (dev-rooms, lightning talks, main track) - availability constraints and special needs You can use HTML in your bio, abstract and description. If you maintain a blog, please consider providing us with the URL of a feed with posts tagged for your RTC-related work. We will be looking for relevance to the conference and dev-room themes, presentations aimed at developers of free and open source software about RTC-related topics. Please feel free to suggest a duration between 20 minutes and 55 minutes but note that the final decision on talk durations will be made by the dev-room administrators. As the two previous dev-rooms have been combined into one, we may decide to give shorter slots than in previous years so that more speakers can participate. Please note FOSDEM aims to record and live-stream all talks. The CC-BY license is used. For any questions, please join the FSFE-sponsored Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc Volunteers needed ================= To make the dev-room and lounge run successfully, we are looking for volunteers: - FOSDEM provides video recording equipment and live streaming, volunteers are needed to assist in this - organizing one or more restaurant bookings (dependending upon number of participants) for the evening of Saturday, 30 January - participation in the Real-Time lounge - helping attract sponsorship funds for the dev-room to pay for the Saturday night dinner and any other expenses - circulating this Call for Participation to other mailing lists FOSDEM is made possible by volunteers and if you have time to contribute, please feel free to get involved through https://volunteers.fosdem.org/ Related events - XMPP and RTC summits ===================================== The XMPP Standards Foundation (XSF) has traditionally held a summit in the days before FOSDEM. There is discussion about a similar summit taking place on 28 and 29 January 2016 http://wiki.xmpp.org/web/Summit_19 - please join the mailing list for details: http://mail.jabber.org/mailman/listinfo/summit We are also considering a more general RTC or telephony summit, potentially on 29 January. Please join the Free-RTC mailing list and send an email if you would be interested in participating, sponsoring or hosting such an event. Social events and dinners ========================= The traditional FOSDEM beer night occurs on Friday, 29 January On Saturday night, there are usually dinners associated with each of the dev-rooms. Most restaurants in Brussels are not so large so these dinners have space constraints. Please subscribe to the Free-RTC mailing list for further details about the Saturday night dinner options and how you can register for a seat: https://lists.fsfe.org/mailman/listinfo/free-rtc Spread the word and discuss =========================== If you know of any mailing lists where this CfP would be relevant, please forward this email. If this dev-room excites you, please blog or microblog about it, especially if you are submitting a talk. If you regularly blog about RTC topics, please send details about your blog to the planet site administrators: http://planet.jabber.org ralphm@ik.nu http://planet.sip5060.net daniel@pocock.pro http://planet.opentelecoms.org daniel@pocock.pro Please also link to the Planet sites from your own blog or web site. Contact ======= For discussion and queries, please join the free-rtc mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc The dev-room administration team: Daniel Pocock Ralph Meijer Saúl Ibarra Corretgé Iain R. Learmonth --===============0310488302== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: JDev-unsubscribe@jabber.org _______________________________________________ --===============0310488302==-- --------------050500050208090107050302-- From nobody Fri Nov 20 14:32:20 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A81F51B3F39 for ; Fri, 20 Nov 2015 14:32:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.878 X-Spam-Level: X-Spam-Status: No, score=-0.878 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, GB_ABOUTYOU=0.5, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JNJhEF22soWU for ; Fri, 20 Nov 2015 14:32:16 -0800 (PST) Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3783F1B3F3D for ; Fri, 20 Nov 2015 14:32:13 -0800 (PST) Received: by obbbj7 with SMTP id bj7so97605421obb.1 for ; Fri, 20 Nov 2015 14:32:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=77b4ZsZZGZljW77gAq+Unv4jKa27AcpLAdSjD1uURD8=; b=j7WdROeCME/xPBGto2BWmvWvzMVE6xmwvmnkhI9t2p6FS2M6yLNrnCueetmKi6EEIS XC4UYI0fUBV8tIz/HCpWEibD0tY18keT6IegSrE8itCboAbHbeUhoP+L4t6Wm1OWC/ck lObNL8qLH3MHoQRNd7O/+Po1WzYJHihUtrCio= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=77b4ZsZZGZljW77gAq+Unv4jKa27AcpLAdSjD1uURD8=; b=ZIaLnsmYlsRHgxFuxHYhtL7LjCusV7vjcRtT4cZGTFTUI7zpxaDMNwc/MDbNmbXwnR 1CDZnMhJK2UKwHPB7aam9VCyTVUG8FrrQ8nxVG5+2ucc1bqy/wiil/WekxwaMr4Gh2O4 PaohsBChP4i1cE2BHu6xMiNJR7mA9731EuT8P8TzcJL8ttXfSxeND+LN8nTMNhBnbK0e o44XbeZ9xTXhi3hToj74pwT6go+31cyo4faqdgwK9jyb3SbEvnFITAPa/YJXT8LMu7JR 3TFccQ70Q32xDrTUODXj6wRc9RAjCnJ5QjT6/1D9BtHA8RIkBL5iQ2kNevQFXh3QzSJt Bnhg== X-Gm-Message-State: ALoCoQnCKVGqIsoSCJi/1X7zHwt/s9oKbMnaIwA7JU4pEuVVg7+BSawWqXYUEP0oIDUpsOesBCmN MIME-Version: 1.0 X-Received: by 10.182.24.193 with SMTP id w1mr11075989obf.52.1448058732869; Fri, 20 Nov 2015 14:32:12 -0800 (PST) Received: by 10.60.11.166 with HTTP; Fri, 20 Nov 2015 14:32:12 -0800 (PST) Received: by 10.60.11.166 with HTTP; Fri, 20 Nov 2015 14:32:12 -0800 (PST) In-Reply-To: <564F8311.5010709@ik.nu> References: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> <564F8311.5010709@ik.nu> Date: Fri, 20 Nov 2015 22:32:12 +0000 Message-ID: From: Dave Cridland To: Ralph Meijer Content-Type: multipart/alternative; boundary=001a11c2ff94631b41052500720b Archived-At: Cc: Jabber/XMPP software development list , XSF Members , XMPP Standards , XMPP Working Group , XMPP Summit Subject: Re: [xmpp] Fwd: [jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 22:32:19 -0000 --001a11c2ff94631b41052500720b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The original went straight into my Google spam folder. Conspiracy theories welcome. On 20 Nov 2015 20:31, "Ralph Meijer" wrote: > Dear all, > > Daniel Pocock sent out the attached Call for Participation for the > FOSDEM 2016 Realtime Devroom, a devroom co-organised by the XSF and the > telephony crowd. Unfortunately, we haven't gotten any XMPP-related talk > proposals so far. I just noticed that the CfP never ended up in these > other mailing lists, so maybe we messed this up or they got dropped in > moderation. > > Please send in your proposals as soon as possible, by using the FOSDEM > Pentabarf system, so we have some more great talks to promote XMPP in > its many of its facets. > > XMPP Rocks! > > -- > Cheers, > > ralphm > > > ---------- Forwarded message ---------- > From: Daniel Pocock > To: JDev@jabber.org > Cc: > Date: Fri, 30 Oct 2015 21:13:06 +0100 (CET) > Subject: [jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers > neeeded > > FOSDEM is one of the world's premier meetings of free software developers= , > with over five thousand people attending each year. FOSDEM 2016 > takes place 30-31 January 2016 in Brussels, Belgium. http://fosdem.org > > This email contains information about: > - Real-Time communications dev-room and lounge, > - speaking opportunities, > - volunteering in the dev-room and lounge, > - related events around FOSDEM, including the XMPP summit, > - social events (including the Saturday night dinner), > - the Planet aggregation sites for RTC blogs > > Call for participation - Real Time Communications (RTC) > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D > > The Real-Time dev-room and Real-Time lounge is about all things involving > real-time communication, including: XMPP, SIP, WebRTC, telephony, > mobile VoIP, codecs, privacy and encryption. The dev-room is a successor > to the previous XMPP and telephony dev-rooms. We are looking for speaker= s > for the dev-room and volunteers and participants for the tables in the > Real-Time lounge. > > The dev-room is only on Saturday, 30 January 2016. The lounge will > be present for both days. > > To discuss the dev-room and lounge, please join the FSFE-sponsored > Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc > > Speaking opportunities > ---------------------- > > Note: if you used Pentabarf before, please use the same account/username > > Main track: the deadline for main track presentations is midnight > today, 30 October. Leading developers in the Real-Time Communications > field are encouraged to consider submitting a presentation to > the main track at https://fosdem.org/submit > > Real-Time Communications dev-room: deadline 27 November > Please also use the Pentabarf system to submit a talk proposal for the > dev-room. On the "General" tab, please look for the "Track" option and > choose "Real-Time devroom". https://penta.fosdem.org/submission/FOSDEM16= / > > Other dev-rooms: some speakers may find their topic is in the scope of mo= re > than one dev-room. It is permitted to apply to more than one dev-room bu= t > please be kind enough to tell us if you do this. You can find the full > list of dev-rooms at https://www.fosdem.org/2016/schedule/tracks/ > > Lightning talks: deadline 27 November > The lightning talks are an excellent opportunity to introduce > a wider audience to your project. Given that dev-rooms are > becoming increasingly busy, all speakers are encouraged to > consider applying for a lightning talk as well as a slot in the dev-room. > On the "General" tab, please look for the "Track" option and > choose "Lightning Talks". https://fosdem.org/submit > > First-time speaking? > -------------------- > > FOSDEM dev-rooms are a welcoming environment for people who have never > given a talk before. Please feel free to contact the dev-room > administrators > personally if you would like to ask any questions about it. > > Submission guidelines > --------------------- > > The Pentabarf system will ask for many of the essential details. Please > remember to re-use your account from previous years if you have one. > > In the "Submission notes", please tell us about: > - the purpose of your talk > - any other talk applications (dev-rooms, lightning talks, main track) > - availability constraints and special needs > > You can use HTML in your bio, abstract and description. > > If you maintain a blog, please consider providing us with the > URL of a feed with posts tagged for your RTC-related work. > > We will be looking for relevance to the conference and dev-room themes, > presentations aimed at developers of free and open source software about > RTC-related topics. > > Please feel free to suggest a duration between 20 minutes and 55 minutes > but note that the final decision on talk durations will be made by the > dev-room administrators. As the two previous dev-rooms have been > combined into one, we may decide to give shorter slots than in previous > years so that more speakers can participate. > > Please note FOSDEM aims to record and live-stream all talks. > The CC-BY license is used. > > For any questions, please join the FSFE-sponsored > Free RTC mailing list: https://lists.fsfe.org/mailman/listinfo/free-rtc > > Volunteers needed > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > To make the dev-room and lounge run successfully, we are looking for > volunteers: > > - FOSDEM provides video recording equipment and live streaming, > volunteers are needed to assist in this > - organizing one or more restaurant bookings (dependending upon number of > participants) for the evening of Saturday, 30 January > - participation in the Real-Time lounge > - helping attract sponsorship funds for the dev-room to pay for the > Saturday night dinner and any other expenses > - circulating this Call for Participation to other mailing lists > > FOSDEM is made possible by volunteers and if you have time to contribute, > please feel free to get involved through https://volunteers.fosdem.org/ > > Related events - XMPP and RTC summits > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > The XMPP Standards Foundation (XSF) has traditionally held a summit > in the days before FOSDEM. There is discussion about a similar > summit taking place on 28 and 29 January 2016 > http://wiki.xmpp.org/web/Summit_19 - please join the mailing > list for details: http://mail.jabber.org/mailman/listinfo/summit > > We are also considering a more general RTC or telephony summit, > potentially on 29 January. Please join the Free-RTC mailing list > and send an email if you would be interested in participating, > sponsoring or hosting such an event. > > Social events and dinners > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D > > The traditional FOSDEM beer night occurs on Friday, 29 January > > On Saturday night, there are usually dinners associated with > each of the dev-rooms. Most restaurants in Brussels are not so > large so these dinners have space constraints. Please subscribe > to the Free-RTC mailing list for further details about the > Saturday night dinner options and how you can register for a seat: > https://lists.fsfe.org/mailman/listinfo/free-rtc > > Spread the word and discuss > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D > > If you know of any mailing lists where this CfP would be relevant, please > forward this email. If this dev-room excites you, please blog or microblo= g > about it, especially if you are submitting a talk. > > If you regularly blog about RTC topics, please send details about your > blog to the planet site administrators: > > http://planet.jabber.org ralphm@ik.nu > > http://planet.sip5060.net daniel@pocock.pro > > http://planet.opentelecoms.org daniel@pocock.pro > > Please also link to the Planet sites from your own blog or web site. > > Contact > =3D=3D=3D=3D=3D=3D=3D > > For discussion and queries, please join the free-rtc mailing list: > https://lists.fsfe.org/mailman/listinfo/free-rtc > > The dev-room administration team: > > Daniel Pocock > Ralph Meijer > Sa=C3=BAl Ibarra Corretg=C3=A9 > Iain R. Learmonth > > > _______________________________________________ > JDev mailing list > Info: http://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: JDev-unsubscribe@jabber.org > _______________________________________________ > > _______________________________________________ > xmpp mailing list > xmpp@ietf.org > https://www.ietf.org/mailman/listinfo/xmpp > > --001a11c2ff94631b41052500720b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

The original went straight into my Google spam folder.

Conspiracy theories welcome.

On 20 Nov 2015 20:31, "Ralph Meijer" &= lt;ralphm@ik.nu> wrote:
Dear all,

Daniel Pocock sent out the attached Call for Participation for the
FOSDEM 2016 Realtime Devroom, a devroom co-organised by the XSF and the
telephony crowd. Unfortunately, we haven't gotten any XMPP-related talk=
proposals so far. I just noticed that the CfP never ended up in these
other mailing lists, so maybe we messed this up or they got dropped in
moderation.

Please send in your proposals as soon as possible, by using the FOSDEM
Pentabarf system, so we have some more great talks to promote XMPP in
its many of its facets.

XMPP Rocks!

--
Cheers,

ralphm


---------- Forwarded message ----------
From:=C2=A0Daniel Pocock= <daniel@pocock.pro>
To:= =C2=A0JDev@jabber.org
Cc:=C2=A0Date:=C2=A0Fri, 30 Oct 2015 21:13:06 +0100 (CET)
Subject:=C2=A0[jdev] = [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded

FOSDEM is one of the world's premier meetings of free software develope= rs,
with over five thousand people attending each year.=C2=A0 FOSDEM 2016
takes place 30-31 January 2016 in Brussels, Belgium.=C2=A0 http://fosdem.org
This email contains information about:
- Real-Time communications dev-room and lounge,
- speaking opportunities,
- volunteering in the dev-room and lounge,
- related events around FOSDEM, including the XMPP summit,
- social events (including the Saturday night dinner),
- the Planet aggregation sites for RTC blogs

Call for participation - Real Time Communications (RTC)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D

The Real-Time dev-room and Real-Time lounge is about all things involving real-time communication, including: XMPP, SIP, WebRTC, telephony,
mobile VoIP, codecs, privacy and encryption.=C2=A0 The dev-room is a succes= sor
to the previous XMPP and telephony dev-rooms.=C2=A0 We are looking for spea= kers
for the dev-room and volunteers and participants for the tables in the
Real-Time lounge.

The dev-room is only on Saturday, 30 January 2016.=C2=A0 The lounge will be present for both days.

To discuss the dev-room and lounge, please join the FSFE-sponsored
Free RTC mailing list: https://lists.fsfe.org/mailma= n/listinfo/free-rtc

Speaking opportunities
----------------------

Note: if you used Pentabarf before, please use the same account/username
Main track: the deadline for main track presentations is midnight
today, 30 October.=C2=A0 Leading developers in the Real-Time Communications=
field are encouraged to consider submitting a presentation to
the main track at https://fosdem.org/submit

Real-Time Communications dev-room: deadline 27 November
Please also use the Pentabarf system to submit a talk proposal for the
dev-room.=C2=A0 On the "General" tab, please look for the "T= rack" option and
choose "Real-Time devroom".=C2=A0 https://pen= ta.fosdem.org/submission/FOSDEM16/

Other dev-rooms: some speakers may find their topic is in the scope of more=
than one dev-room.=C2=A0 It is permitted to apply to more than one dev-room= but
please be kind enough to tell us if you do this.=C2=A0 You can find the ful= l
list of dev-rooms at https://www.fosdem.org/2016/schedul= e/tracks/

Lightning talks: deadline 27 November
The lightning talks are an excellent opportunity to introduce
a wider audience to your project.=C2=A0 Given that dev-rooms are
becoming increasingly busy, all speakers are encouraged to
consider applying for a lightning talk as well as a slot in the dev-room. On the "General" tab, please look for the "Track" optio= n and
choose "Lightning Talks".=C2=A0 https://fosdem.org/submit

First-time speaking?
--------------------

FOSDEM dev-rooms are a welcoming environment for people who have never
given a talk before.=C2=A0 Please feel free to contact the dev-room adminis= trators
personally if you would like to ask any questions about it.

Submission guidelines
---------------------

The Pentabarf system will ask for many of the essential details.=C2=A0 Plea= se
remember to re-use your account from previous years if you have one.

In the "Submission notes", please tell us about:
- the purpose of your talk
- any other talk applications (dev-rooms, lightning talks, main track)
- availability constraints and special needs

You can use HTML in your bio, abstract and description.

If you maintain a blog, please consider providing us with the
URL of a feed with posts tagged for your RTC-related work.

We will be looking for relevance to the conference and dev-room themes,
presentations aimed at developers of free and open source software about RTC-related topics.

Please feel free to suggest a duration between 20 minutes and 55 minutes but note that the final decision on talk durations will be made by the
dev-room administrators.=C2=A0 As the two previous dev-rooms have been
combined into one, we may decide to give shorter slots than in previous
years so that more speakers can participate.

Please note FOSDEM aims to record and live-stream all talks.
The CC-BY license is used.

For any questions, please join the FSFE-sponsored
Free RTC mailing list: https://lists.fsfe.org/mailma= n/listinfo/free-rtc

Volunteers needed
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

To make the dev-room and lounge run successfully, we are looking for
volunteers:

- FOSDEM provides video recording equipment and live streaming,
=C2=A0 volunteers are needed to assist in this
- organizing one or more restaurant bookings (dependending upon number of =C2=A0 participants) for the evening of Saturday, 30 January
- participation in the Real-Time lounge
- helping attract sponsorship funds for the dev-room to pay for the
=C2=A0 Saturday night dinner and any other expenses
- circulating this Call for Participation to other mailing lists

FOSDEM is made possible by volunteers and if you have time to contribute, please feel free to get involved through https://volunteers.fosdem.org= /

Related events - XMPP and RTC summits
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

The XMPP Standards Foundation (XSF) has traditionally held a summit
in the days before FOSDEM.=C2=A0 There is discussion about a similar
summit taking place on 28 and 29 January 2016
http://wiki.xmpp.org/web/Summit_19 - please join the mailing list for details: http://mail.jabber.org/mailman/listi= nfo/summit

We are also considering a more general RTC or telephony summit,
potentially on 29 January.=C2=A0 Please join the Free-RTC mailing list
and send an email if you would be interested in participating,
sponsoring or hosting such an event.

Social events and dinners
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

The traditional FOSDEM beer night occurs on Friday, 29 January

On Saturday night, there are usually dinners associated with
each of the dev-rooms.=C2=A0 Most restaurants in Brussels are not so
large so these dinners have space constraints.=C2=A0 Please subscribe
to the Free-RTC mailing list for further details about the
Saturday night dinner options and how you can register for a seat:
https://lists.fsfe.org/mailman/listinfo/free-rtc=

Spread the word and discuss
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D

If you know of any mailing lists where this CfP would be relevant, please forward this email. If this dev-room excites you, please blog or microblog<= br> about it, especially if you are submitting a talk.

If you regularly blog about RTC topics, please send details about your
blog to the planet site administrators:

=C2=A0 http://planet.jabber.org=C2=A0 =C2=A0 =C2=A0 =C2=A0 ralphm@ik.nu

=C2=A0 http://planet.sip5060.net=C2=A0 =C2=A0 =C2=A0 =C2=A0daniel@pocock.pro

=C2=A0 http://planet.opentelecoms.org=C2=A0 daniel@pocock.pro

Please also link to the Planet sites from your own blog or web site.

Contact
=3D=3D=3D=3D=3D=3D=3D

For discussion and queries, please join the free-rtc mailing list:
https://lists.fsfe.org/mailman/listinfo/free-rtc=

The dev-room administration team:

=C2=A0 Daniel Pocock <daniel@pocock= .pro>
=C2=A0 Ralph Meijer <ralphm@ik.nu>= ;
=C2=A0 Sa=C3=BAl Ibarra Corretg=C3=A9 <saul@ag-projects.com>
=C2=A0 Iain R. Learmonth <irl@debian.o= rg>


_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: JDev-unsubscrib= e@jabber.org
_______________________________________________

_______________________________________________
xmpp mailing list
xmpp@ietf.org
https://www.ietf.org/mailman/listinfo/xmpp

--001a11c2ff94631b41052500720b-- From nobody Fri Nov 20 21:47:10 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45A881B3821 for ; Fri, 20 Nov 2015 21:47:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.302 X-Spam-Level: X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0xiDOG-YWAgK for ; Fri, 20 Nov 2015 21:47:09 -0800 (PST) Received: from mail1.trendhosting.net (mail1.trendhosting.net [195.8.117.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01A221B381F for ; Fri, 20 Nov 2015 21:47:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mail1.trendhosting.net (Postfix) with ESMTP id B085E150C1; Sat, 21 Nov 2015 05:47:07 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1448084827; bh=dP2/pF1upOfhviE7FjQVmA7Zylh7kaBzZ9vwLIqIMcg=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=NhdcCdvEMasff1NW7bHSK61+Qvydb7as4qVvTyq4fo5vmWglEEvMKHuDWlpxvwkBw zgkvusfHbfSE8n7P1xfNwW6LM47BQ9+7Dw6Kr7shU6UqR3gvJpyazTHmvvzS5kI3y/ FEnRHCzfDEDifxc4oFTgabV2/ZWSeHvbQjA9A1+4= Received: from mail1.trendhosting.net ([127.0.0.1]) by localhost (thp003.trendhosting.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VcWIcAczzeyE; Sat, 21 Nov 2015 05:47:05 +0000 (GMT) Message-ID: <56500558.3030805@pocock.pro> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1448084825; bh=dP2/pF1upOfhviE7FjQVmA7Zylh7kaBzZ9vwLIqIMcg=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=uGdQtvhorgDgINGhnenxEQlPvLaw/s3+5VmlgCYzfwR4GQYz6ZF1rhGVbXGkSy/L3 w78xWvxEeaZB2OdhZIuyXuB9snG8vnv+ODDMQB7v111czn68lWfta/XaRXOZsKpQpO 6LHaZmUnsjBOPhfgcpyLIZUg9c250W/Ob01Sgu34= Date: Sat, 21 Nov 2015 06:47:04 +0100 From: Daniel Pocock User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: XMPP Summit , Ralph Meijer References: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> <564F8311.5010709@ik.nu> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Archived-At: Cc: XMPP Working Group , Jabber/XMPP software development list , XMPP Standards , XSF Members Subject: Re: [xmpp] [Summit] Fwd: [jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2015 05:47:10 -0000 On 20/11/15 23:32, Dave Cridland wrote: > The original went straight into my Google spam folder. > > Conspiracy theories welcome. > I don't use gmail myself. Could you contact the support team and ask why this message was marked as spam and let me know so I can be more careful writing messages like that in future? Could you look at the message headers to see if there is any clue there from the spam classifier? May not be an anti-XMPP conspiracy though, it is a known problem for a long time now that Google's spam filter is quite bad and they expect you to spend a little bit of time working for them every day training their spam filter: http://danielpocock.com/unpaid-work-training-googles-spam-filters Regards, Daniel From nobody Fri Nov 20 22:03:05 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C02AE1A1E0B for ; Fri, 20 Nov 2015 22:03:03 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GMcRHVSrSGCj for ; Fri, 20 Nov 2015 22:03:02 -0800 (PST) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF3C1A1DBC for ; Fri, 20 Nov 2015 22:03:01 -0800 (PST) Received: by wmdw130 with SMTP id w130so42084345wmd.0 for ; Fri, 20 Nov 2015 22:03:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ZnqWN0ro4tXI9cul55OZ1+s4oFOu4lrO4XGc0oJINPk=; b=rDia7PvqBfkNFHswRqJPt3BCk41Z/EGjIYOPR2pOfmfg/CeZvvKaIwj2QUr4uo9AaN Z8RsgiLW8QroYzg2YuwM+i+J4SZXlhRGDVJN/pvutV7pknzVy4FLfswHuEO0W98roOp1 7K1G4vInC614mEk4L660uXcCrBQ8wNaELVa3rfEa6ZfYq8ChfEWRMN/LHBEC07DxqAh7 LO/L9uBEY2e/MAmq64HVlVqcjSqvMqRFBnzFKgyCOZAkoIWP/fnB2/YFrCyZePs/uD// mCLJ31njT8kuBnx9uvVkwlWqOA0ATNphjK24f2mp60/QvWdBS2piBPwPV+iktdGE9rz3 IPZQ== X-Received: by 10.194.142.45 with SMTP id rt13mr18135116wjb.45.1448085780334; Fri, 20 Nov 2015 22:03:00 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.241.232 with HTTP; Fri, 20 Nov 2015 22:02:39 -0800 (PST) In-Reply-To: <56500558.3030805@pocock.pro> References: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> <564F8311.5010709@ik.nu> <56500558.3030805@pocock.pro> From: Arc Riley Date: Fri, 20 Nov 2015 22:02:39 -0800 Message-ID: To: Daniel Pocock Content-Type: multipart/alternative; boundary=089e0122927e8a908e052506be79 Archived-At: Cc: XMPP Standards , Jabber/XMPP software development list , XMPP Working Group , XSF Members , Ralph Meijer , XMPP Summit Subject: Re: [xmpp] [Summit] Fwd: [jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2015 06:03:03 -0000 --089e0122927e8a908e052506be79 Content-Type: text/plain; charset=UTF-8 I'm on email, it did not go to spam. On Fri, Nov 20, 2015 at 9:47 PM, Daniel Pocock wrote: > > > On 20/11/15 23:32, Dave Cridland wrote: > > The original went straight into my Google spam folder. > > > > Conspiracy theories welcome. > > > > > I don't use gmail myself. Could you contact the support team and ask > why this message was marked as spam and let me know so I can be more > careful writing messages like that in future? > > Could you look at the message headers to see if there is any clue there > from the spam classifier? > > May not be an anti-XMPP conspiracy though, it is a known problem for a > long time now that Google's spam filter is quite bad and they expect you > to spend a little bit of time working for them every day training their > spam filter: > http://danielpocock.com/unpaid-work-training-googles-spam-filters > > Regards, > > Daniel > > _______________________________________________ > xmpp mailing list > xmpp@ietf.org > https://www.ietf.org/mailman/listinfo/xmpp > --089e0122927e8a908e052506be79 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm on email, it did not go to spam.

On Fri, Nov 20, 2015 at 9:4= 7 PM, Daniel Pocock <daniel@pocock.pro> wrote:


On 20/11/15 23:32, Dave Cridland wrote:
> The original went straight into my Google spam folder.
>
> Conspiracy theories welcome.
>


I don't use gmail myself.=C2=A0 Could you contact the support te= am and ask
why this message was marked as spam and let me know so I can be more
careful writing messages like that in future?

Could you look at the message headers to see if there is any clue there
from the spam classifier?

May not be an anti-XMPP conspiracy though, it is a known problem for a
long time now that Google's spam filter is quite bad and they expect yo= u
to spend a little bit of time working for them every day training their
spam filter:
http://danielpocock.com/unpaid-work= -training-googles-spam-filters

Regards,

Daniel

_______________________________________________
xmpp mailing list
xmpp@ietf.org
https://www.ietf.org/mailman/listinfo/xmpp

--089e0122927e8a908e052506be79-- From nobody Fri Nov 20 23:38:59 2015 Return-Path: X-Original-To: xmpp@ietfa.amsl.com Delivered-To: xmpp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E481B4143 for ; Fri, 20 Nov 2015 23:38:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.701 X-Spam-Level: X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2U6-fmzjB0CP for ; Fri, 20 Nov 2015 23:38:56 -0800 (PST) Received: from mail1.trendhosting.net (mail1.trendhosting.net [195.8.117.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0BF41B40B9 for ; Fri, 20 Nov 2015 23:38:55 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mail1.trendhosting.net (Postfix) with ESMTP id BA8FF150AC; Sat, 21 Nov 2015 07:38:53 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1448091533; bh=5X89FrVjNYi/Ve5mer0Fn8nuthNy7NbcNb2JeVLD1BU=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=WRdNWYhsNZkBsiP3eggF54QNOzxEVtuk+c/POmDngvR4Pq7NC/Q54pibR4oSc3k6w 6OJ9e5R18950vXtPt++fUo2tQXU8z8Dw9vjapGmg6IQDwtLkpCpH7YmaIGlBN1dRMa q/TVcNn7crijt7MB5rwVsLkqVvFD2S0r/jLQGfF0= Received: from mail1.trendhosting.net ([127.0.0.1]) by localhost (thp003.trendhosting.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id lRIsroaT2OPm; Sat, 21 Nov 2015 07:38:50 +0000 (GMT) Message-ID: <56501F88.6090707@pocock.pro> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1448091530; bh=5X89FrVjNYi/Ve5mer0Fn8nuthNy7NbcNb2JeVLD1BU=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=a82bMloHKcFBdwuF+Z4FHri6gumrJx5EriILIEL1jajqcgT9Y2ofcvsWV7Bp4hQjN 9roUbC1rFAvQ9CmK83NHjwE73/r2vV6vJHqMQ9XiQdsYJq4XUDoRU6oPznainWFeTH /5loIZ7Vox8LSawjOcsGtSo1Ae5B7WXhXQHL+HPw= Date: Sat, 21 Nov 2015 08:38:48 +0100 From: Daniel Pocock User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0 MIME-Version: 1.0 To: Arc Riley References: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> <564F8311.5010709@ik.nu> <56500558.3030805@pocock.pro> In-Reply-To: Content-Type: multipart/alternative; boundary="------------020200090407040108090807" Archived-At: Cc: XMPP Standards , Jabber/XMPP software development list , XMPP Working Group , XSF Members , Ralph Meijer , XMPP Summit Subject: Re: [xmpp] [Summit] Fwd: [jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded X-BeenThere: xmpp@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: XMPP Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2015 07:38:58 -0000 This is a multi-part message in MIME format. --------------020200090407040108090807 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit On 21/11/15 07:02, Arc Riley wrote: > I'm on email, it did not go to spam. Can anybody else comment on whether they got it or not? Does anybody who did or did not receive it see any headers indicating how Google's spam filters are classifying the message? I'm hearing far too many reports of these problems these days. Somebody suggested it may be triggered by 4 of the letters in my surname, although I feel lucky not be in the same situation as these people: http://www.theguardian.com/technology/2015/nov/18/facebook-thinks-im-a-terrorist-woman-named-isis-has-account-disabled --------------020200090407040108090807 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
On 21/11/15 07:02, Arc Riley wrote:
I'm on email, it did not go to spam.

Can anybody else comment on whether they got it or not?

Does anybody who did or did not receive it see any headers indicating how Google's spam filters are classifying the message?

I'm hearing far too many reports of these problems these days.  Somebody suggested it may be triggered by 4 of the letters in my surname, although I feel lucky not be in the same situation as these people:

http://www.theguardian.com/technology/2015/nov/18/facebook-thinks-im-a-terrorist-woman-named-isis-has-account-disabled


--------------020200090407040108090807--