Re: [jose] HTTP content type of JWS/JWE compact serializations
Sergey Beryozkin <sberyozkin@gmail.com> Wed, 10 September 2014 13:15 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 749251A700A for <jose@ietfa.amsl.com>; Wed, 10 Sep 2014 06:15:17 -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 GTRhvJDrK3Rx for <jose@ietfa.amsl.com>; Wed, 10 Sep 2014 06:15:12 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B0E71A008C for <jose@ietf.org>; Wed, 10 Sep 2014 06:14:41 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id bs8so398975wib.8 for <jose@ietf.org>; Wed, 10 Sep 2014 06:14:39 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=WswVbIThTWzr2rMs5qsLNBRPi1X+jLMvNcryAliCx4w=; b=K5QRayT6TaOwQoBq2G/SbMZzeSuJquR1A7y0J2mcq6Cg7nb8oFvraCvQs6Ni/307md 0gOkuRxuyyVevhD+/BXEpPkzbDOKEivdMQAe2h9PAVuXXgAlHjkX+zAQP79HTs/oWoRZ CrTzb0b/3eo0WFWcIxY/0TwkkrenIMJhLlvF8xGnT6T7B0w+puDTjQ5GjB2ODGaWIJKo X5EdE/MIeBOUboVr0aFca1NuwUxQrH+fcdTMlzM4i4w7V5Bik0YgNJHzbWLj8GU/J0B2 PL1kXzstVdaglXjxknxXa9kqiQVBiGJRqCPXz1doviGcv8XQJuvFmWFirqYFu7ZHNm6K fbDw==
X-Received: by 10.194.57.237 with SMTP id l13mr3691821wjq.102.1410354879908; Wed, 10 Sep 2014 06:14:39 -0700 (PDT)
Received: from [192.168.2.7] ([109.255.231.6]) by mx.google.com with ESMTPSA id u8sm2407537wia.24.2014.09.10.06.14.38 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Sep 2014 06:14:39 -0700 (PDT)
Message-ID: <54104EBC.8040803@gmail.com>
Date: Wed, 10 Sep 2014 14:14:36 +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: Brian Campbell <bcampbell@pingidentity.com>
References: <COL401-EAS1838D8ED8A7323D3422439EDFD80@phx.gbl> <4E1F6AAD24975D4BA5B16804296739439AE76076@TK5EX14MBXC294.redmond.corp.microsoft.com> <541037F8.6070408@gmail.com> <CA+k3eCRTEpzgNCgEkXZqjqE+vVdmca2Me9qk_O7W3ByBU+JoBg@mail.gmail.com>
In-Reply-To: <CA+k3eCRTEpzgNCgEkXZqjqE+vVdmca2Me9qk_O7W3ByBU+JoBg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/idbLj-jgIDKPvEq9IqZ5xHgnE5k
Cc: "jose@ietf.org" <jose@ietf.org>
Subject: Re: [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 13:15:17 -0000
Hi Brian, On 10/09/14 13:05, Brian Campbell wrote: > I believe it'd be application/jose per > https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-31#section-9.2.1 > and > https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-31#section-4.1.9 > and one could further distinguish between JWS/JWE using the alg header > or the number of periods in the compact serialization. > Thanks, I missed it, sorry for the noise Having the hints (JWE vs JWS) might be handy too, but the above is sufficient, Thanks, Sergey > > > On Wed, Sep 10, 2014 at 5:37 AM, Sergey Beryozkin <sberyozkin@gmail.com > <mailto:sberyozkin@gmail.com>> wrote: > > 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 > > _________________________________________________ > jose mailing list > jose@ietf.org <mailto:jose@ietf.org> > https://www.ietf.org/mailman/__listinfo/jose > <https://www.ietf.org/mailman/listinfo/jose> > >
- Re: [jose] Secdir review of draft-ietf-jose-json-… Mike Jones
- [jose] HTTP content type of JWS/JWE compact seria… Sergey Beryozkin
- Re: [jose] HTTP content type of JWS/JWE compact s… Brian Campbell
- Re: [jose] HTTP content type of JWS/JWE compact s… Sergey Beryozkin
- [jose] JWK 'use' property Sergey Beryozkin
- Re: [jose] JWK 'use' property Sergey Beryozkin
- Re: [jose] Secdir review of draft-ietf-jose-json-… Mike Jones