IETF Logo Mail Archive

Re: [xmpp] Consensus Call on Adoption of POSH

Tobias Markmann <tmarkmann@googlemail.com> Thu, 30 January 2014 09:13 UTC

Return-Path: <tmarkmann@googlemail.com>
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 23E3C1A0417 for <xmpp@ietfa.amsl.com>; Thu, 30 Jan 2014 01:13:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level:
X-Spam-Status: No, score=-1.377 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, FREEMAIL_FROM=0.001, 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 37NXJYJzsPi3 for <xmpp@ietfa.amsl.com>; Thu, 30 Jan 2014 01:13:43 -0800 (PST)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) by ietfa.amsl.com (Postfix) with ESMTP id DC5011A03E9 for <xmpp@ietf.org>; Thu, 30 Jan 2014 01:13:42 -0800 (PST)
Received: by mail-yk0-f172.google.com with SMTP id 200so14383799ykr.3 for <xmpp@ietf.org>; Thu, 30 Jan 2014 01:13:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=IL5dS8tDgB9u+XzfFAYmBMV2McuyzrwdV8jXs36hGxk=; b=VFMo07CUI1GRvwToSRm9d6QUo6v+yROxkEPorDq7FPmxsqaMdHM6z+M5m2SE0uh5wf EQyDLyDAFFCLa3X1oJGX/OK9A0sNMuCtNX5/td2kDFpTsrvVezCCgKVoXSV8DBVEwpfC atd/IogzxrwrhBSRbC0Cqs+LxyKmRPm+xoktjDD+Ds+Re0oYfVP6e38BMyeow1Ykr+XG 18/wRG5yHTAjRrQp+zRLTYU0tjJq/uHo6cR2W/QKJyfaEPNDmcWUEACIFNtGIdVOrasO oCPoHjbd3FDCxQXOUrlQE6coG0vIH4CluZ2UTdWJSkAHDwiatyWZuy93UVUlPOVpQJ5d kwUw==
X-Received: by 10.236.151.41 with SMTP id a29mr12409585yhk.39.1391073219649; Thu, 30 Jan 2014 01:13:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.170.123.16 with HTTP; Thu, 30 Jan 2014 01:13:18 -0800 (PST)
In-Reply-To: <52EA1171.9010604@ahsoftware.de>
References: <3E197582-9715-4FE9-AA4A-322FDC18F301@nostrum.com> <52EA1171.9010604@ahsoftware.de>
From: Tobias Markmann <tmarkmann@googlemail.com>
Date: Thu, 30 Jan 2014 10:13:18 +0100
Message-ID: <CAJ9A0VsVorYJu7sW_uevpakbZ0UeGQ0A+3NyystRB5=NJgmaLw@mail.gmail.com>
To: Alexander Holler <holler@ahsoftware.de>
Content-Type: multipart/alternative; boundary="20cf303a30f71d249104f12c7936"
Cc: Ben Campbell <ben@nostrum.com>, XMPP Group <xmpp@ietf.org>
Subject: Re: [xmpp] Consensus Call on Adoption of POSH
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: Thu, 30 Jan 2014 09:13:44 -0000

On Thu, Jan 30, 2014 at 9:46 AM, Alexander Holler <holler@ahsoftware.de>wrote:

> Why does it use JSON and not XML? This makes it necessary to use another
> parser besides the XML-parser already available in http- and xmpp-clients
> and servers.
>
> And if uses JSON, please make sure to define how comments will have to
> look. Last time I looked at the JSON spec, it didn't know comments,
> something I have no comment for. ;)
>

It uses JSON because it uses the JSON Web Key[1] format. POSH was
generalized to work for more than just the XMPP protocol, which, I suppose,
is the reason for it not wanting to depend on XML parsers.

The JSON[2] spec referenced by JWK doesn't mention comments at all. I guess
the JSON you'll use in JWK simply can't include any comments.

Cheers,
Tobias

[1] http://tools.ietf.org/html/draft-ietf-jose-json-web-key-20
[2] http://tools.ietf.org/html/draft-ietf-json-rfc4627bis-10

v2.23.0 | Report a Bug | By Email