IETF Logo Mail Archive

Re: [xmpp] message size

Alexander Holler <holler@ahsoftware.de> Sat, 08 March 2014 10:46 UTC

Return-Path: <holler@ahsoftware.de>
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 9124D1A016A for <xmpp@ietfa.amsl.com>; Sat, 8 Mar 2014 02:46:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.208
X-Spam-Level:
X-Spam-Status: No, score=0.208 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, HOST_MISMATCH_NET=0.311, 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 0Ue_cx0jU5dl for <xmpp@ietfa.amsl.com>; Sat, 8 Mar 2014 02:46:31 -0800 (PST)
Received: from mail.ahsoftware.de (h1446028.stratoserver.net [85.214.92.142]) by ietfa.amsl.com (Postfix) with ESMTP id C31991A0166 for <xmpp@ietf.org>; Sat, 8 Mar 2014 02:46:30 -0800 (PST)
Received: by mail.ahsoftware.de (Postfix, from userid 65534) id 316D4423C297; Sat, 8 Mar 2014 11:46:25 +0100 (CET)
Received: from eiche.ahsoftware (p57B20126.dip0.t-ipconnect.de [87.178.1.38]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ahsoftware.de (Postfix) with ESMTPSA id 6873A423C297 for <xmpp@ietf.org>; Sat, 8 Mar 2014 11:46:22 +0100 (CET)
Received: by eiche.ahsoftware (Postfix, from userid 65534) id 793237FAAE; Sat, 8 Mar 2014 11:46:21 +0100 (CET)
Received: from [IPv6:feeb::c685:8ff:fe12:175d] (unknown [IPv6:feeb::c685:8ff:fe12:175d]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by eiche.ahsoftware (Postfix) with ESMTPS id C75AB7F82C; Sat, 8 Mar 2014 10:46:18 +0000 (UTC)
Message-ID: <531AF4E8.1040207@ahsoftware.de>
Date: Sat, 08 Mar 2014 11:46:00 +0100
From: Alexander Holler <holler@ahsoftware.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: kevin@kismith.co.uk, Ashley Ward <ashley.ward@surevine.com>
References: <531883F5.7000800@stpeter.im> <CAKHUCzz7QqnJirHHwrGJHSD1U_m_uAZGV4GcQaC-rteceug-sA@mail.gmail.com> <C16C702C-50EC-41A2-9559-B7576129A70B@surevine.com> <CAOb_FnywkNkyjwc3c4+AJb1xAXTpjD8dPj1gex_K9GzGKiJvAg@mail.gmail.com> <26D173CC-25CE-45AF-8F5A-27AF576558A0@surevine.com> <CAOb_FnznTTEXO8jWKoHXSNJRDSYsLH_6YgeOTs4-RW-=w2NORw@mail.gmail.com>
In-Reply-To: <CAOb_FnznTTEXO8jWKoHXSNJRDSYsLH_6YgeOTs4-RW-=w2NORw@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/xmpp/1AahrwTyIlwV8r6btub1gGEGBl0
Cc: XMPP Working Group <xmpp@ietf.org>
Subject: Re: [xmpp] message size
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Mar 2014 10:46:32 -0000

Am 06.03.2014 15:49, schrieb Kevin Smith:
> On Thu, Mar 6, 2014 at 2:44 PM, Ashley Ward <ashley.ward@surevine.com> wrote:
>> On 6 Mar 2014, at 14:40, Kevin Smith <kevin@kismith.co.uk> wrote:
>>> On Thu, Mar 6, 2014 at 2:35 PM, Ashley Ward <ashley.ward@surevine.com> wrote:
>>>> On 6 Mar 2014, at 14:28, Dave Cridland <dave@cridland.net> wrote:
>>>>
>>>>> You're saying to include, pre-encrypt, something like <spacer:junk xmlns:spacer='urn:...'>123465</spacer> in the plaintext order to defeat message size analysis of the ciphertext?
>>>>
>>>> It's XML - you could always just use <!-- --> comments or whitespace.
>>>
>>> Comments are slightly problematic, on account of being illegal.
>>
>> True - I often forget that XMPP isn't entirely XML compliant!
> 
> The stream isn't a real XML document (stream restarts break this) but
> not allowing comments doesn't stop it being XML, just a subset.

And just using whitespace is the most elegant solution. No necessary
changes and no obvious problems. So instead of

<message>foobar</message>

using

<message >foobar</message>

or e.g.

<message    >foobar</message      >

or something similiar is imho the most preferable way to add unused
plaintext.

Regards,

Alexander Holler

v2.23.0 | Report a Bug | By Email