Re: [jose] Alissa Cooper's No Objection on draft-ietf-jose-json-web-signature-33: (with COMMENT)
Mike Jones <Michael.Jones@microsoft.com> Mon, 29 September 2014 22:57 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 648E31ACD71; Mon, 29 Sep 2014 15:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 oVYvjmpwMG4a; Mon, 29 Sep 2014 15:57:22 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0144.outbound.protection.outlook.com [65.55.169.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 673C51ACD69; Mon, 29 Sep 2014 15:57:22 -0700 (PDT)
Received: from DM2PR0301MB1214.namprd03.prod.outlook.com (25.160.219.155) by DM2PR0301MB1184.namprd03.prod.outlook.com (25.160.217.146) with Microsoft SMTP Server (TLS) id 15.0.1039.15; Mon, 29 Sep 2014 22:57:40 +0000
Received: from BN3PR0301CA0082.namprd03.prod.outlook.com (25.160.152.178) by DM2PR0301MB1214.namprd03.prod.outlook.com (25.160.219.155) with Microsoft SMTP Server (TLS) id 15.0.1039.15; Mon, 29 Sep 2014 22:57:21 +0000
Received: from BN1BFFO11FD009.protection.gbl (2a01:111:f400:7c10::1:108) by BN3PR0301CA0082.outlook.office365.com (2a01:111:e400:401e::50) with Microsoft SMTP Server (TLS) id 15.0.1039.15 via Frontend Transport; Mon, 29 Sep 2014 22:57:19 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1BFFO11FD009.mail.protection.outlook.com (10.58.144.72) with Microsoft SMTP Server (TLS) id 15.0.1029.15 via Frontend Transport; Mon, 29 Sep 2014 22:57:18 +0000
Received: from TK5EX14MBXC288.redmond.corp.microsoft.com ([169.254.3.218]) by TK5EX14HUBC106.redmond.corp.microsoft.com ([157.54.80.61]) with mapi id 14.03.0195.002; Mon, 29 Sep 2014 22:57:03 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
Thread-Topic: Alissa Cooper's No Objection on draft-ietf-jose-json-web-signature-33: (with COMMENT)
Thread-Index: AQHP24yKL/DMh4NBHkOI6gY85ytvmpwYuWjg
Date: Mon, 29 Sep 2014 22:57:02 +0000
Message-ID: <4E1F6AAD24975D4BA5B16804296739439BAA169B@TK5EX14MBXC288.redmond.corp.microsoft.com>
References: <20140929022406.23790.44693.idtracker@ietfa.amsl.com>
In-Reply-To: <20140929022406.23790.44693.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.32]
Content-Type: multipart/alternative; boundary="_000_4E1F6AAD24975D4BA5B16804296739439BAA169BTK5EX14MBXC288r_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10019020)(438002)(13464003)(199003)(52044002)(377454003)(189002)(54356999)(97736003)(99396003)(50986999)(76176999)(6806004)(15975445006)(87936001)(68736004)(55846006)(2656002)(19580395003)(19580405001)(44976005)(77096002)(512874002)(84326002)(19625215002)(95666004)(64706001)(76482002)(21056001)(86362001)(230783001)(66066001)(10300001)(16236675004)(120916001)(92726001)(69596002)(80022003)(106116001)(31966008)(81156004)(106466001)(4396001)(107046002)(15202345003)(71186001)(20776003)(19300405004)(19617315012)(92566001)(104016003)(85852003)(86612001)(46102003)(84676001)(33656002)(26826002)(85306004); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR0301MB1214; H:mail.microsoft.com; FPR:; MLV:ovrnspm; PTR:InfoDomainNonexistent; A:1; MX:1; LANG:en;
X-Microsoft-Antispam: UriScan:;UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB1214;
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 034902F5BC
Received-SPF: Pass (protection.outlook.com: domain of microsoft.com designates 131.107.125.37 as permitted sender) receiver=protection.outlook.com; client-ip=131.107.125.37; helo=mail.microsoft.com;
Authentication-Results: spf=pass (sender IP is 131.107.125.37) smtp.mailfrom=Michael.Jones@microsoft.com;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0301MB1184;
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/x6aFGhrXeKkbNxOSMahpsaRWPEk
Cc: "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "jose@ietf.org" <jose@ietf.org>, "draft-ietf-jose-json-web-signature@tools.ietf.org" <draft-ietf-jose-json-web-signature@tools.ietf.org>
Subject: Re: [jose] Alissa Cooper's No Objection on draft-ietf-jose-json-web-signature-33: (with COMMENT)
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, 29 Sep 2014 22:57:25 -0000
Thanks for your review, Alissa. I’ve added the working group to this thread so they're aware of your comments. Replies are inline below… -----Original Message----- From: Alissa Cooper [mailto:alissa@cooperw.in] Sent: Sunday, September 28, 2014 7:24 PM To: The IESG Cc: jose-chairs@tools.ietf.org; draft-ietf-jose-json-web-signature@tools.ietf.org Subject: Alissa Cooper's No Objection on draft-ietf-jose-json-web-signature-33: (with COMMENT) Alissa Cooper has entered the following ballot position for draft-ietf-jose-json-web-signature-33: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: http://datatracker.ietf.org/doc/draft-ietf-jose-json-web-signature/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- == Section 2 == "These terms defined by the JSON Web Encryption (JWE) [JWE] specification are incorporated into this specification: "JSON Web Encryption (JWE)" and "JWE Compact Serialization"." Seems like "JWE JSON Serialization" should be included in this list as well. Good catch – thanks. == Section 4.2 == "As indicated by the common registry, JWSs and JWEs share a common Header Parameter space; when a parameter is used by both specifications, its usage must be compatible between the specifications." Since both the JWS and JWE specifications are on their way to becoming RFCs, would it make more sense to say "its usage is compatible between the specifications"? Or is this for the future when new parameters may get defined? (Per my response to your related comment on the JWE spec, this language applies to both initial and subsequent IANA registrations.) == Section 9 == Do we use iesg@iesg.org<mailto:iesg@iesg.org>? I usually use iesg@ietf.org<mailto:iesg@ietf.org>. -- Mike