IETF Logo Mail Archive

Re: [jose] Binary encoding for JSON

Richard Barnes <rlb@ipv.sx> Wed, 12 June 2013 20:09 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E21B11E80EA for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.329
X-Spam-Level:
X-Spam-Status: No, score=-0.329 tagged_above=-999 required=5 tests=[AWL=0.096, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Gz6pq+pnzro for <jose@ietfa.amsl.com>; Wed, 12 Jun 2013 13:09:03 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 1DFC311E80F5 for <jose@ietf.org>; Wed, 12 Jun 2013 13:09:01 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so5664058oah.10 for <jose@ietf.org>; Wed, 12 Jun 2013 13:09:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=s2Ts0xUwb5WxVqGdiA+aTij1Z1WC9z5DiVaOAkA2Gdg=; b=N/d1vBXUwxC3P4N1ySY5LbiwdFMtWYDAa4ZhzXFVX0G58cpDmWi7xjI2RlqR9kQ6it N1f0d0cge7KVhXkSlakdSu3DhmUQflGuDdDDlkxcroQXLW/SG3pvqHKHHW0zIwtmg+RX 0FnD0qu3RPpxZQHaopRak2+bWXtUnMz7bSH3k51Wq/I0vliDHYnYh7Z6ydm2ff/eCMg0 LOxI64kE2iGri0DWMd3chx1N/WcCjojS5e33AK3P+iLaNEPAmPFoKEoXk4X++6dd3dk7 Q3+3PbLkbwfFx+6fZOXWWofpXaNGqfq81WFw1v9W1w203gcB/3zPPAZZOcdtM3ujLPXS vxuA==
MIME-Version: 1.0
X-Received: by 10.60.134.236 with SMTP id pn12mr16940046oeb.4.1371067740458; Wed, 12 Jun 2013 13:09:00 -0700 (PDT)
Received: by 10.60.84.8 with HTTP; Wed, 12 Jun 2013 13:09:00 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <CAMm+LwgR-5uxvXsc_d4nsJJqey5qDyK==Hetznujw8Nxhargfw@mail.gmail.com>
References: <CAMm+LwjBXHK-3Lsq1o=_Hu95xyqXZTKbg0U_piiANtAWFaOF5w@mail.gmail.com> <51B74E44.7040201@stpeter.im> <079d01ce66c7$1ebd98b0$5c38ca10$@augustcellars.com> <CAMm+LwgR-5uxvXsc_d4nsJJqey5qDyK==Hetznujw8Nxhargfw@mail.gmail.com>
Date: Wed, 12 Jun 2013 16:09:00 -0400
Message-ID: <CAL02cgTnn16bPpG_i8EtSEym6bV+snvkSwpgrXYyapoGKdMvKQ@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary="047d7b471f6aa2372704defa9594"
X-Gm-Message-State: ALoCoQkAHFXYc/rC5dDV4ikME4jJqFD9s3MTNtGD8ZK7Ruvqr7iHZz5/Zx/plRCrP+AFMrkrLc1z
Cc: Jim Schaad <ietf@augustcellars.com>, Peter Saint-Andre <stpeter@stpeter.im>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Binary encoding for JSON
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jose>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jun 2013 20:09:07 -0000

Conversely, there's some discussion right now about how to make JOSE
suitable for a binary-capable encoding:
<http://www.ietf.org/mail-archive/web/jose/current/msg02493.html>


On Wed, Jun 12, 2013 at 3:52 PM, Phillip Hallam-Baker <hallam@gmail.com>wrote:

> On Tue, Jun 11, 2013 at 1:14 PM, Jim Schaad <ietf@augustcellars.com>wrote:
>
>> <chair>
>>
>> At this point only the fact that binary encodings exist is in scope for
>> the
>> WG.
>>
>> Any concreteness would require a charter modification.
>>
>
> Any concrete would needs be added in apps area in any case.
>
> The reason for raising it here was simply to make people aware that there
> is a binary option and to encourage anyone who might be interested in
> making sure that it is suitable for use with JOSE to take a look to check
> if anything was left out.
>
> I would like to be able to use JOSE as an alternative to CMS at some
> point. But not with the Base64 penalty.
>
> --
> Website: http://hallambaker.com/
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>
>

v2.23.0 | Report a Bug | By Email