[jose] HTTP content type of JWS/JWE compact serializations

Sergey Beryozkin <sberyozkin@gmail.com> Wed, 10 September 2014 11:37 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 496C51A6F67 for <jose@ietfa.amsl.com>; Wed, 10 Sep 2014 04:37:33 -0700 (PDT)
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 5KYauSVnsowt for <jose@ietfa.amsl.com>; Wed, 10 Sep 2014 04:37:32 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 139E91A6F6F for <jose@ietf.org>; Wed, 10 Sep 2014 04:37:31 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id hi2so6091164wib.4 for <jose@ietf.org>; Wed, 10 Sep 2014 04:37:30 -0700 (PDT)
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=089znFVKlFzKKLdAs0w+j81YyvmmFiRsBlVuzHJXZ70=; b=1BoKaG46UcJvVa0645slws9igJAOIzCzmtSIObp9kCZ7YP+NkMvx5Wh66uTJ4FvTjt WQ4TOHafuIm/LdQkOZ+J17nzzFkSYc/5ymMV0LdVjUCJtP/7QOkzv1hVALXaMluw2+ep MnV6aOAlOzMnx30s4Q9ZFEg+ITC4i+XnWqMSkDfppTo9164G7YlLj+yr0yN/cutUCEig zF+uzY9U3tjUaR3TGkBhl08MCWD05XI7qv4aIYZkkpIB1ixufmbd2G1nz1exF5BrgBUv 3D029Y1nGEY/5sBsofckuzXD6Ka2LgNrFjDXggRlhztAs3cG20pP658lkeiDguJxVBjG hr6w==
X-Received: by 10.180.76.37 with SMTP id h5mr4383367wiw.71.1410349050485; Wed, 10 Sep 2014 04:37:30 -0700 (PDT)
Received: from [192.168.2.7] ([109.255.231.6]) by mx.google.com with ESMTPSA id o3sm2114240wiy.18.2014.09.10.04.37.29 for <jose@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Sep 2014 04:37:29 -0700 (PDT)
Message-ID: <541037F8.6070408@gmail.com>
Date: Wed, 10 Sep 2014 12:37:28 +0100
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: jose@ietf.org
References: <COL401-EAS1838D8ED8A7323D3422439EDFD80@phx.gbl> <4E1F6AAD24975D4BA5B16804296739439AE76076@TK5EX14MBXC294.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739439AE76076@TK5EX14MBXC294.redmond.corp.microsoft.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/oXWJfWzCBn8MoCSCmdZLTqkglMY
Subject: [jose] HTTP content type of JWS/JWE compact serializations
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: Wed, 10 Sep 2014 11:37:33 -0000

Hi All,

What would be the right HTTP Content-Type value to identify a given 
compact JWE or JWS serialization payload transmitted as an HTTP message 
payload (as opposed to as a header or query value).
I see both JWE and JWS compact serializations can use a 'cty' header 
property to identify the encrypted or signed content but it is not clear 
how the actual JWE/JWS compact serializations are identified.

Something like

application/jose+jws;format=compact
application/jose+jwe;format=compact

with a format parameter being optional,

or somehow else ?

Sorry if I missed something,

Thanks, Sergey