[jose] JWT JSON representation

Sergey Beryozkin <sberyozkin@gmail.com> Mon, 10 November 2014 18:29 UTC

Return-Path: <sberyozkin@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F76C1A82E2 for <jose@ietfa.amsl.com>; Mon, 10 Nov 2014 10:29:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 AUL_4zso6Zsu for <jose@ietfa.amsl.com>; Mon, 10 Nov 2014 10:29:12 -0800 (PST)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5001F1A9150 for <jose@ietf.org>; Mon, 10 Nov 2014 10:26:53 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id d1so11339097wiv.1 for <jose@ietf.org>; Mon, 10 Nov 2014 10:26:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=s1O9NFvv4Jm6s0bBntOMnyjQEImONpnrI6lAlPFVdUI=; b=vrBOaSwnYhKb3q923wHGdq6uvcYKG+F9uU604BgOzBH29rVi8b9mkozPoizfq1xA9y ONJmhxRaM/WHX8dnPUbQNVVI2XEsgaWGDw+1EeIrxsnmy4/z9esmMic3tE0xC/abGh6T twTuoTVCwtnYqsjxS5iSQKUER++Qy9fAWybzaaTxPwvYwvybUvpwg/8FOrJ/CZBFrNEW cJsXR9G593i0qfLvYMeO6+A5xfoik7ffDYnMjuXM6FlAVbsawIB3xniYOwIJIgpr/GQd c93hv70jw8bjUfjLNkqOG6pG4HcUmgF3Q5WAySh5iHg5Eblt5BzmlyDJQUm56CTbq45C zJsg==
X-Received: by 10.194.62.226 with SMTP id b2mr44413366wjs.46.1415644009524; Mon, 10 Nov 2014 10:26:49 -0800 (PST)
Received: from [192.168.2.7] ([109.255.82.67]) by mx.google.com with ESMTPSA id s2sm14385966wia.3.2014.11.10.10.26.47 for <jose@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Nov 2014 10:26:47 -0800 (PST)
Message-ID: <54610366.6010400@gmail.com>
Date: Mon, 10 Nov 2014 18:26:46 +0000
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: jose@ietf.org
References: <5458E645.9020904@mit.edu> <CAL02cgTVHkGmB2+L90EaqpBT26+FqsNsvkvsV0Tig45tDJLjaw@mail.gmail.com> <5458E955.3090700@mit.edu> <CAL02cgSf_MeLys1D+bJcSsfPz9e5TLt5wT4G9szhD-=2OVFAnA@mail.gmail.com>
In-Reply-To: <CAL02cgSf_MeLys1D+bJcSsfPz9e5TLt5wT4G9szhD-=2OVFAnA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/8_Va9-0RI16kyqA2eEXUAWjUm3U
Subject: [jose] JWT JSON representation
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 10 Nov 2014 18:29:13 -0000

Hi All,

Would it make sense to have a JWT spec talk about its JSON 
representation, example:
{
    "headers": {...}
    "claims": {...}
}

IMHO it might be interesting in cases where JWT is an access token 
passed over the secure channel or simply used as a standard data/token 
container

Sergey