Re: [jose] JOSE Hash-algorithm Identifiers?

Mike Jones <Michael.Jones@microsoft.com> Fri, 04 March 2016 19:14 UTC

Return-Path: <Michael.Jones@microsoft.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 CD9331A882F for <jose@ietfa.amsl.com>; Fri, 4 Mar 2016 11:14:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_HELO_PASS=-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 BheGjGNboeGv for <jose@ietfa.amsl.com>; Fri, 4 Mar 2016 11:14:27 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0744.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:744]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4295E1A87F0 for <jose@ietf.org>; Fri, 4 Mar 2016 11:14:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=vhL4L26csDob1fiW6kbqL/bju00A2CclVnjb7lJe/Xg=; b=WtxhYZ0bIB/6gSu0GpPbLiYNWUjjuDI8RMymYt0TsTKDsHUGsoNNI4AgdOtNQ5SIQJE4QHBIL2FSchjacrSNtjrNnDtTmqZON1UplQxnOH7XrhHEEHHpskxdsFhhYFYxnbzlpdHlv6qTOXOo4XfoQ0pZQilHRoqp56kxQRJfbe0=
Received: from SN1PR0301MB1645.namprd03.prod.outlook.com (10.162.130.139) by SN1PR0301MB1645.namprd03.prod.outlook.com (10.162.130.139) with Microsoft SMTP Server (TLS) id 15.1.427.16; Fri, 4 Mar 2016 19:14:06 +0000
Received: from SN1PR0301MB1645.namprd03.prod.outlook.com ([10.162.130.139]) by SN1PR0301MB1645.namprd03.prod.outlook.com ([10.162.130.139]) with mapi id 15.01.0427.019; Fri, 4 Mar 2016 19:14:06 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>, "jose@ietf.org" <jose@ietf.org>
Thread-Topic: [jose] JOSE Hash-algorithm Identifiers?
Thread-Index: AQHRMlD6idKZbMBG0keCGTD3FwGAzZ9J8C+AgAAj0ICAABOagIAAB9Dk
Date: Fri, 04 Mar 2016 19:14:06 +0000
Message-ID: <SN1PR0301MB16459F0C2A59B782ABBA2E20F5BE0@SN1PR0301MB1645.namprd03.prod.outlook.com>
References: <5667D450.7090503@gmail.com> <56D9A975.2050107@gmail.com> <SN1PR0301MB164584E7697015DC87FC2197F5BE0@SN1PR0301MB1645.namprd03.prod.outlook.com>, <56D9D7F1.9070107@gmail.com>
In-Reply-To: <56D9D7F1.9070107@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [167.220.25.95]
x-ms-office365-filtering-correlation-id: 77e7c083-65df-4782-d17f-08d344612831
x-microsoft-exchange-diagnostics: 1; SN1PR0301MB1645; 5:q3adzZNvM/7+u0xxfzv0TC4ePyyD8Yo7C0yHpbAHCIBRfCmQqQrdERJzmlHcCzMenO8VVeYTRwk281h7/wvS9a2ZG2oC7ve0qQz5ujc+uw52T1R9G327YGp7IN3wUlyo9T/6QmqJHYQrrGfqEe11iw==; 24:Tn6MeK8Q0EetRQrPrMXbRQjZgBufo4MKtHRM8j/M43G5xgB6da2Vcc0mUwyIk0cdM3tLEaEdZhaRk53AkHsd3/F3l/M2wbgk/T1XU1Lb3P0=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:SN1PR0301MB1645;
x-microsoft-antispam-prvs: <SN1PR0301MB164595CBD5638B47C0EFB8D0F5BE0@SN1PR0301MB1645.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(61426038)(61427038); SRVR:SN1PR0301MB1645; BCL:0; PCL:0; RULEID:; SRVR:SN1PR0301MB1645;
x-forefront-prvs: 0871917CDA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(377454003)(377424004)(13464003)(24454002)(106116001)(87936001)(81166005)(92566002)(19617315012)(93886004)(8990500004)(5002640100001)(33656002)(19625215002)(5003600100002)(16236675004)(19580395003)(575784001)(86362001)(2501003)(66066001)(76576001)(74316001)(76176999)(54356999)(19580405001)(50986999)(5004730100002)(5008740100001)(5005710100001)(1220700001)(1096002)(586003)(3660700001)(77096005)(11100500001)(40100003)(102836003)(6116002)(10090500001)(3846002)(2900100001)(3900700001)(2950100001)(10290500002)(122556002)(107886002)(2906002)(189998001)(3280700002)(15975445007)(10400500002)(5001770100001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR0301MB1645; H:SN1PR0301MB1645.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR0301MB16459F0C2A59B782ABBA2E20F5BE0SN1PR0301MB1645_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2016 19:14:06.4366 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0301MB1645
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/rdCQ_gmgKrFwSAKsKy57NL59ms8>
Subject: Re: [jose] JOSE Hash-algorithm Identifiers?
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 04 Mar 2016 19:14:33 -0000

For
________________________________
From: Anders Rundgren<mailto:anders.rundgren.net@gmail.com>
Sent: ‎3/‎4/‎2016 10:46 AM
To: Mike Jones<mailto:Michael.Jones@microsoft.com>; jose@ietf.org<mailto:jose@ietf.org>
Subject: Re: [jose] JOSE Hash-algorithm Identifiers?

On 2016-03-04 18:36, Mike Jones wrote:
> The PKCE RFC [RFC 7636] also uses "S256".

Since this points to a rather specific application, I'm not sure if this speaks for or against using S256 for indicating SHA256...

Anders

>
> -----Original Message-----
> From: jose [mailto:jose-bounces@ietf.org] On Behalf Of Anders Rundgren
> Sent: Friday, March 4, 2016 7:28 AM
> To: jose@ietf.org
> Subject: Re: [jose] JOSE Hash-algorithm Identifiers?
>
> No takers on this one?
>
> On 2015-12-09 08:12, Anders Rundgren wrote:
>> The following extract from a recent ACME posting indicates that I'm not the only one who see use-cases for such:
>>
>> It's not a bad idea to specify the agreement-integrity as a dictionary
>> instead so in that future case, there's not problem of checksum
>> negotiation:
>> "agreement-integrity": {"sha512":
>> "3Ys8QL9di54ggXIGBAS2RHr_W6cMurZPizhZihkQjwl3VG2dpXZYmsYZ0B7LG-tWlVE9-
>> Hwp9hL3Mosvbr6lCA"}
>>
>> In my work I used the names S128, S256, and S512.
>>
>> Anders
>>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>